How the JMSInput node derives the message domain and JMS message type.
When a JMS message is received by the JMSInput node, the message domain is derived according to the following criteria and in the following order of precedence:
In this case, the node expects to receive only the following JMS message types:
Message domain | Valid JMS message types | ||||
BytesMessage | TextMessage | MapMessage | StreamMessage | ObjectMessage | |
BLOB | X | X | X | ||
XML | X | ||||
XMLNS | X | ||||
XMLNSC | X | ||||
MRM | X | X | |||
JMSMap | X | ||||
JMSStream | X | ||||
MIME | X | X | |||
IDOC | X | X |
If a JMS message type is received, which is not valid for the message domain that is configured in the JMSInput node, the node issues a warning and backs out the message either to the source JMS provider destination, or to the backout destination.
JMSType | Broker domain | |
mcd://MRM/[set]/[type]/[?format=fmt] | MRM | |
mcd://XML | XML | |
mcd://XMLNS | XMLNS | |
mcd://XMLNSC/[set] | XMLNSC | |
mcd://IDOC/[set]/[?format=fmt] | IDOC | |
mcd://MIME | MIME |
If a JMS message type is received, which is not valid for the message domain configured in the JMSType header, the node issues a warning and backs out the message either to the source JMS provider destination, or to the backout destination.
Messages received in the MRM domain
mcd://MRM/[set]/[type]/[?format=fmt]
mcd://MRM/SWIFTXML2005/{http://SWIFT/2005}:Document/?format=SWIFT
If the JMSType field does not conform to this format, the message is handled in the BLOB domain.
The message domain is set according to the JMS message Java™ Class as follows:
JMS message type | Message domain |
TextMessage | XML |
BytesMessage | BLOB |
MapMessage | JMSMap |
StreamMessage | JMSStream |
ObjectMessage | BLOB |