Retrieve MBM Identifier
M3 Business Messages (MBM) contains UUID as an identifier that is used for tracking in M3/BE.
M3 sends MBM messages through MvxNGIn or MvxTGIn to EC. Inappropriate detection or improperly configured message agreement may cause errors. EC refers to the MBM Identifier to update the BE where a particular MBM message encountered an error in EC. Then, you can set up a reply message back to M3 on the status of the MBM based on its identifier indicating that it failed to process the message. Then, Outbound MBM Status pulls up the MBM Identifier.
There are two ways to set MBM Identifier Error Handling in EC, one through the Agreement and the other through the Channel. Although MBM Identifier is not to be used in an Agreement, it can be used in error handling.
Agreement
The MBM identifier must be in the manifest when checking through an Agreement.
A properly set Agreement has a saved MBM Identifier in the manifest. If an Xpath value is found, the manifest is automatically populated. You verify the populated manifest in PA menu > Manage> Advanced > Populating Targets tab.
If MBM identifier is set in the manifest, this error handling process will retrieve the identifier.
Otherwise, this error handling process will parse the value of the node /MvxEnvelope/MBMIdentifier
to look for the MBM identifier.
Channel
When messages pass through a channel, EC will try to find the MBM Identifier of messages in error on a channel level.