WebSphere Broker JMS Transport

The WebSphere Broker JMS Transport uses JMS as the connection protocol for sending and receiving messages in a Java environment.

The WebSphere Broker JMS Transport can be used to support the following operations:

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 connection to a JMS provider.

Two transformation nodes allow the JMSInput and JMSOutput nodes to inter-operate 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.

Start of changeThe 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 Message Broker supports Java Version 1.4.2 (the default version) and Java 1.5. If you want to use Java 1.5, configure your environment as described in Setting up a command environment (for distributed systems) or Customizing the level of Java on z/OS.End of change

The JMS Nodes sample is provided to help you start using the WebSphere Broker JMS Transport.

Related concepts
Support for JMS messages
Simplified JMS message representation
JMS message transformation
Connection to different JMS providers
Related reference
JMSInput node
JMSOutput node
JMSMQTransform node
MQJMSTransform node