At the JMSInput node, a message is received as a Java object and not as a bit stream wire format (as would be the case with an MQInput node). The message does not populate an MQMD and RFH2 header, but instead populates a new message tree that represents a JMS message in a more native way.
To represent a JMS message in a message tree, a new canonical form has been created. This new message tree allows for representation of JMS message header data, and message properties. The JMS message tree is in a format that is recognizable to Java programmers.
The JMS message
For details about the structure and content of the JMS message tree, see Representation of messages across the JMS Transport.
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac24881_ |