WebSphere Message Brokers
File: ac24881_
Writer: John Cooper

Concept topic

This build: July 31, 2007 21:19:46

Simplified JMS message representation

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 diagram depicts the JMS message tree that is used by the JMSInput and JMSOutput nodes

For details about the structure and content of the JMS message tree, see Representation of messages across the JMS Transport.

Related concepts
JMS message transformation
Related reference
JMS message types
JMS message structure
JNDI administered objects
JMS message for output
JMSInput node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:19:46

ac24881_ This topic's URL is: