This topic contains sections marked as revised for this release

WebSphere Message Brokers
File: ac00595_
Writer: Karen Cameron

Concept topic

This build: July 31, 2007 21:16:53

Which parser should you use?

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

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

Review the messages that your applications send to the broker, and determine to which message domain the message body data belongs, so that you can either include the correct headers in the message, or configure the input node of the message flow appropriately.

If your application data is in XML format
Use the XMLNSC domain, or the XMLNS domain, or the XML Wire Format in the MRM domain.

See XML messages in the MRM and XML domains for more details about the capabilities of these domains.

If your application data comes from a C or COBOL application, or consists of fixed-format binary data (possibly including null-terminated strings)
Use the Custom Wire Format in the MRM domain.
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 Tagged/Delimited String format in the MRM domain.
If your application data is created using the JMS API
The domain you use depends on the type of the JMS message. For a full description of JMS message processing, see WebSphere Broker JMS Transport.
If your application data is in SAP IDoc format
Use the IDOC domain.
If your application data is in MIME format (for example, SOAP with Attachments, or RosettaNet)
Use the MIME domainStart of change or, if applicable, the SOAP domainEnd of change. You might need to parse specific parts of the message with other parsers. For example, you might parse the root of a SOAP with Attachments message using the MRM XML parser.
Start of changeIf your application data uses SOAP-based Web servicesEnd of change
Start of changeUse the SOAP domain. This domain provides a common WSDL-based logical tree format for working with Web services, independent of physical bitstream format.End of change
If you do not know, or do not need to know, the content of your application data
Use the BLOB domain.
Related concepts
MRM parser and domain
XML parsers and domains
JMS parser and domains
IDOC parser and domain
MIME parser and domain
BLOB parser and domain
Start of changeSOAP parser and domainEnd of change
Message modeling
XML messages in the MRM and XML domains
Related tasks
Developing message flows
Developing ESQL
Developing Java
Related reference
WebSphere Broker JMS Transport
Built-in nodes
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:16:53

ac00595_ This topic's URL is: