The JMSInput and JMSOutput nodes expect JMS messages
and therefore expect a native JMS message tree representation.
The following two nodes are available when a
WebSphere MQ JMS
message tree is expected but the representation is that of a JMS message tree:
- The JMSMQTransform node
- The MQJMSTransform node
These nodes do not have any configurable attributes. The
JMSMQTransform node
transforms a native JMS message tree to a
WebSphere MQ JMS
message tree, and the
MQJMSTransform node
performs the transformation in the opposite direction. The following
diagram provides an overview of the mapping scheme that is used:

The above mapping uses the same scheme as the WebSphere MQ JMS
provider to convert between a JMS message and an MQMD or MQRFH2 message.
When transforming between a
WebSphere MQ message
tree and a native JMS message tree, the transformation nodes copy elements
from different parts of a message tree.
- For a WebSphere MQ JMS message tree:
Elements
are taken from the MQMD, MQRFH2, and UserData, and are copied into the appropriate
JMS folders.
- For a native JMS message tree:
Elements are taken from the JMS header
and properties, and are copied into the appropriate MQMD and MQRFH2 folders.
Example message flow scenario: JMSInput node
to MQOutput node
- A JMSInput node is configured
to subscribe to Topic ABC.
- An application that is connected to the JMS server publishes on topic
ABC.
- A publication is received at the JMSInput node.
- The node extracts data from the JMS message.
- The JMS message is passed to the JMSMQTransform node
where the message is converted to an MQ message.
- The MQOutput node receives
the MQ message, and publishes the message on a WebSphere MQ queue.
The final destination is a WebSphere MQ queue,
and therefore the message must pass through a JMSMQTransform node
to convert the message tree to a WebSphere MQ JMS
format before it reaches the MQOutput node.
Example message flow scenario: MQInput node to JMSOutput node
- An MQInput node receives a
message from a WebSphere MQ queue.
- The MQInput node creates an
MQ message.
- The MQ message is passed to the MQJMSTransform node
where the message tree is converted to a JMS format.
- The JMSOutput node receives
the JMS message and publishes the JMS message on Topic XYZ.
Note: These two examples are not intended to be exclusive, but demonstrate
the range of solutions that you can achieve when you use the JMS Transport.
For example, although it is not shown here, the message can be passed to a
Compute node or a
JavaCompute node
and the contents can be modified as required.
Refer to the following sample
for examples of the JMS nodes being used in message flows:
You can view samples only when you use the information center
that is integrated with the Message Brokers Toolkit.