Other domains

IBM® Integration Bus provides several other domains, such as XMLNS, MIME, JMSMap and JMSStream, and accompanying parsers to parse and serialize messages that belong to them.

The TX Map node can consume and create messages in these domains.

To create a message flow that uses the TX Map node to create or consume messages in these domains, do the following steps within the IBM Integration Toolkit:

  1. In the Transformation Extender Development perspective, use Type Designer to model the message format as a type in a type tree (.mtt) file.
  2. 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 type tree (.mtt) file as the Type tree, and the type as the Type.
  3. Switch to the IBM Integration Development perspective, and create a message flow containing a TX Map node that uses your map.
    1. If the message is consumed by an input card, configure the input node of the message flow to specify the selected Message Domain.
    2. If the message is created by an output card, configure the corresponding TX Map node output terminal to specify the selected Message Domain. 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.
  4. Complete the message flow, and deploy it to the broker.
If the message is to be consumed by an input card, at run time the input node of the message flow starts the selected parser. The parser creates a message tree from the message bit stream. The TX Map node receives the message tree, serializes it back to a bit stream, and passes it to the input card. The map runs and uses the type tree to parse the bit stream.

If the message is to be created by an output card, at run time the map creates a bit stream. The TX Map node starts the selected parser to create a message tree from the bit stream, and propagates it to the next node in the message flow. The output node of the message flow starts the selected parser, which serializes the message tree.

The map is built by using the type tree. At run time, the map uses the type tree to parse the message bit stream on input, and serialize it on output.