Building the message model for the IDOC parser
The ALE IDoc messages that are sent to, and received from, SAP applications by using the WebSphere® MQ Link for R3, can be processed by the IDOC parser, which requires a message model to interpret the data correctly. This topic describes how to build the message model.
Before you begin
The IDOC domain is deprecated. To develop new message flows, use the MRM domain with a TDS physical format when you want to process SAP ALE IDocs that are sent to the integration node by SAP R3 clients across the WebSphere MQ link for R3.
Obtaining the IDoc
About this task
Procedure
What to do next
Modeling the IDoc
About this task
Create your message model.
Procedure
Using the IDoc message model
About this task
You can now use your message model to help you to construct a message flow that processes instances of your IDoc message. You can use ESQL or Java™ to access the fields of the IDoc. You cannot use graphical maps to access the fields of the IDoc because the IDOC domain is not supported by the mapping editor.
When you set the properties of the MQInput node that is to receive your IDoc from the WebSphere MQ Link for R3, the Message Domain property must be IDOC, the Message model property must be the name of the message set, and the Message Format property must be the name of your Custom Wire Format. You do not need to set a Message Type property on the MQInput node because it is not needed by the IDOC parser.
When your message flow is complete, add the message set and the message flow to a BAR file and deploy the BAR file to an integration node integration server.
When an IDoc is received by the MQInput node, the IDOC parser processes the SAP-defined elements in the DC, then, for each DD, processes the SAP-defined elements, and calls the MRM parser to process the user-defined segment data, as described by your exported IDoc, using the CWF physical format. The MRM parser knows the Message Type property to use for the user-defined segment, because it is obtained from the SAP-defined DD field segnam by the IDOC parser.