Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the default messaging provider


Enable WAS v5.1 JMS usage of messaging resources in later versions of the product

To enable JMS applications developed for WAS v5.1 to use messaging resources of the default messaging provider, a WebSphere MQ client link is created on the node of the later version of the product. Each WebSphere MQ client link presents itself as a queue manager and transforms between the WebSphere MQ client protocols used by v5.1 and the protocols used by the default messaging provider in later versions.

Throughout this topic, the abbreviation " Version 5.1 " refers to " WAS v5.1 ". For example, " Version 5.1 JMS resources" refers to JMS resources provided by WAS v5.1.

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

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

Applications running in later versions can use the messaging resources of the v5.1 messaging provider without any need for a WebSphere MQ client link.

The following figure shows a JMS application running on v5.1 and using JMS resources provided by the default messaging provider on a v7.0 node. The JMS queue hosted by v5.1 is backed by a service integration bus queue, which is normal for a JMS queue hosted by v7.0, but there is no configured link between the v5.1 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. WAS v5.1 JMS application scenario


Procedure


Results

The application running on v5.1 can continue to access the JMS resources on the later level of the product, which are now implemented through the default messaging provider, as shown in the figure WAS v5.1 JMS application scenario. The JMS application communicates with the v5.1 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 v5.1 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 developed for WAS v5.1 and the protocols used by messaging engines on the later version.
Client access to JMS resources
Maintain v5 default messaging resources
WebSphere MQ client links [Collection]
WebSphere MQ client link [Settings]

+

Search Tips   |   Advanced Search