Supported message domains

A parser is a program that interprets the bit stream of an incoming message and creates an internal representation of the message in a tree structure. The parser also regenerates a bit stream from the internal message tree representation for an outgoing message. Each parser is suited to a particular message domain. A message domain is class of messages, such as fixed-length binary messages or XML messages. IBM® Integration Bus supplies a range of parsers to parse and write message formats.

The following table lists the domain that you should use for the specified scenario.

Table 1. Message scenarios and domain types
Scenario	Domain
Message is modeled by type tree (.mtt), or XML Schema (.xsd), or broker message definition (.mxsd). Only the map processes the message content. The message is opaque to native broker nodes in the message flow.	BLOB
Message is a business object from a WebSphere® adapter, and is modeled by broker message definition (.mxsd).	DataObject
Message is not XML or a business object, and is modeled by Data Format Description Language (DFDL) schema.	DFDL
Message is not XML or a business object, and is modeled by broker message definition (.mxsd).	MRM
Message is XML, and is modeled by XML Schema (.xsd) or broker message definition (.mxsd).	XMLNSC

The TX Map node handles messages that belong in the following message domains, and these messages can be used as input to, and output from, map cards. The steps you take to create your message flow, and the runtime behavior of the TX Map node, depend on the domain that you selected.