JMS message payload and appropriate parser

When the JMSInput node creates a message body from the JMS message payload, the appropriate parser for that payload is determined. Therefore, the JMSInput node must know the type of JMS message that it expects to receive. A JMS message is defined by the payload type, and the JMSInput node extracts the payload from the JMS message by using the JMS API.

The following JMSInput node properties allow you to specify the type of JMS message that the node expects to receive:
  • Message Domain
  • Message Set
  • Message Type
  • Message Format
The Message Domain can be set to one of the following values:
Domain Usage
blank This corresponds to the blank domain in an MQInput node.

The node derives the Message Domain from the JMSType header field providing that the value conforms to a proprietary URI format, see Order of precedence for deriving the message domain. If the JMSType value is blank or does not match this URI format, the node sets the Message Domain according to the JMS Message Java Class type.

Refer to Order of precedence for deriving the message domain for more information.

BLOB The node expects bit stream data from ByteMessage, ObjectMessage, or TextMessage.
XML The node expects a TextMessage with an XML payload.
XMLNS The node expects a TextMessage with an XMLNS payload.
XMLNSC The node expects a TextMessage with an XMLNSC payload.
MRM The node expects to receive a TextMessage or ByteMessage. If the message set, type, and format are not supplied in the JMSInput node then the JMSType header field must be set.
JMSMap The node expects to receive a MapMessage only.
JMSStream The node expects to receive a StreamMessage only.
MIME The node expects a TextMessage or ByteMessage with a MIME (Multipurpose Internet Mail Extension).
IDOC The node expects a TextMessage or ByteMessage with an IDOC payload.
Related reference
JMS message structure
JMS message types
Representation of messages across the JMS Transport
JMS input message header and property data
JMS Message payload
Order of precedence for deriving the message domain
JMS message for output