Develop a message flow and message model for simple and complex
element mapping
This is the first stage of the scenario
to perform simple message enrichment.
This topic demonstrates how to develop a message flow and message
model for simple and complex element mapping, where there is the same
source and target, a different source and target, or an attribute
source and target. This task also involves changing field values and
creating an instance document.
From the Broker Application Development perspective,
create the following resources:
Create a message called addev1 that has the following structure:
addev1
ssat (xsd:string) local attribute
ssel (xsd:string) local element
dsel1 (xsd:string) local element
atel local complex element
latt (xsd:string) attribute
cel1 local complex element
intel (xsd:int) local element
strel (xsd:string) local element
dsel2 (xsd:string) global element
cel2 (cel2ct) global complex type
intel (xsd:int) local element
fltel (xsd:float) local element
Create a message flow project called MAPPING3_SIMPLE_flows.
Create a message flow called addev1 that contains the following
mapping: MQInput -> Mapping -> MQOutput.
Open the map in the Message Mapping
editor and select message
addev1 as both source and target
Expand all levels of both messages and wire the elements
as shown:
message set MAPPING3_SIMPLE_messages, which you have populated
with message addev1
message flow addev1 in project MAPPING3_SIMPLE_flows, which contains
the mapping addev1_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 second 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
addev1.
Add the message set MAPPING3_SIMPLE_messages and the message
flow addev1 to the BAR file.