XMLNSC domain

IBM® Integration Bus uses the XMLNSC parser to read and write messages that belong to the XMLNSC domain.

The XMLNSC parser is a flexible, general-purpose XML parser that offers high performance XML parsing and optional XML schema validation. The XMLNSC parser has a range of options that make it suitable for most XML processing requirements. The XMLNSC parser uses either XML schema files (.xsd) from an IBM Integration Bus library, or message definitions in a message set to parse and serialize messages. A message definition (.mxsd) file is an annotated XML schema file.

The TX Map node can consume and create messages in the XMLNSC domain.

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

  1. In the IBM Integration Development perspective, model the message format as either:
    • A global element in an XML schema file (.xsd) within a broker library
    • A message in a message definition (.mxsd) file within a broker message set, typically by importing an XML schema (.xsd) file.
    For detailed instructions, see the IBM Integration Bus product documentation.
  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 either the message definition (.mxsd) file or the XML schema (.xsd) file as the Type tree. Select the group that corresponds to the message as the Type.
  3. Switch to the IBM Integration Development perspective, and create a message flow that contains 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 Message Domain as XMLNSC.
    2. If the message is created by an output card, configure the corresponding TX Map node output terminal to specify the Message Domain as XMLNSC. 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 along with the message set.
If the message is to be consumed by an input card, at run time the input node of the message flow starts the XMLNSC parser. The XMLNSC parser uses the XML schema or the message set to create a message tree from the message bit stream. The TX Map node receives the XMLNSC domain message tree and passes it to the input card. When the map runs, it uses the tree directly.

If the message is to be created by an output card, at run time the map creates the XMLNSC 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 XMLNSC parser. The XMLNSC parser uses the XML schema or the message set to serialize the message tree.

You do not have to create an equivalent type tree for the XML message. The map is built with the message definition file or XML schema. At run time, the map operates directly on the XMLNSC domain message tree, and not on a bit stream.