WebSphere MQ JMS bindings: a general perspective

The WebSphere® MQ JMS service provides integration with WebSphere MQ based JMS providers.

WebSphere MQ administrative tasks

The WebSphere MQ Administrator is expected to create the underlying Queue Manager and Queues in WebSphere MQ which the WebSphere MQ JMS Bindings will utilize before running an application containing these bindings.

WebSphere MQ JMS Import bindings

The WebSphere MQ JMS Import binding provides outbound connectivity from Service Component Architecture (SCA) applications to WebSphere MQ based JMS providers. Please ensure that you are using a supported version of WebSphere MQ. Detailed hardware and software requirements can be found on the IBM support pages.

Two types of WebSphere MQ JMS Import binding are supported:

For both one-way and two-way usage scenarios dynamic and static header properties can be specified, some of these properties have special meanings to the SCA JMS Runtime.

WebSphere MQ JMS Export bindings

The WebSphere MQ JMS Export binding provides inbound connectivity from WebSphere MQ based JMS provider to the SCA System.

An MDB is deployed to listen to requests incoming to the receive destination specified in the export binding. The destination specified in the send field is used to send the reply to the inbound request if the invoked service provides a reply. The destination specified in the JMSReplyTo field of the response message overwrites the destination specified in the send field.

WebSphere MQ JMS message delivery and the failed event manager

WebSphere MQ JMS bindings are configured by default to have a maximum retries value of 1. The WebSphere MQ JMS bindings require a value for the maximum retries of at least 1 for the underlying listener ports used for an incoming message. This is required for the receive destinations on both Import and Exports to enable the failed event manager to store failed messages. If you set the maximum retries value to less than 1, messages to the target component that fail will not be available in the failed event manager. A failure in the target component constitutes a runtime exception.


Last updated: Wed 06 Dec 2006 07:08:08

(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)