WebSphere WebSphere Application Server Express, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Managing WebSphere Version 5 JMS use of WebSphere version 6 messaging resources

This topic describes tasks that enable WebSphere Application Server Version 5 J2EE applications to use messaging resources of the WebSphere Application Server version 6 default messaging provider.

Why and when to perform this task

This JMS interoperation from WebSphere Application Server version 5 to version 6 is enabled and managed by a WebSphere MQ client link created on the WebSphere Application Server version 6 node. Each WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by Version 51 JMS applications and the WebSphere Application Server version 6 protocols used by messaging engines.

This JMS interoperation is only intended as an aid to the migration from the embedded messaging in WebSphere Application Server Version 5 to the default messaging provider in WebSphere Application Server version 6. For more information about migrating from the embedded messaging provider, see Migrating from Version 5 embedded messaging.

Note: WebSphere Application Server version 6 J2EE applications can use messaging resources of the WebSphere Application Server Version 5 default messaging provider without any need for a WebSphere MQ client link.

Consider the JMS interoperation scenario, of a Version 5 JMS application using JMS resources provided by the default messaging provider on a WebSphere Application Server version 6 node, shown in the following figure Figure 1. The Version 5 JMS queue is backed by a bus queue, as normal for a version 6 JMS queue, but there is no configured link between the Version 5 JMS queue and 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. This figure shows an example single-node scenario at WebSphere Application Server version 6. A Version 5 JMS application uses a Version 5 JMS queue connection factory to connect to the version 6 node and to pass messages to a bus queue. The bus queue has been created and assigned to the 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 Version 5 JMS application and the bus queue.
This figure shows a WebSphere MQ client link on a messaging engine being used to pass messages between a Version 5 JMS application and a bus queue.  For more information, see the text accompanying the figure.

You can use the following tasks to manage WebSphere Version 5 JMS use of WebSphere version 6 JMS resources.

The WebSphere Version 5 application can continue to access the Version 5 JMS resources, which are now implemented through the WebSphere Application Server version 6 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 Version 5 JMS applications and the WebSphere Application Server version 6 protocols used by messaging engines.

For more information about managing WebSphere Version 5 JMS use of WebSphere version 6 JMS resources, see the related tasks.
Related concepts
Client access to JMS resources
Related tasks
Maintaining Version 5 default messaging resources
1 To make reading easier in this topic, the abbreviation "Version 5" is sometimes used to refer to "WebSphere Application Server Version 5" and "version 6" is used to refer to "WebSphere Application Server version 6". For example, "version 5 JMS resources" refers to JMS resources provided by WebSphere Application Server Version 5.

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjq0000_.html

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