IBM® Integration Bus uses
the MRM parser to read and write messages that belong to the MRM domain.
Use the MRM domain to parse and write a wide variety of
message formats. It is primarily intended for non-XML message formats,
but it can also parse and write XML. The MRM parser always uses message
definitions in a message set when parsing and serializing messages.
A message definition (.mxsd) file is an annotated XML Schema file.
The TX Map node
can consume and create messages in the MRM domain.
To create
a message flow that uses the TX Map node
to create or consume messages in the MRM domain, do the following
steps within the IBM Integration Toolkit:
-
In the IBM Integration Development perspective perspective, model the
message format as a message in a message definition (.mxsd) file, within a broker message set. For
detailed instructions, see the specific IBM Integration Bus
product documentation.
- In the Transformation Extender Development
perspective,
use Map Designer to
create a map, and add input or output cards as required. In the New
Card dialog, select the message definition (.mxsd) file
as the Type tree, and the group corresponding
to the message as the Type.
- Switch to the IBM Integration Development perspective,
and create a message flow containing a TX Map node
that uses your map.
- If the message is consumed by an input card, configure
the input node of the message flow to specify the Message
Domain as MRM, and complete the Message
Set, Type, and Format properties.
- If the message is created by an output card, configure
the corresponding TX Map node
output terminal to specify the Message Domain as MRM,
complete the Message Set, Type and Format properties,
and set the Encoding and Coded Char
Set ID properties to match the byte order (endianness)
and character set of the output data from the map.
- Complete the message flow, and deploy it to the broker
along with the message set.
At run time, if the message is to be consumed by an input
card, the input node of the message flow starts the MRM parser, which
creates a message tree from the message bit stream, using the message
set. The
TX Map
node receives the MRM domain message tree, and passes it to the input
card. When the map runs, it uses the tree directly.
At run time,
if the message is to be created by an output card, when the map runs,
it creates the MRM domain message tree directly. The TX Map node
propagates the message tree to the next node in the message flow.
The output node of the message flow starts the MRM parser, which serializes
the message tree, using the message set.
You do not have to create an equivalent type tree for
the message. The map is built using the message definition file, and
at run time, the map operates directly on the MRM domain message tree,
and not on a bit stream.