Running Composite XML Transaction Samples
About this task
The sample composite XML transactions are available in the folder mdmsamples\com.ibm.mdm.sample.composite.xml\test\.
There are several test cases for composite transactions included with the InfoSphere MDM samples (mdmsamples\com.ibm.mdm.sample.composite.xml\test\):
- RRD composite transactions.
RRD FE for RoV has a requirement to update DataAssociation (DWLDataAssociationBObj) and add/update AssociatedObjects (DataAssociationObjectBObj in a single unit of work. Currently no composite transactions exist in the RoV Admin Services back-end to carry out such a request. The XML Composite Framework can be used to provide composite functionality for RRD front-end.
- UpdateParty using PartyAdminSysKey
To update a party, at least two transactions, getPartyByAdminSysKey and updateParty, must be run. The getPartyByAdminSysKey retrieves all the objects to be updated. The Composite Framework then retrieves the required keys from the response objects of the get transaction and plugs them into the request objects of the updateParty transaction based on the condition clause.
A set of sample request and response XML files (updatePartyByAdminSysKeyCompTxnSample.xml and ResponseupdatePartyByAdminSysKeyCompTxnSample.xml) are provided in the InfoSphere MDM Samples folder (mdmsamples\com.ibm.mdm.sample.composite.xml\test\).
For details of this sample, see Using the update party by party equivalency sample.
- UpdateContract using adminSysKey.
The updateContractCompTxnSample composite XML transaction is similar to the UpdateParty using PartyAdminSysKey sample. The Contract ID can be retrieved by searchContract or getContract. Two sets of request and response XML files (updateContractByAdminSysKeyCompTxnSample_1.xml, ResponseupdateContractByAdminSysKeyCompTxnSample_1.xml, updateContractByAdminSysKeyCompTxnSample_1.xml and ResponseupdateContractByAdminSysKeyCompTxnSample_2.xml) are provided in the InfoSphere MDM Samples folder (mdmsamples\com.ibm.mdm.sample.composite.xml\test\).
- AddContract using PartyAdminSysKey.
The client has a requirement to add a new contract. The Party involved in this agreement, already exists in InfoSphere MDM but the partyId is not available to addContract Transaction. Instead PartyAdminSysKey (TCRMAdminContEquivBObj) is used to identify the party ID.
- UpdatePartyAddress using PartyId and AddressUsageType.
The client has a requirement to update the party address for a party. PartyAddressIdPK is not available for updatePartyAddress. Instead, PartyId is used for getAllPartyAddresses() and then a conditional check on addressusagetype is done to identify PartyAddressIdPK
- AddParty to include PartyInteraction and Grouping Association.
The client has a requirement to include Party Interaction and Grouping Association as a part of addParty. Currently InfoSphere MDM does not provide this functionality.