# mulesoft Informatica Business 360 Connector - Full Documentation --- product: Informatica Business 360 Connector version: 1.0 is-latest-version: true --- # Informatica Business 360 Connector 1.0 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt > [!NOTE] Where possible, we changed noninclusive terms to align with our company value of Equality. > We maintained certain terms to avoid any effect on customer implementations. Anypoint Connector for Informatica Business 360 (Informatica Business 360 Connector) enables Mule applications to integrate with the Informatica Business 360 (MDM) REST API. Use this connector to manage master data records, perform searches, run ML-based fuzzy matching, and discover business object metadata, all from within your Mule flows. For information about compatibility and fixed issues, refer to the Informatica Business 360 Connector Release Notes. ## Before You Begin To use this connector, you must be familiar with: - The Informatica Business 360 Connector’s API - Anypoint Connectors - Mule runtime engine (Mule) - Elements and global elements in a Mule flow - How to create a Mule app using Anypoint Code Builder or Anypoint Studio Before creating an app, you must have: - Credentials to access the Informatica Business 360 target resource - Anypoint Platform - The latest versions of Anypoint Code Builder or Anypoint Studio - Access to an Informatica Business 360 (MDM) environment with valid credentials - At least one business entity configured in your B360 tenant (for example, `c360.person`) ## Supported Authentication Methods This connector supports two Informatica API authentication versions:

Method	Description
Basic Auth V3	Authenticates via the V3 login endpoint (`/saas/public/core/v3/login`) using JSON. Uses the `IDS-SESSION-ID` session header.
Basic Auth V2	Authenticates via the V2 login endpoint (`/ma/api/v2/user/login`) using JSON. Uses the `icSessionId` session header. Retained for environments that require the V2 endpoint.

## Key Capabilities - Entity CRUD Operations Create, read, update (full and partial via JSON patch), delete, and restore business entity records such as persons, organizations, and custom entity types. - Search with Automatic Pagination Perform full-text or field-based searches across entity records. The connector handles pagination transparently, fetching pages on demand as your flow iterates over results. - ML-Based Fuzzy Matching Find similar records using Informatica’s match engine. Search Match V1 matches against source records using blocking fields defined in the match model. - Metadata Discovery The connector dynamically retrieves available business entity types and source systems from the B360 tenant. Anypoint Studio and Anypoint Code Builder display dynamic dropdowns for object types and source systems. - Dynamic Input and Output Metadata The connector dynamically resolves input and output schemas at design time based on the selected business object type, providing field-level autocompletion in Anypoint Studio and Anypoint Code Builder. Dynamic input and output metadata for the operation is cached and is automatically refreshed once every 10 minutes. - Automatic Session Management The connector manages the session token lifecycle automatically, including proactive refresh before the 30-minute expiration window and transparent retry on 401 (Unauthorized) responses. - Error Handling Hierarchy Structured error types (`CLIENT_ERROR`, `SERVER_ERROR`, `CONNECTIVITY`) with specific subtypes (`NOT_FOUND`, `BAD_REQUEST`, `RATE_LIMITED`, etc.) enable precise error handling in your flows. - Debug Logging When the connector logger is set to `DEBUG` level, HTTP request and response details are logged automatically with sensitive data masked. No separate configuration is required. ## Connection Management The connector uses a cached connection model (`CachedConnectionProvider`), meaning a single connection is shared across all operations within a Mule app. The session token is proactively refreshed on a configurable interval (default: 25 minutes) to avoid mid-request expiration. If a request receives a 401 (Unauthorized) response, the connector automatically refreshes the session token and retries the request once before propagating the error. ## Next Step After you complete the prerequisites, you’re ready to create an app and configure the connector using [Anypoint Studio](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-studio) or [Anypoint Code Builder](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-acb). ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange) - [Informatica Business 360 Connector Reference](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-reference) - [Salesforce Help](https://help.salesforce.com) --- product: Informatica Business 360 Connector version: 1.0 is-latest-version: true --- # Informatica Business 360 Connector 1.0 Examples > For the full documentation index, see: https://docs.mulesoft.com/llms.txt This page provides examples for Informatica Business 360 Connector operations. Each example shows the XML configuration you can use in Anypoint Studio or a text editor. ## Before You Begin - Access to an Informatica Business 360 (MDM) environment with valid credentials - A Mule project with Informatica Business 360 Connector added as a dependency - A configured global element for the connector (see [Using Anypoint Studio to Configure Informatica Business 360 Connector 1.0](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-studio)) ## Create and Read a Business Entity This example creates a new person record and then reads it back using the returned business ID. ### XML Configuration ```xml

``` ## Update and Partial Update a Record This example shows both a full update (PUT) and a field-level partial update (PATCH) using JSON Patch format. ### XML Configuration ```xml

``` ## Delete and Restore a Record This example soft-deletes a record and then restores it. ### XML Configuration ```xml

``` ## Search with Pagination This example performs a full-text search and iterates over paginated results. ### XML Configuration ```xml

``` ## Fuzzy Matching with Search Match V1 This example performs ML-based fuzzy matching against source records to find similar person records. ### XML Configuration ```xml

``` ## Error Handling This example shows how to handle specific connector error types in your flows. ### XML Configuration ```xml

``` ## Retry with Until Successful This example wraps a connector operation with `until-successful` for automatic retry on transient failures. ### XML Configuration ```xml

``` ## See Also - [Informatica Business 360 Connector Reference](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-reference) - [Using Anypoint Studio to Configure Informatica Business 360 Connector](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-studio) - [Salesforce Help](https://help.salesforce.com/s/) --- product: Informatica Business 360 Connector version: 1.0 is-latest-version: true --- # Informatica Business 360 Connector 1.0 Reference > For the full documentation index, see: https://docs.mulesoft.com/llms.txt > [!NOTE] Where possible, we changed noninclusive terms to align with our company value of Equality. > We maintained certain terms to avoid any effect on customer implementations. ## Configurations ### Default Configuration Default configuration for the connector. #### Parameters

Name	Type	Description	Required
Name	String	The name for this configuration. Connectors reference the configuration with this name.	x
Connection	Login V2 Connection Provider Login V3 Connection Provider	The connection types to provide to this configuration.	x
Name	String	The identifier of this element used to reference it in other components.	x
Expiration Policy	Expiration Policy	Configures the minimum amount of time that a dynamic configuration instance can remain idle before Mule considers it eligible for expiration. This does not mean that the platform expires the instance at the exact moment that it becomes eligible. Mule purges the instances as appropriate.

#### Connection Types ##### Login V2 Connection Provider ###### Parameters

Name	Type	Description	Default Value	Required
Base URL	String	Base URL for the Informatica MDM API.		x
Username	String	The username used to authenticate requests.		x
Password	String	The password used to authenticate requests.		x
Connection Timeout	Number	Connection timeout for the request.	30
Connection Timeout Unit	Enumeration, one of: NANOSECONDS MICROSECONDS MILLISECONDS SECONDS MINUTES HOURS DAYS	Time unit for the Connection Timeout field.	SECONDS
Use Persistent Connections	Boolean	Whether to use persistent HTTP connections for outbound requests.	true
Max Connections	Number	Maximum simultaneous outbound connections, unlimited by default.	-1
Connection Idle Timeout	Number	Time a connection can stay idle before closing. Applies only when persistent connections are enabled.	30
Connection Idle Timeout Unit	Enumeration, one of: NANOSECONDS MICROSECONDS MILLISECONDS SECONDS MINUTES HOURS DAYS	Time unit for the Connection Idle Timeout field.	SECONDS
Stream Response	Boolean	When enabled, allows processing to begin after headers are parsed. The response must be read eventually to avoid memory issues.	false
Response Buffer Size	Number	Space in bytes for the buffer where the HTTP response is stored.	-1
Token Refresh Interval (minutes)	Number	Interval in minutes at which the session token is refreshed.	25
Proxy Configuration	One of: Default NTLM	HTTP proxy configuration for outbound requests.
TLS Configuration	TLS	When using HTTPS, the TLS configuration used to secure the connection.
Default Headers	Array of Default Header	Custom headers to include in every request.
Default Query Parameters	Array of Default Query Param	Custom query parameters to include in every request.
Reconnection	Reconnection	When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test does not pass after exhausting the associated reconnection strategy.

##### Login V3 Connection Provider ###### Parameters

Name	Type	Description	Default Value	Required
Base URL	String	Base URL for the Informatica MDM API.		x
Username	String	The username used to authenticate requests.		x
Password	String	The password used to authenticate requests.		x
Connection Timeout	Number	Connection timeout for the request.	30
Connection Timeout Unit	Enumeration, one of: NANOSECONDS MICROSECONDS MILLISECONDS SECONDS MINUTES HOURS DAYS	Time unit for the Connection Timeout field.	SECONDS
Use Persistent Connections	Boolean	Whether to use persistent HTTP connections for outbound requests.	true
Max Connections	Number	Maximum simultaneous outbound connections, unlimited by default.	-1
Connection Idle Timeout	Number	Time a connection can stay idle before closing. Applies only when persistent connections are enabled.	30
Connection Idle Timeout Unit	Enumeration, one of: NANOSECONDS MICROSECONDS MILLISECONDS SECONDS MINUTES HOURS DAYS	Time unit for the Connection Idle Timeout field.	SECONDS
Stream Response	Boolean	When enabled, allows processing to begin after headers are parsed. The response must be read eventually to avoid memory issues.	false
Response Buffer Size	Number	Space in bytes for the buffer where the HTTP response is stored.	-1
Token Refresh Interval (minutes)	Number	Interval in minutes at which the session token is refreshed.	25
Proxy Configuration	One of: Default NTLM	HTTP proxy configuration for outbound requests.
TLS Configuration	TLS	When using HTTPS, the TLS configuration used to secure the connection.
Default Headers	Array of Default Header	Custom headers to include in every request.
Default Query Parameters	Array of Default Query Param	Custom query parameters to include in every request.
Reconnection	Reconnection	When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test does not pass after exhausting the associated reconnection strategy.

## Supported Operations - [Create Entity](#CreateEntity) - [Delete Entity](#DeleteEntity) - [Partial Update Entity](#PartialUpdateEntity) - [Read Entity](#ReadEntity) - [Restore Entity](#RestoreEntity) - [Search](#Search) - [Search Match V1](#SearchMatchV1) - [Update Entity](#UpdateEntity) ## Operations ## Create Entity `` Creates a master data record in Informatica Business 360. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity or object type identifier (for example, `c360.person`).		x
Source System	String	Internal ID of the source system.		x
Payload	Any	Request body for the create operation.		x
Source Primary Key	String	Primary key of the source record.
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Any
Attributes Type	HTTP Response Attributes

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Delete Entity `` Removes data from Business 360. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity or object type identifier (for example, `c360.person`).		x
Business ID	String	Unique business identifier of the master record.		x
Source System	String	Internal ID of the source system.		x
Source Primary Key	String	When specified, deletes only the source record instead of the master record.
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Any
Attributes Type	HTTP Response Attributes

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Partial Update Entity `` Applies partial changes to an existing master record using a list of update operations (for example, JSON patch), without sending a full entity replacement. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity or object type identifier (for example, `c360.person`).		x
Business ID	String	Unique business identifier of the master record.		x
Source System	String	Internal ID of the source system.		x
Update Operations	Array of Any	Partial update operations to apply to the entity (for example, JSON patch operations).		x
Resolve Crosswalk	Boolean	Standardize picklist values based on source system configuration.	false
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Any
Attributes Type	HTTP Response Attributes

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Read Entity `` Fetches a master record. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity or object type identifier (for example, `c360.person`).		x
Business ID	String	Unique business identifier of the master record.		x
Skip Lookup	Boolean	Retrieve picklist values from cache instead of the data store.	false
Show Content Metadata	Boolean	Include trust scores and survivorship configuration.	false
Show Pending	Boolean	Retrieve only master records pending review.	false
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Binary
Attributes Type	HTTP Response Attributes

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Restore Entity `` Recovers a master record that was previously deleted. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity or object type identifier (for example, `c360.person`).		x
Business ID	String	Unique business identifier of the deleted master record.		x
Source System	String	Internal ID of the source system.		x
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Any
Attributes Type	HTTP Response Attributes

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Search `` Runs a search against a business entity type. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity GUID (for example, `c360.person`).		x
Query	Any	Search query body in JSON format with `search` or `fields` parameters.		x
Page Size	Number	Number of records per page (maximum 10000).	50
Record Offset	Number	Number of records to skip before returning results.	0
Records To Return	Number	Total number of records to return (`-1` for all matching records).	-1
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Iterable Repeatable File Store Iterable non-repeatable-iterable	Configures how Mule processes iterable results. Repeatable iteration is the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Array of Any

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Search Match V1 `` Invokes Informatica Business 360 match (fuzzy matching) for a record against a published match model on the selected object type. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity GUID for an entity with a published match model (for example, `c360.person`).		x
Payload	Any	JSON body with `searchControls` and `data.searchRecord`.		x
Match Model	String	Unique identifier of a published match model.
Version	Number	Match model version number (defaults to the latest version).
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Any
Attributes Type	HTTP Response Attributes

### For Configurations - [Default Configuration](#Config) ### Throws - INFORMATICA-B360:BAD\_GATEWAY - INFORMATICA-B360:BAD\_REQUEST - INFORMATICA-B360:CLIENT\_ERROR - INFORMATICA-B360:CONNECTIVITY - INFORMATICA-B360:FORBIDDEN - INFORMATICA-B360:GATEWAY\_TIMEOUT - INFORMATICA-B360:NOT\_FOUND - INFORMATICA-B360:RATE\_LIMITED - INFORMATICA-B360:REQUEST\_TIMEOUT - INFORMATICA-B360:RETRY\_EXHAUSTED - INFORMATICA-B360:SERVER\_BUSY - INFORMATICA-B360:SERVER\_ERROR - INFORMATICA-B360:SERVICE\_ERROR - INFORMATICA-B360:UNAUTHORIZED ## Update Entity `` Replaces an existing master record with the full payload. ### Parameters

Name	Type	Description	Default Value	Required
Configuration	String	The name of the configuration to use.		x
Object Type	String	Business entity or object type identifier (for example, `c360.person`).		x
Business ID	String	Unique business identifier of the master record.		x
Source System	String	Internal ID of the source system.		x
Payload	Any	Request body for the update operation.		x
Resolve Crosswalk	Boolean	Standardize picklist values based on source system configuration.	false
Output Mime Type	String	The MIME type of the payload that this operation outputs.
Output Encoding	String	The encoding of the payload that this operation outputs.
Config Ref	ConfigurationProvider	The name of the configuration to use to execute this component.		x
Streaming Strategy	Repeatable In Memory Stream Repeatable File Store Stream non-repeatable-stream	Configures how Mule processes streams. Repeatable streams are the default behavior.
Custom Query Parameters	Object	Additional query parameters to send with the request.
Custom Headers	Object	Additional HTTP headers to send with the request.
Target Variable	String	Name of the variable that stores the operation’s output.
Target Value	String	An expression to evaluate against the operation’s output and store the expression outcome in the target variable.	#[payload]
Error Mappings	Array of Error Mapping	Set of error mappings.
Reconnection Strategy	Reconnect Reconnect Forever	A retry strategy in case of connectivity errors.

### Output

Type	Any
Attributes Type	HTTP Response Attributes

Field	Type	Description
Enabled Protocols	String	A comma-separated list of protocols enabled for this context.
Enabled Cipher Suites	String	A comma-separated list of cipher suites enabled for this context.
Trust Store	Trust Store	Trust store configuration for verifying server certificates.
Key Store	Key Store	Key store configuration for client certificate authentication.
Revocation Check	Standard Revocation Check Custom OCSP Responder CRL File	Certificate revocation checking configuration.

### Trust Store

Field	Type	Description
Path	String	The location (which will be resolved relative to the current classpath and file system, if possible) of the trust store.
Password	String	The password used to protect the trust store.
Type	String	The type of store used.
Algorithm	String	The algorithm used by the trust store.
Insecure	Boolean	If true, no certificate validations will be performed, rendering connections vulnerable to attacks. Use at your own risk.

### Key Store

Field	Type	Description
Path	String	The location (which will be resolved relative to the current classpath and file system, if possible) of the key store.
Type	String	The type of store used.
Alias	String	When the key store contains many private keys, this attribute indicates the alias of the key that should be used. If not defined, the first key in the file will be used by default.
Key Password	String	The password used to protect the private key.
Password	String	The password used to protect the key store.
Algorithm	String	The algorithm used by the key store.

### Standard Revocation Check

Field	Type	Description
Only End Entities	Boolean	Only verify the last element of the certificate chain.
Prefer Crls	Boolean	Try CRL instead of OCSP first.
No Fallback	Boolean	Do not use the secondary checking method (the one not selected before).
Soft Fail	Boolean	Avoid verification failure when the revocation server can not be reached or is busy.

### Custom OCSP Responder

Field	Type	Description	Default Value	Required
Url	String	The URL of the OCSP responder.
Cert Alias	String	Alias of the signing certificate for the OCSP response (must be in the trust store), if present.

### CRL File

Field	Type	Description	Default Value	Required
Path	String	The path to the CRL file.

### Default Header

Field	Type	Description	Default Value	Required
Key	String	HTTP header name.		x
Value	String	HTTP header value.		x

### Default Query Param

Field	Type	Description	Default Value	Required
Key	String	Query parameter name.		x
Value	String	Query parameter value.		x

### Reconnection

Field	Type	Description	Default Value	Required
Fails Deployment	Boolean	When the application is deployed, a connectivity test is performed on all connectors. If set to true, deployment fails if the test does not pass after exhausting the associated reconnection strategy.
Reconnection Strategy	Reconnect Reconnect Forever	The reconnection strategy to use.

### Reconnect

Field	Type	Description
Frequency	Number	How often in milliseconds to reconnect.
Blocking	Boolean	If false, the reconnection strategy runs in a separate, non-blocking thread.
Count	Number	How many reconnection attempts to make.

### Reconnect Forever

Field	Type	Description	Default Value	Required
Frequency	Number	How often in milliseconds to reconnect.
Blocking	Boolean	If false, the reconnection strategy runs in a separate, non-blocking thread.

### Expiration Policy

Field	Type	Description	Default Value	Required
Max Idle Time	Number	A scalar time value for the maximum amount of time a dynamic configuration instance should be allowed to be idle before it is considered eligible for expiration.
Time Unit	Enumeration, one of: NANOSECONDS MICROSECONDS MILLISECONDS SECONDS MINUTES HOURS DAYS	Time unit for the Max Idle Time field.

### HTTP Response Attributes

Field	Type	Description
Headers	Object	HTTP response headers.
Reason Phrase	String	HTTP reason phrase for the status code.
Status Code	Number	HTTP status code of the response.

### Repeatable In Memory Stream

Field	Type	Description
Initial Buffer Size	Number	The amount of memory that will be allocated to consume the stream and provide random access to it. If the stream contains more data than can be fit into this buffer, then the buffer expands according to the bufferSizeIncrement attribute, with an upper limit of maxInMemorySize.
Buffer Size Increment	Number	This is by how much the buffer size expands if it exceeds its initial size. Setting a value of zero or lower means that the buffer should not expand, meaning that a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised when the buffer gets full.
Max Buffer Size	Number	The maximum amount of memory to use. If more than that is used then a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised. A value lower than or equal to zero means no limit.
Buffer Unit	Enumeration, one of: BYTE KB MB GB	The unit in which all these attributes are expressed.

### Repeatable File Store Stream

Field	Type	Description	Default Value	Required
In Memory Size	Number	Defines the maximum memory that the stream should use to keep data in memory. If more than that is consumed content on the disk is buffered.
Buffer Unit	Enumeration, one of: BYTE KB MB GB	Unit for the In Memory Size field.

### Error Mapping

Field	Type	Description	Default Value	Required
Source	Enumeration, one of: ANY REDELIVERY_EXHAUSTED TRANSFORMATION EXPRESSION SECURITY CLIENT_SECURITY SERVER_SECURITY ROUTING CONNECTIVITY RETRY_EXHAUSTED TIMEOUT	Source error type to map from.
Target	String	Target error type identifier for the mapping.		x

### Repeatable In Memory Iterable

Field	Type	Description
Initial Buffer Size	Number	The number of instances initially allowed in memory to consume the stream and provide random access to it. If the stream contains more data than can fit into this buffer, then the buffer expands according to the Buffer Size Increment field, with an upper limit of Max Buffer Size. The default value is 100 instances.
Buffer Size Increment	Number	This is by how much the buffer size expands if it exceeds its initial size. Setting a value of zero or lower means that the buffer should not expand, meaning that a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised when the buffer gets full. Default value is 100 instances.
Max Buffer Size	Number	The maximum amount of memory to use. If more than that is used then a STREAM_MAXIMUM_SIZE_EXCEEDED error is raised. A value lower than or equal to zero means no limit.

### Repeatable File Store Iterable

Field	Type	Description	Default Value	Required
In Memory Objects	Number	The maximum amount of instances to keep in memory. If more than that is required, content on the disk is buffered.
Buffer Unit	Enumeration, one of: BYTE KB MB GB	Unit for the In Memory Objects field.

### Default

Field	Type	Description	Required
Host	String	Proxy server hostname or IP address.	x
Port	Number	Proxy server port number.	x
Username	String	Username for proxy authentication.
Password	String	Password for proxy authentication.
Non Proxy Hosts	String	Comma-separated list of hosts that bypass the proxy.

### NTLM

Field	Type	Description	Required
Ntlm Domain	String	NTLM domain name for proxy authentication.	x
Host	String	Proxy server hostname or IP address.	x
Port	Number	Proxy server port number.	x
Username	String	Username for proxy authentication.
Password	String	Password for proxy authentication.
Non Proxy Hosts	String	Comma-separated list of hosts that bypass the proxy.

--- product: Informatica Business 360 Connector version: 1.0 is-latest-version: true --- # Informatica Business 360 Connector 1.0 XML and Maven Support > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Although you can manually code a Mule app in XML, it is more efficient to use Anypoint Code Builder or Studio: - If you manually code a Mule runtime engine (Mule) app in XML, either from the Anypoint Code Builder or Studio XML editor, or from a text editor, you can access the connector from your app by adding reference statements to both your XML Mule flow and the Apache Maven `pom.xml` file. - If you add the connector in Anypoint Code Builder or Studio, the XML is automatically populated the code with the connector’s namespace and schema location and it also adds a dependency to the `pom.xml` file. ## Add a Namespace for the Connector Paste the following code inside the `mule` tag of the header of your configuration XML: ```xml http://www.mulesoft.org/schema/mule/informatica b360 http://www.mulesoft.org/schema/mule/informatica b360/current/mule-informatica b360.xsd ``` This example shows how the namespace statements are placed in the `` XML block: ```xml ``` ## Add a POM File Dependency The Apache Maven `pom.xml` file generated by Anypoint Studio contains dependencies for a Mule app. If you code a Mule app manually, include this XML snippet in your `pom.xml` file to enable access to this connector: ```xml com.mulesoft.connectors mule4-informatica-b360-connector x.x.x mule-plugin ``` Replace `x.x.x` with the version that corresponds to the connector you are using. To obtain the most up-to-date `pom.xml` file information: 1. Go to [Anypoint Exchange](https://www.mulesoft.com/exchange/). 2. In Exchange, click **Login** and supply your Anypoint Platform username and password. 3. In Exchange, search for `informatica-b360`. 4. Select the connector. 5. Click **Dependency Snippets** near the upper right of the screen. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Salesforce Help](https://help.salesforce.com) --- product: Informatica Business 360 Connector version: 1.0 is-latest-version: true --- # Using Anypoint Code Builder to Configure Informatica Business 360 Connector 1.0 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Cloud IDE (Beta) is scheduled for retirement on August 31, 2026. August 30, 2026 is the last day you can access Cloud IDE (Beta). Download your projects to work from Desktop IDE. Learn more in [Migrate a Project from Cloud IDE to Desktop IDE](https://docs.mulesoft.com/anypoint-code-builder/int-import-mule-project#migrate-cloud-to-desktop). To use Anypoint Code Builder to configure a connector or module, create a basic integration project in Anypoint Code Builder, add connectors and other components to your Mule application to process your business logic, and configure the attributes. ## Before You Begin Before creating an integration project, you must: - [Set up and access the Anypoint Code Builder web or desktop IDE](https://docs.mulesoft.com/anypoint-code-builder/start-acb) - Have credentials to access the connector’s API - Ensure that the Visual Studio Code Extension Pack for Java is installed. To use this connector, you must be familiar with: - The connector’s API - Anypoint Connectors - Mule runtime engine (Mule) ## Create a New Integration Project To create a new integration project: 1. In the activity bar of the IDE, click the ![Anypoint Code Builder icon](/mulesoft/current/en-us/connectors/_images/acb-icon-ms-logo.png) (**Anypoint Code Builder**) icon. 2. From **Quick Actions**, click **Develop an Integration**: ![Develop an Integration link highlighted in the Getting started section](/mulesoft/current/en-us/anypoint-code-builder/_images/develop-integration-option-mat.png) 3. Complete the following in the **Develop an Integration** form:

Attribute	Value
Project Name	Unique name for your project. This name is used as the title and name of the integration project file. For example, if the project name is "Salesforce Integration," the project file name is `salesforce-integration`.
Project Location	Your home directory or another directory you create. Click Browse to select a different directory for the integration project. Don’t create the project within another project directory. See Adding Folders to Your Home Directory.

4. Select the type of project to create by selecting either the **Empty Project** or **Template or Example** card. 5. Select the **Mule runtime** and **Java Version** for your app. 6. Click **Create Project**. ## Add the Connector to Your Integration Project Anypoint Connectors provide operations for retrieving, modifying, and sending data to and from systems. In addition to the [built-in connectors](https://docs.mulesoft.com/anypoint-code-builder/acb-reference#builtin-connectors) that Anypoint Code Builder provides, you can download many other connectors from Anypoint Exchange. To import a connector from Exchange and add it to your configuration: 1. In the Explorer view, open the configuration XML file for your project, such as `my-project-name.xml`. 2. Click the ![Show Mule graphical mode icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-tree-view.png) (**Show Mule graphical mode**) icon in the activity bar to open the canvas UI if it doesn’t open automatically. 3. Add the connector the same way you added other components from the canvas UI: 1. In the canvas UI, click the ![Add component icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-plus.png) (**Add component**) icon. 2. In the **Add Component** panel, click **Connectors**. 3. Click the connector name and then click the operation to add, such as **Publish**: ![Add Publish operation from Anypoint MQ Connector](/mulesoft/current/en-us/anypoint-code-builder/_images/int-add-connector-operation.png) If the connector is not available locally, click the ![Search in Exchange icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-search-exchange.png) (**Search in Exchange**) toggle: ![Search in Exchange toggle](/mulesoft/current/en-us/anypoint-code-builder/_images/int-connector-search-exchange.png)

1	Search locally
2	Search in Exchange

4. Select the connector to add to your project. 5. Select the operation from the **Add Component** panel. Adding a connector to an integration project does not make that connector available to other projects in your Anypoint Code Builder workspace. ## Configure the Source For the Flow A trigger (source) starts the flow when specified conditions are met. If a connector has its own associated sources, you can use a connector-specific trigger to initiate the flow. Each connector trigger has a unique configuration. You can configure the following sources for this 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 trigger, follow these steps: 1. Click the **Listener** component on the canvas UI. 2. (Optional) Click the edit icon to change the name of the **Listener** component. 3. (Optional) If you created a configuration file for the connector, select it. 4. In the **General** tab, in the **Path** field, enter the relative path for the path set in the HTTP configuration element. See [Configure Paths](https://docs.mulesoft.com/http-connector/latest/http-listener-ref#configure-paths). 5. Select the **Advanced** tab to configure the following attributes:

Attribute	Description	Required
Allowed methods	To allow all HTTP methods (default), do not define this attribute. To restrict certain methods, specify all allowed HTTP methods, for example, `GET, POST`, as a comma-separated list.	No
Response streaming mode	Whether to use streaming when the response is sent.	No
Output MIME type	MIME type of the payload that this component outputs.	No
Parameters	Appends a key-value pair for a reader property to the value of the Output MIME attribute. Multiple key-value pairs are allowed.	No
Output encoding	Encoding of the payload that this component outputs.	No
Streaming Strategy	Configures the way data streams are consumed in Mule apps.	No
Primary node only	Select this option to execute the Listener trigger on the primary node only when running in a cluster.	No
Redelivery policy	Configures the redelivery policy for executing requests that generate errors. You can add a redelivery policy to any source in a flow.	No
Reconnection strategy	When an operation in a Mule application fails to connect to an external server, the default behavior is for the operation to fail immediately and return a connectivity error. You can modify the default behavior by configuring the reconnection strategy for the operation.	No
Response	See HTTP Response Attributes.	No
Error Response	HTTP error response returns a status code for the error.	No
Body	Body of the error message.	No
Headers	Headers to include in the error message.	No
Status code	Status code of the error response, for example, `500`.	No
Reason phrase	Reason for the error, for example, `Gateway Timeout` or `Internal Server Error`.	No

## Add Components to Your Project Add components to your integration project to build a flow: 1. In the **Explorer** view, open the XML file for your project, such as `my-project-name.xml`. 2. Select **Build a Flow** from the start card to create an empty flow: ![Anypoint Code Builder canvas with starting cards with the options to start from scratch, build a flow, or build a subflow](/mulesoft/current/en-us/connectors/_images/acb-build-flow.png) 3. Change the name of the flow: 1. Click **Flow**. 2. Click the edit icon. ![Arrow pointing to the flow name edit pencil icon](/mulesoft/current/en-us/connectors/_images/acb-change-flow-name.png) 3. Enter the flow name, and click the checkmark. 4. In the canvas UI, click the ![Add component icon](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-plus.png) (**Add component**) icon. 5. In the **Add Component** panel, search for and select your component from the results. The following example shows the **Listener** component from the **HTTP** search results: ![Listener component highlighted in the Add Component section](/mulesoft/current/en-us/anypoint-code-builder/_images/main-tutorial-add-first-listener.png) The configuration XML file now includes the XML for the HTTP Listener into the `` element, for example: ```XML ``` ## Configure the Component Attributes After you add components to your integration project, configure the attributes in the component UI, or configure the attributes directly in the XML code editor. Connector XML tags start with a namespace followed by an operation, following the syntax `namespace:operation`, such as `` for a **Select** operation in Anypoint Connector for Database (Database Connector). You can use autocomplete from an expression (**fx**) field for a component to select DataWeave functions from the Core module and other values accepted in this field. ### Connection Configuration (V3) ```xml

``` ### Connection Configuration (V2) ```xml

``` ### Connection Configuration with Advanced Settings ```xml

``` ### Entity Operations #### Create Entity ```xml

``` #### Read Entity ```xml ``` #### Update Entity (Full) ```xml

``` #### Partial Update Entity (JSON Patch) ```xml

``` #### Delete Entity ```xml ``` #### Restore Entity ```xml ``` ### Search Operations #### Search ```xml

``` #### Search Match V1 (Source Records) ```xml

``` ## Create a New Configuration XML File Anypoint Code Builder creates the initial Mule configuration XML file in `src/main/mule` within the Mule project. This file contains global configurations and flow structures. You can create additional configuration files, for example, to store global configurations. To create a new XML configuration file: 1. In the Explorer view, right-click the **mule** folder (`src/main/mule`) and select **New File**. Alternatively, use the menu. Show me how Select the `mule` folder, and then: - In the desktop IDE, select **File** > **New Mule Configuration File**. - In the cloud IDE, click the ![](/mulesoft/current/en-us/anypoint-code-builder/_images/icon-menu.png) (menu) icon, and select **File** > **New File**. 2. Enter a name for the new file with the `.xml` extension. 3. In the Editor view for the new file, press Ctrl+Space to display available options. 4. Select **Empty mule configuration**: ![New Mule configuration option in auto-correct](/mulesoft/current/en-us/anypoint-code-builder/_images/int-new-mule-config.png) This command adds the following code to the file: ```xml ``` ## See Also - [Anypoint Code Builder Overview](https://docs.mulesoft.com/anypoint-code-builder/) - [Creating Integrations](https://docs.mulesoft.com/anypoint-code-builder/int-create-integrations) - [Using Anypoint Code Builder to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-acb) - [Anypoint Code Builder Components and Commands Reference](https://docs.mulesoft.com/anypoint-code-builder/acb-reference) - [Defining and Securing Properties for a Mule Application](https://docs.mulesoft.com/anypoint-code-builder/int-create-secure-configs) - [Triggering Flows in Your Development Environment](https://docs.mulesoft.com/anypoint-code-builder/int-trigger-flows) - [Configuring Components](https://docs.mulesoft.com/anypoint-code-builder/int-configure-components) - [Debugging Mule Applications](https://docs.mulesoft.com/anypoint-code-builder/int-debug-mule-apps) - [Salesforce Help](https://help.salesforce.com) --- product: Informatica Business 360 Connector version: 1.0 is-latest-version: true --- # Using Anypoint Studio to Configure Informatica Business 360 Connector 1.0 > For the full documentation index, see: https://docs.mulesoft.com/llms.txt 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](#create-mule-project). 2. [Add the connector to your Mule project](#add-connector-to-project). 3. [Configure a source for the connector’s flow](#configure-source). 4. [Add a connector operation to the flow](#add-connector-operation). 5. [Configure a global element for the connector](#configure-global-element). 6. [Configure the other connector fields](#configure-other-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](#view-app-log). If you are new to configuring connectors in Studio, see [Using Anypoint Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio). If, after reading this topic, you need additional information about the connector fields, see the [Informatica Business 360 Connector Reference](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-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: - [Login V3 Connection Provider](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-reference#Config_BasicAuthV3) Authenticates using the Informatica V3 login endpoint with JSON-only communication. - [Login V2 Connection Provider](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-reference#Config_BasicAuthV2) Authenticates using the Informatica V2 login endpoint. Use this for environments that require the V2 authentication endpoint. 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](https://docs.mulesoft.com/connectors/introduction/intro-connector-configuration-overview). 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: ```json [{ "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: ```xml ``` 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/.log`. You can configure the location of the log path in the app log file `log4j2.xml`. ## See Also - [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors) - [Using Studio to Configure a Connector](https://docs.mulesoft.com/connectors/introduction/intro-config-use-studio) - [Informatica Business 360 Connector Reference](https://docs.mulesoft.com/informatica-b360-connector/latest/informatica-b360-connector-reference) - [Salesforce Help](https://help.salesforce.com)