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.
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
Create a second message called trigger, which has the following
structure:
trigger
start (xsd:string) local element
Create a message flow called addev2, which contains the following
mapping: MQInput -> Mapping -> MQOutput.
Open the map and select trigger as the source and addev2 as the
target.
In the Spreadsheet pane, expand the target message fully and set
the target fields as shown:
Expand the Properties folder in the Spreadsheet pane and set the
following value:
MessageType | 'addev2'
Create an instance document with the appropriate RFH2 header and
the following data:
<trigger>
<start>yes</start>
</trigger>
You have created the following resources:
two messages called addev2 and trigger
a message flow called addev2, which contains the mapping addev2_Mapping.msgmap
a file that contains an instance message
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.
Create a broker archive (bar) file called addev2.
Add the message set MAPPING3_SIMPLE_messages and the message flow
addev2 to the bar file.