Contact Us 1-800-596-4880
  1. Homepage
  2. Informatica Business 360 Connector (1.0)

  3. Using Anypoint Studio to Configure Informatica Business 360 Connector

All Connectors

Using Anypoint Studio to Configure Informatica Business 360 Connector 1.0

Anypoint Studio (Studio) editors help you design and update your Mule applications, properties, and configuration files.

To add and configure a connector in Studio:

  1. Create a Mule project.

  2. Add the connector to your Mule project.

  3. Configure a source for the connector’s flow.

  4. Add a connector operation to the flow.

  5. Configure a global element for the connector.

  6. Configure the other connector fields.

When you run the connector, you can view the app log to check for problems in real time, as described in View the App Log.

If you are new to configuring connectors in Studio, see Using Anypoint Studio to Configure a Connector. If, after reading this topic, you need additional information about the connector fields, see the Informatica Business 360 Connector Reference.

Create a Mule Project

In Studio, create a new Mule project in which to add and configure Anypoint Connector for Informatica Business 360 (Informatica Business 360 Connector):

  1. In Studio, select File > New > Mule Project.

  2. Enter a name for your Mule project and click Finish.

Add the Connector to Your Mule Project

Add Informatica Business 360 Connector to your Mule project to automatically populate the XML code with the connector’s namespace and schema location and add the required dependencies to the project’s pom.xml file:

  1. In Mule Palette, click (X) Search in Exchange.

  2. In Add Dependencies to Project, type informatica b360 in the search field.

  3. Click Informatica Business 360 Connector in Available modules.

  4. Click Add.

  5. Click Finish.

Adding a connector to a Mule project in Studio does not make that connector available to other projects in your Studio workspace.

Configure a Source

A source initiates a flow when a specified condition is met. You can configure one of these sources to use with Informatica Business 360 Connector:

  • HTTP > Listener

    Initiates a flow each time it receives a request on the configured host and port

  • Scheduler

    Initiates a flow when a time-based condition is met

For example, to configure an HTTP > Listener source, follow these steps:

  1. In Mule Palette, select HTTP > Listener.

  2. Drag Listener to the Studio canvas.

  3. On the Listener configuration screen, optionally change the value of the Display Name field.

  4. Specify a value for the Path field.

  5. Click the plus sign (+) next to the Connector configuration field to configure a global element that can be used by all instances of the HTTP > Listener source in the app.

  6. On the General tab, specify the connection information for the connector.

  7. On the TLS tab, optionally specify the TLS information for the connector.

  8. On the Advanced tab, optionally specify reconnection information, including a reconnection strategy.

  9. Click Test Connection to confirm that Mule can connect with the specified server.

  10. Click OK.

Add a Connector Operation to the Flow

When you add a connector operation to your flow, you are specifying an action for that connector to perform.

To add an operation for Informatica Business 360 Connector, follow these steps:

  1. In Mule Palette, select Informatica Business 360 and then select the desired operation.

  2. Drag the operation onto the Studio canvas, next to the source.

Configure a Global Element for the Connector

When you configure the connector, configure a global element that all instances of that connector in the app can use. Configuring a global element requires you to provide the authentication credentials and connection settings the connector needs to access the Informatica Business 360 API.

To configure the global element for Informatica Business 360 Connector, follow these steps:

  1. Select the operation in the Studio canvas.

  2. In the General configuration screen for the operation, click the Add icon to access the global element configuration fields.

  3. In the General tab, in Connection, select the connection type to use:

  4. Configure the required connection parameters:

    • Base URL: The Informatica Cloud base URL for your region (for example, https://dmr-us.informaticacloud.com)

    • Username: Your Informatica Cloud username

    • Password: Your Informatica Cloud password

      You can reference a configuration file that contains ANT-style property placeholders (recommended), or you can enter your connection details in the global configuration properties. For information about the benefits of using property placeholders and how to configure them, refer to Anypoint Connector Configuration.

  5. In the Advanced tab, optionally configure:

    • Default Headers: Custom headers to include in every API request

    • Default Query Parameters: Custom query parameters to append to every API request

    • Connection Timeout: TCP connection timeout (default: 30 seconds)

    • Use Persistent Connections: Keep connections open for reuse (default: true)

    • Max Connections: Maximum simultaneous outbound connections (default: unlimited)

    • Connection Idle Timeout: Time an idle connection can remain open (default: 30 seconds)

    • Token Refresh Interval: How often to proactively refresh the session token (default: 25 minutes)

    • Reconnection information, including a reconnection strategy

  6. In the Proxy tab, optionally configure HTTP proxy settings (Standard or NTLM).

  7. In the TLS tab, optionally configure TLS settings for environments with custom certificates.

  8. Click Test Connection to confirm that Mule can connect with the specified Informatica B360 instance.

  9. Click OK.

Configure Additional Connector Fields

After you configure a global element for Informatica Business 360 Connector, configure the other required fields for the connector. The required fields vary depending on which connector operation you use.

Configure Entity Operations

Entity operations require the following parameters:

  • Object Type: Select the business entity type from the dropdown (for example, c360.person). The connector dynamically retrieves available object types from your B360 tenant.

  • Source System: Select the source system from the dropdown (for example, b360.default.system).

  • Business ID: The unique business identifier of the record (required for read, update, partial update, delete, and restore operations).

For create-entity and update-entity, the payload schema is dynamically resolved based on the selected object type. Anypoint Studio displays the available fields in the DataSense explorer.

For partial-update-entity, the payload uses JSON patch format:

[
  { "op": "replace", "path": "lastName", "value": "NewValue" }
]

Configure Search Operations

The search operation requires:

  • Object Type: The business entity type to search

  • Query: A JSON body containing the search criteria (search for full text or fields for field specific lookups)

  • Page Size (optional): Number of records per page (default: 50, max: 10,000)

  • Record Offset (optional): Number of records to skip before returning results (default: 0)

  • Records To Return (optional): Total number of records to return across all pages (default: -1, meaning all matching records)

The connector handles pagination automatically. Results are returned as an iterator that fetches pages on demand.

Enable Debug Logging

To enable detailed request and response logging, add the following to your Mule app’s log4j2.xml configuration:

<AsyncLogger name="com.mulesoft.connectors.informatica.b360.internal.connection.InfaB360Connection" level="DEBUG" />

Debug logging captures HTTP method, URI, headers (with sensitive values masked), and body content (truncated at 2048 characters) for every API call.

View the App Log

To check for problems, you can view the app log as follows:

  • If you’re running the app from Anypoint Platform, the app log output is visible on the Anypoint Studio console window.

  • If you’re running the app using Mule from the command line, the app log output is visible in your operating system console.

Unless the log file path is customized in the app’s log file (log4j2.xml), you can also view the app log in the default location MULE_HOME/logs/<app-name>.log. You can configure the location of the log path in the app log file log4j2.xml.

See Also

Back to top