WebSphere WebSphere Application Server Network Deployment, Version 6.1.x Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Managing WebSphere Application Server Version 5 JMS use of messaging resources in later versions of the product

This task enables J2EE applications running in WebSphere Application Server Version 5 to use messaging resources of the default messaging provider in WebSphere Application Server Version 6 and later versions.

Before you begin

Throughout this topic, the abbreviation "Version 5" refers to "WebSphere Application Server Version 5" and "Version 6" refers to "WebSphere Application Server Version 6". For example, "Version 5 JMS resources" refers to JMS resources provided by WebSphere Application Server Version 5.

This task refers to the default messaging provider. For related information, see Managing messaging with the default messaging provider.

JMS connectivity between the Version 5 messaging provider and later versions is enabled and managed by a WebSphere MQ client link. This does not mean that a WebSphere MQ system is involved. The Version 5 messaging provider uses WebSphere MQ client protocols, and is therefore handled as if it were a WebSphere MQ client by later versions of the product. The WebSphere MQ client link is provided only for use with JMS applications developed for WebSphere Application Server Version 5. Moreover, this JMS connectivity is only intended as an aid to migration from the Version 5 messaging provider to the default messaging provider in Version 6 and later versions. For more information about migrating from the Version 5 messaging provider, see Migrating from WebSphere Application Server Version 5 embedded messaging.

Applications running in Version 6 and later versions can use the messaging resources of the Version 5 messaging provider without any need for a WebSphere MQ client link.

About this task

To enable JMS applications running in Version 5 to use messaging resources of the default messaging provider, a WebSphere MQ client link is created on the Version 6 or later version node. Each WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by Version 5 and the protocols used by the default messaging provider in Version 6 and later versions.

The following figure shows a JMS application running on Version 5 using JMS resources provided by the default messaging provider on a Version 6 node. The JMS queue hosted by Version 5 is backed by a service integration bus queue, which is normal for a JMS queue hosted by Version 6 or later versions, but there is no configured link between the Version 5 JMS queue and the bus queue. The JMS application communicates with the bus queue through the WebSphere MQ client link and the messaging engine. To send messages to the bus queue or receive messages from the queue, the JMS application opens a connection on the WebSphere MQ client link. This is all invisible to the JMS application, but can be displayed and managed by the administrator.

Figure 1. WebSphere Application Server Version 5 JMS application scenario
A JMS application running on Version 5 uses a Version 5 JMS queue connection factory to connect to a Version 6 node and to pass messages to a bus queue. The bus queue has been created and assigned to a messaging engine, and is used to store and process messages for the JMS queue. A WebSphere MQ client link has been created for the messaging engine, and is used to pass messages between the JMS application running on Version 5 and the bus queue.
Note: If you want to send messages from a Version 5 application to a remote cell rather than within the same cell, the recommended and supported method for doing this is to use the IBM Client for JMS on J2SE with IBM WebSphere Application Server. The client is supported in WebSphere Application Server Version 5 provided that all of the following conditions apply:
  • All enterprise applications using the client package the client jar files inside the EAR file.
  • All enterprise beans jar files within the enterprise application EAR file must include the client jar files in the classpath statement in their manifest.mf file, for example, Class-Path: sibc.jms.jar sibc.jndi.jar.
  • All enterprise applications using the client must be deployed with Classloader Mode=PARENT_LAST.
IBM Client for JMS on J2SE with IBM WebSphere Application Server is available for download at http://www.ibm.com/support/docview.wss?uid=swg24012804.

Procedure

Results

The application running on Version 5 can continue to access the Version 5 JMS resources, which are now implemented through the Version 6 and later default messaging provider. as shown in the figure Figure 1. The JMS application communicates with the Version 5 JMS resources through the WebSphere MQ client link and the messaging engine. This is invisible to the JMS application. The JMS resources, a JMS queue connection factory, shown as JMS QCF(V5), and a JMS queue, shown as JMS Q(V5), are managed as Version 5 default messaging JMS resources. The new bus queue, shown as JMS Q, is managed as a resource of the service integration bus. Messages for JMS Q are stored and processed by the message point for the associated bus destination, a queue shown as Bus Q. The WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by JMS applications running on Version 5 and the protocols used by messaging engines on Version 6 and later versions.

Related concepts
Client access to JMS resources
Related tasks
Maintaining Version 5 default messaging resources

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 26 February 2009
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/tasks/tjq0000_.html

Copyright IBM Corporation 2004, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)