Skip to content

mule-infa-mdm-connector

A MuleSoft Java SDK Connector (ain't no REST wrapper 😉 ) for the Informatica MDM Business 360 REST API, providing native Anypoint Studio and Anypoint Code Builder integration with full DataSense metadata resolution.

New to MDM? Read the Design Concept page first — it explains why the operations are named the way they are and how this connector bridges the gap between MDM terminology and Application Integration patterns.

Key Benefits

  • Native MDM Operations: Dedicated operations for Master Read, Search, Source Read, and Source Submit — no HTTP Requester boilerplate required.
  • Dynamic DataSense: Metadata resolvers introspect your B360 tenant datamodel at design time, providing entity-aware input/output types and attribute metadata.
  • Value Providers: Drop-down selection for Business Entities and Source Systems, populated directly from your MDM tenant.
  • Simplified Authentication: Logs in via the IICS V3 Login API and automatically manages session tokens and JWT refresh.
  • Proxy & TLS Support: Full support for HTTP/HTTPS, custom TLS contexts, and HTTP proxy configuration.

Operations

OperationDisplay NameDescription
Master ReadINFA MDM - Master ReadRead a master record by Business ID or Source System key
SearchINFA MDM - Master SearchFull-text or field-level search across business entities
Source ReadINFA MDM - Source ReadRead a cross-reference (source) record
Source SubmitINFA MDM - Source SubmitCreate or update a source record
MetaData ReadINFA MDM - MetaData ReadRead schema, entity blueprints, or relationship metadata
Http RequestINFA MDM - Http RequestSend an HTTP request to any B360/MDM endpoint with the connector's session

Use Cases

Data Enrichment / Lookup

An incoming order or service request contains a customer name or ID. Use Search or Master Read to look up the golden record in MDM and enrich the payload with verified address, phone, email, or other attributes before routing downstream.

Customer 360 / Single View

Surface the master record in a CRM, portal, or case management system. Master Read by Business ID gives you the consolidated golden record; Source Read lets you drill into the individual source contributions (e.g., "this address came from SAP, that phone number came from Salesforce").

Data Onboarding / Ingestion

New or updated records arrive from an external system (file, API, event). Use Source Submit to push them into MDM as source records, letting B360's match/merge engine handle deduplication and survivorship.

Data Synchronization

Keep downstream systems in sync with MDM. Use Search or Master Read to pull master data, then transform and push to target systems (ERP, data warehouse, marketing platform).

Duplicate Detection / Validation

Before creating a new account or contact, Search MDM to check if a matching record already exists. Prevent duplicates at the point of entry rather than cleaning up after the fact.

Cross-Reference Resolution

Given a source system key (e.g., SAP customer number), use Source Read to find the corresponding master record and then resolve to another source system's key — effectively translating IDs across systems.

MDM SaaS APIs and common use cases — case study and demo

MDM SaaS APIs and Common Use Cases with Case Study and Demo (PDF) — End-to-end use cases, case study, and demo walkthrough for the B360 REST API and this connector.

Supported Error Types

Error TypeDescription
B360:CLIENT_ERROR4xx HTTP responses from the B360 API
B360:SERVER_ERROR5xx HTTP responses from the B360 API
B360:TIMEOUTRequest timed out (SocketTimeoutException)
B360:CONNECTIVITYGeneral connectivity failure

Requirements

  • Mule Runtime: 4.6.0 or later
  • Java: 8, 11, or 17
  • Informatica Cloud (IICS): Active account with MDM Business 360 entitlement

Learn More

Released under the MIT License.