Develop a message flow and message model for a simple message without an RFH2 header

Before you start
This is the seventh stage of the scenario to perform simple message enrichment. This topic demonstrates how to develop a message flow and message model for a simple message without an RFH2 header.
  1. Create a message set project and a message set called MAPPING3_SIMPLE_xml.
  2. On the message set parameters page, set the Runtime Parser to XML.
  3. Create a message definition file called SIMPLE.
  4. Create a message called addev4, which has the following structure:
    addev4
       str1                   (xsd:string)  local element
       cel                     local complex element
           int1                (xsd:int) local element
           bool1             (xsd:boolean) local element
  5. Create a message flow called addev4, which contains the following mapping: MQInput -> Mapping -> MQOutput.
  6. On the MQInput node Default properties page, set the Message Domain to XML.
  7. Open the map and select addev4 as both source and target.
  8. Map the inputs to the corresponding outputs, as shown in this example:
    str1 --- str1
    int1 --- int1
    bool1 --- bool1
  9. Create an instance message with no RFH2 header and the following data:
    <addev4>
    <str1>this</str1>
    <cel>
    <int1>452</int1>
    <bool1>0</bool1>
    </cel>
    </addev4>
You have created the following resources:
Now deploy the message set and message flow.

Deploy the message set and message flow

This is the final stage of the scenario to perform simple message enrichment. This topic demonstrates how to deploy the message set and message flow and run the data through the broker.
  1. Create a broker archive (bar) file called addev4.
  2. Add the message flow called addev4 to the bar file.
  3. Deploy the bar file to the broker.
  4. Put the instance document on the input queue.
The output message looks like this:
<addev4>
<str1>this</str1>
<cel>
<int1>452</int1>
<bool1>0</bool1>
</cel>
</addev4>
You have completed the scenario.