IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Configuring resources for processing JMS messages

A number of nodes are provided in IBM® Integration Bus for processing and routing JMS messages. Follow the links in this topic to find out how to configure the JMS nodes and broker resources for processing JMS messages.

IBM Integration Bus provides the following nodes for working with JMS messages:
JMSInput node
Use a JMSInput node if the messages are received from a JMS application.
JMSOutput node
Use a JMSOutput node if the messages are sent to a JMS destination.
JMSReceive node
Use a JMSReceive node to receive JMS messages in the middle of a message flow. The JMSReceive node has a similar function to the JMSInput node, but the JMSReceive node can consume or browse JMS queues in the middle of a message flow. The result message is combined with the input message and propagated to the out terminal.
JMSReply node
The JMSReply node has a similar function to the JMSOutput node, but the JMSReply node sends JMS messages only to the reply destination that is supplied in the JMSReplyTo header field of the JMS message tree. Use the JMSReply node to treat a JMS message that is produced from a message flow as a reply to a JMS input message, and when you have no other routing requirements.
JMSMQTransform node
Use the JMSMQTransform node to transform a message with a JMS message tree into a message that has a tree structure that is compatible with the format of messages that are produced by the WebSphere® MQ JMS provider.

The JMSMQTransform node can be used to send messages to existing message flows and to interoperate with WebSphere MQ JMS and WebSphere MQ Publish/Subscribe.

MQJMSTransform node
Use the MQJMSTransform node to receive messages that have a WebSphere MQ JMS provider message tree format, and transform them into a format that is compatible with messages that are to be sent to JMS destinations.

You can use the MQJMSTransform node to send messages to existing message flows and to interoperate with WebSphere MQ JMS and WebSphere MQ Publish/Subscribe.

JMSHeader node
Use a JMSHeader node to change JMS Header_Values properties, or add, modify, or delete JMS Application properties without programming.
SOAPInput node
Use a SOAPInput node for SOAP messages received from a JMS application.
SOAPReply node
The SOAPReply node sends SOAP messages using JMS transport only to the reply destination specified in the received message. Use the SOAPReply node to treat a JMS message that is produced from a message flow as a reply to a JMS input message.
SOAPRequest node
Use a SOAPRequest node to send a SOAP request to a remote Web service. This node is a synchronous request and response node, and blocks after sending the request until the response is received.
SOAPAsyncRequest and SOAPAsyncResponse nodes
Use a SOAPAsyncRequest node with a SOAPAsyncResponse node to construct a pair of message flows that call a Web service asynchronously.
To use JMS nodes in your message flows, there are additional configuration steps in the broker environment that you might need to complete. See the following topics for information about additional configuration tasks that you might need to complete:

bz90081_.htm | Last updated Friday, 21 July 2017