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.
Create a message set project and a message set called MAPPING3_SIMPLE_xml.
On the message set parameters page, set the
Runtime Parser to XML.
Create a message definition file called SIMPLE.
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
Create a message flow called addev4, which contains the following
mapping: MQInput -> Mapping -> MQOutput.
On the MQInput node Default properties page,
set the Message Domain to XML.
Open the map and select addev4 as both source and target.
Map the inputs to the corresponding outputs, as shown in this example:
str1 --- str1
int1 --- int1
bool1 --- bool1
Create an instance message with no RFH2 header and the following
data:
a message set called MAPPING3_SIMPLE_xml, which contains the message addev4
a message flow called addev4, which contains the mapping addev4_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 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.
Create a broker archive (bar) file called addev4.
Add the message flow called addev4 to the bar file.