Use the WebSphere® Broker
JMS Transport to send and receive JMS messages. The WebSphere Broker
JMS Transport uses JMS as the connection protocol for sending and receiving messages in a Java™ environment.
The exchange of JMS messages is implemented by two built-in nodes, the JMSInput node and the JMSOutput node. These two nodes allow a message flow to receive messages from JMS destinations, or to send messages to JMS destinations. These destinations are accessible through a connection to a JMS provider.
Two transformation nodes allow the JMSInput and JMSOutput nodes to work with nodes that expect a propagated message to contain an MQMD (and MQRFH2) header. These nodes are the JMSMQTransform node and the MQJMSTransform node:
You can include JMS nodes in applications where messages are produced and consumed from a variety of JMS destinations. In sending and receiving messages, the JMS nodes behave like JMS clients.
The JMS nodes work with the WebSphere MQ JMS provider, WebSphere Application Server Version 6.0, the IBM® Service Integration Bus, and any JMS provider that conforms to the Java Message Service Specification, version 1.1. WebSphere Event Broker supports Java Version 1.4.2 (the default version) and Java 5 (also known as Java 1.5). If you want to use Java 5, configure your environment as described in Setting up a command environment (for distributed systems) or Customizing the version of Java on z/OS.
To use the WebSphere Broker JMS Transport, you must deploy a message flow that contains a JMSInput node or a JMSOutput node. You can also include a JMSMQTransform node or an MQJMSTransform node.
The JMS messages must conform to the Java Message Service
Specification, version 1.1.