Configure the JMSInput node properties to specify the message domain that will be used to parse the JMS message payload.
When the JMSInput node creates a message tree from the JMS message payload, the appropriate message domain for that payload must be used. Therefore, the JMSInput node must know the type of JMS message that it expects to receive. The JMSInput node extracts the payload from the JMS message using the appropriate JMS API, then passes the payload data to the parser for the domain. The parser creates the body portion of the message tree.
The message domain is derived according to the following criteria and in the following order of precedence:
Message domain | Valid JMS message types | ||||
---|---|---|---|---|---|
BytesMessage | TextMessage | MapMessage | StreamMessage | ObjectMessage | |
BLOB | • | • | • | ||
XMLNS | • | ||||
XMLNSC | • | ||||
MRM | • | • | |||
JMSMap | • | ||||
JMSStream | • | ||||
MIME | • | • | |||
IDOC | • | • | |||
XML | • |
The JMSType header field must be set according to the URI format shown in the following table. The domain in the mcd: string can be uppercase or lowercase.
JMSType | Message domain |
---|---|
mcd://BLOB | BLOB |
mcd://MRM/[set]/[type]/[?format=fmt] | MRM |
mcd://XMLNS | XMLNS |
mcd://XMLNSC/[set] | XMLNSC |
mcd://IDOC/[set]/[?format=fmt] | IDOC |
mcd://MIME | MIME |
mcd://XML | XML |
JMS message type | Message domain |
---|---|
TextMessage | XML |
BytesMessage | BLOB |
MapMessage | JMSMap |
StreamMessage | JMSStream |
ObjectMessage | BLOB |