Enabling proxy communication with IBM Master Data Management after migration

The IBM Master Data Management migration proxy service provides a compatibility layer between InfoSphere MDM and the IBM Master Data Management service. Organizations migrating from InfoSphere MDM to IBM Master Data Management can use the proxy service to maintain existing integrations while downstream systems gradually transition to the new platform.

When you migrate from InfoSphere MDM to IBM Master Data Management, the API structures and data models differ significantly. Downstream systems that rely on existing InfoSphere MDM interfaces can take time to adapt to the IBM Master Data Management APIs. In large enterprise environments, updating all dependent systems simultaneously can introduce operational risk.

The proxy service enables existing integrations to continue functioning while downstream systems progressively transition to direct integrations with IBM Master Data Management. This approach helps you to:

  • Minimize disruption to existing integrations
  • Reduce migration risk
  • Enable gradual migration of downstream applications
  • Maintain business continuity during platform transition

The migration proxy service includes the following capabilities:

  • Service translation: Converts formats between hierarchical InfoSphere MDM XML service structures and flattened IBM Master Data Management service models.
  • XML-based interfaces: Supports XML service requests and responses for backward compatibility.
  • Metadata-driven architecture: Uses extracted metadata to generate mappings and define transaction properties.
  • Domain support: Covers Party and Account domains.
  • Extension support: Handles InfoSphere MDM TCRMExtension objects and custom data models.

How the proxy service works

The proxy service gives downstream applications the flexibility to continue sending requests using the InfoSphere MDM XML format. The proxy performs the required transformations to communicate with IBM Master Data Management.

The migration proxy service acts as an intermediary layer by providing a standard API entry point that:

  1. Receives XML-based service requests from InfoSphere MDM clients.
  2. Translates the hierarchical XML structures to IBM Master Data Management service models.
  3. Integrates with backend IBM Master Data Management services through SDK calls.
  4. Converts responses back to XML format for client consumption.

This approach allows your applications to continue using InfoSphere MDM service interfaces while the underlying platform transitions to IBM Master Data Management.

Metadata approach

The migration proxy service uses a metadata-driven approach to reduce hardcoding and accelerate onboarding:

  • Metadata is extracted from your InfoSphere MDM runtime instance.
  • Mappings and transaction properties are generated once.
  • Metadata is stored in cluster or local storage for reuse.
  • New transactions can be onboarded faster with minimal configuration.

Supported InfoSphere MDM transactions

The IBM Master Data Management migration proxy service supports three primary transaction categories:

  • Inquiry transactions: Read and query operations with dynamically mapped data objects.
  • Persistent transactions: Add and update operations with predefined request and response structures.
  • Composite services: Multi-step transaction flows with orchestration logic.

For information about configuring more InfoSphere MDM transactions for use with the proxy service, see Configuring additional transactions for the migration proxy service.

Inquiry transactions

The following supported InfoSphere MDM transactions retrieve existing records from the system.

  • getPerson
  • getOrganization
  • getInteraction
  • getParty
  • getPartyBasic
  • getContactMethod
  • getConsent
  • getContract
  • getClaim
  • getPartyWithContracts
  • getAllPartyIdentifications
  • getPersonName
  • getOrganizationName
  • getPartyValue
  • getFSParty
  • getPartyAddress
  • getPartyAlert
  • getPartyIdentification

Add transactions

The following supported InfoSphere MDM transactions create new records in the system.

  • addPerson
  • addOrganization
  • addInteraction
  • addParty
  • addPersonName
  • addOrganizationName
  • addPartyAddress
  • addPartyValue
  • addPartyAlert
  • addPartyIdentification
  • addContract
  • addClaim
  • addConsent

Update transactions

The following supported InfoSphere MDM transactions update existing records.

  • updateClaim
  • updateParty
  • updatePartyAlert
  • updatePartyAddress
  • updatePerson
  • updatePersonName
  • updatePartyValue
  • updateInteraction
  • updateOrganization
  • updatePartyIdentification
  • updateConsent
  • updateContract

Search transactions

These following supported InfoSphere MDM transactions search for records based on provided criteria.

  • searchOrganization
  • searchParty
  • searchPerson
  • searchFSParty
  • searchConsent
  • searchContract

Maintainence transactions

The following supported InfoSphere MDM maintenance transactions support specific lifecycle operations.

  • MaintainParty

Learn more