Changing Message Choreography

You can use MDM to work with specific datapools.

Procedure

  1. Update Rulebase to support New Message Type. For MDM to support a new message type, the first step is to update the rbformatattributes_gdsn.xml rulebase file so the new synchronization format is detected in the synchronization profile UI.
    • Update the $MQ_COMMON_DIR/standard/rulebase/rbformatattributes_gdsn.xml file.
  2. Update Map file to support New Message Type. The next step is to update the map file to support the new message type.
    • Update the datapool specific map file from the $MQ_COMMON_DIR/standard/maps folder.
    • For more details on datapool specific map files for different message types, refer to GDSN-Specific Maps.
  3. Update Sync Operation Identifier Rulebase. Next, update the datapool specific sync operation identifier rulebase to identify datapool specific sync operations.
    • Update the appropriate file in:
$MQ_COMMON_DIR/standard/rulebase.
    • For 1WorldSync, the rulebase name is rbtransorasupplier.xml
  4. Status Derivation. When a datapool receives a message from the MDM supplier or retailer applications, a response is sent to the appropriate application. Based on the response, MDM updates the status of the record. For example, if an "Item add" message is sent, the record is internally updated based on the response received from the datapool. You can update the status derivation.
    • To add or to update an operation from the UI on the supplier or retailer applications, change the constraints from the following file
$MQ_COMMON_DIR/standard/rulebase/rbsyncstatusupdatederivation.xml.
    • To update from the UI, change the constraints in the $MQ_COMMON_DIR/standard/rulebase/rbsyncstatusupdatederivation.xml update statusderivation.xml file.
    • To update record status derivation on receiving a response from the datapool, change the constraints in the $MQ_COMMON_DIR/standard/rulebase/statusderivation.xml file.
  5. Message Handler Selection. To change the message handler selection, properties similar to the following should be updated in $MQ_HOME/config/gdsn.config
    • com.tibco.cim.connector.plugin.mapping.handlemessaging.supplier.*1sync*=com.tibco.cim.init.connector.plugin.handlemessaging.supplier.1Sync
    • com.tibco.cim.init.connector.plugin.handlemessaging.supplier.1Sync.class=com.tibco.mdm.gdsn.integration.connector.TransoraMessagingHandler