WebSphere Message Brokers
File: ar25249_3_
Writer: Cerys Giddings

Task topic

This build: July 31, 2007 21:36:18

Develop a message flow and message model for a target-only element

Before you start
This is the third stage of the scenario to perform simple message enrichment. This topic demonstrates how to develop a message flow and message model for a target-only element. It also involves attributing a mapping and creating an instance document.
  1. Create a message called addev2, which has the following structure:
    addev2
        matt             (xsd:string) local attribute
        ssel              (xsd:string)  local element
        csel              local complex element
            elatt          (xsd:string)  local attribute
  2. Create a second message called trigger, which has the following structure:
    trigger
       start               (xsd:string) local element
  3. Create a message flow called addev2, which contains the following mapping: MQInput -> Mapping -> MQOutput.
  4. Open the map and select trigger as the source and addev2 as the target.
  5. In the Spreadsheet pane, expand the target message fully and set the target fields as shown:
    matt    |   'first attribute'
    ssel     |   'string element'
    elatt     |   'second attribute'
  6. Expand the Properties folder in the Spreadsheet pane and set the following value:
    MessageType   |   'addev2'
  7. Create an instance document with the appropriate RFH2 header and the following data:
    <trigger>
    <start>yes</start>
    </trigger>
You have created the following resources:
Now deploy the message set and message flow.

Deploy the message set and message flow

This is the fourth 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 addev2.
  2. Add the message set MAPPING3_SIMPLE_messages and the message flow addev2 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:
<addev2 matt="first attribute">
<ssel>string element</ssel>
<csel elatt="second attribute"></csel>
</addev2>
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:36:18

ar25249_3_ This topic's URL is: