Available parsers

A parser is invoked by the broker only when that parser is required. The parser that is invoked depends upon the parser that has been specified.

For certain implementation functions, it might be necessary to specify the name of a parser supplied with WebSphere Message Broker. For example, functions include:
  • cniCreateElementAfterUsingParser
  • cniCreateElementAsFirsthChildUsingParser
  • cniCreateElementAsLastChildUsingParser
  • cniCreateElementAsLastChildFromBitstream
  • cniCreateElementBeforeUsingParser

When using these functions, you must specify the correct class name of the parser. The following table provides a summary of the parsers, root element names, and class names for different headers.

Parser Root element name Class name
BLOB BLOB NONE
IDOC IDOC IDOC
JMSMap JMSMap JMS_MAP
JMSStream JMSStream JMS_STREAM
MIME MIME MIME
MQCFH MQPCF MQPCF
MQCIH MQCIH MQCICS
MQDLH MQDLH MQDEAD
MQIIH MQIIH MQIMS
MQMD MQMD MQHMD
MQMDE MQMDE MQHMDE
MQRFH MQRFH MQHRF
MQRFH2 MQRFH2 MQHRF2
MQRMH MQRMH MQHREF
MQSAPH MQSAPH MQHSAP
MQWIH MQWIH MQHWIH
MRM MRM MRM
Properties Properties PropertyParser
SMQ_BMH SMQ_BMH SMQBAD
XML XML xml
XMLNS XMLNS xmlns
XMLNSC XMLNSC xmlnsC

When using the MQMD parser, the MQMD is assumed to be a V2 MQMD.

You can also create your own user-defined parsers, or make use of user-defined parsers that have been supplied by third party vendors.

Related concepts
User-defined parsers
User-defined parser life cycle
Planning user-defined parsers
Related reference
XML and MRM parser constants
C language user-defined parser API