WebSphere Message Brokers
File: ac24800_
Writer: John Cooper

Concept topic

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

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.

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 Message Broker supports Java 5 (also known as Java 1.5).

The following sample is provided to help you start using the WebSphere Broker JMS Transport. You can view samples only when you use the information center that is integrated with the Message Brokers Toolkit.
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
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:33

ac24800_ This topic's URL is: