Which body parser should you use?

The characteristics of the messages that your applications exchange indicate which body parser you must use.

WebSphere® IBM® Integration provides a range of message parsers. Each parser processes either message body data for messages in a particular message domain (for example, XML), or particular message headers (for example, the MQMD).

Review the messages that your applications send to the integration node, and determine to which message domain the message body data belongs, using the following criteria as a guide.

If your application data uses SOAP-based web services, including SOAP with Attachments (MIME) or MTOM

Use the SOAP domain. The SOAP domain has built-in support for WS-Addressing and WS-Security standards.

If your application data uses JSON format, as maybe used in RESTful web services

Use the JSON domain.

If your application data is in XML format other than SOAP

The domain that you use depends on the nature of the XML documents and the processing that you want to perform. See Which XML parser should you use?

If your application data comes from a C or COBOL application, or consists of fixed-format binary data

Use the DFDL domain. You can also use the MRM domain with a Custom Wire Format (CWF) physical format.

If your application data consists of formatted text, perhaps with field content that is identified by tags, or separated by specific delimiters, or both

Use the DFDL domain. You can also use the MRM domain with a Tagged/Delimited String (TDS) physical format.

If your application data is created using the JMS API

The domain that you use depends on the type of the JMS message. For a full description of JMS message processing, see JMS message as input.

If your application data is from a WebSphere Adapter such as the adapters for SAP, PeopleSoft, or Siebel

Use the DataObject domain.

If your application data is in SAP text IDoc format, such as those exported using the WebSphere MQ Link for R3

Use the DFDL domain. You can also use the MRM domain with a Tagged/Delimited String (TDS) physical format.

If your application data is in MIME format other than SOAP with Attachments (for example, RosettaNet)

Use the MIME domain. If the message is multipart MIME, you might have to parse specific parts of the message with other parsers. For example, you might use the XMLNSC parser to parse the XML content of a RosettaNet message.

If you do not know, or do not have to know, the content of your application data

Use the BLOB domain.