Transaction reference
In general, each InfoSphere® MDM module (such as the Core module, Party module, and others) consists of either a Txn controller or a Finder controller component.
- Overview of the InfoSphere MDM XML interface
Transactions are processed through transaction-specific methods on each of the controller interfaces. - InfoSphere MDM transaction formats
Tx transactions transport business objects and are therefore used for all Add and Update operations. - Hybrid MDM transactions
This section describes each of the hybrid MDM transactions in detail. The business usage of the transaction is described, and the request and response details are noted. - Physical MDM transactions
This section describes each physical MDM transaction in detail. The business usage of each transaction is described, the request and response details are noted, and filter values (where applicable) are listed. - InfoSphere MDM business objects
The following business objects are used in InfoSphere MDM transactions. - InfoSphere MDM code tables
Code tables are used to store collections of values in the MDM database and can populate UI elements, such as lists, with the code table values. - Search inquiry levels
The search results returned in a search contain the basic details of each party found. There may be times when additional details are required. - Banking Objects, Transactions and Attributes
- Example of a getTransactionLog transaction
The getTransactionLog transaction is the only transaction that retrieves transaction log information from InfoSphere MDM. - Party and product relationships
- Web Services and their relationship to RMI transactions
This section provides Web Services developers with a context for how transactions and the information in the Transaction Reference Guide relate to the Web Services.
Last updated: 5 Jun 2018