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.
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.
You can use the following tasks to manage WebSphere Version 5
JMS use of WebSphere version 6 JMS resources.
- Configure a WebSphere version
6 node to support WebSphere Version 5 applications that use JMS resources. If you want a WebSphere version 6 node to provide JMS destinations for
use by WebSphere Version 5 applications, complete the following steps:
- Create an application server. You can use an
existing application server on the version 6 node; for example, an application
server that a Version 5 application is to be deployed onto.
- Create a service integration
bus. You can use an existing bus.
- Add the application server
as a bus member. This automatically creates a messaging
engine on the application server.
- Create a WebSphere MQ client link on the messaging engine. Specify the following property values:
- Name
- This can be any name that is useful for your administrative purposes.
It is not used by the application environment.
- MQ channel name
- This is the name of the channel for the WebSphere MQ client link, used
to flow messages between the WebSphere Version 5 application and the bus.
This name must match the receiving channel name configured for the WebSphere
Version 5:
WAS.JMS.SVRCONN
This is the default value shown when
you first display the WebSphere MQ client link settings panel.
- Queue manager name
- This is the virtual queue manager name that is associated with the messaging
engine, and by which the messaging engine is known to WebSphere Version 5
applications. Type the queue manager name in the form:
WAS_node_name_server_name
Where:- node_name
- is the name of the WebSphere Application Server version 6 node.
- server_name
- is the name of the application server.
The correct value is shown by default when you first display
the WebSphere MQ client link settings panel.
- Default queue manager
- Select this check box if you want the MQ client link to be used as the
default for applications that cannot find a suitable MQ client link to use.
If
a WebSphere Version 5 application specifies that it wants to connect to a
non-default queue manager name, you can configure a WebSphere MQ client link
with that queue manager name. If a WebSphere MQ client link cannot be found
with the required queue manager name, the connection is rejected. Alternatively,
you can select this option on another WebSphere MQ client link, which is used
instead of rejecting the connection.
- Define a port called JMSSERVER_QUEUED_ADDRESS on the application
server. The port number must be the same used by the SIB_MQ_ENDPOINT_ADDRESS
port.
Specify the following property values:
- Port name
- For Well-known Port, select JMSSERVER_QUEUED_ADDRESS
- Host
- Type the IP address, domain name server (DNS) host name with domain name
suffix, or the short DNS host name of the WebSphere version 6 node.
- Port
- Type the port number used by the SIB_MQ_ENDPOINT_ADDRESS port. By default,
this is 5558.
- Configure a WebSphere version 6 managed node to
support WebSphere Version 5 applications that use JMS resources. If
you want a WebSphere version 6 managed node to provide JMS destinations for
use by WebSphere Version 5 applications, complete the following steps:
- Create an application server. Specify the name jmsserver.
- Create a service integration
bus. You can use an existing bus.
- Add the application
server as a bus member. This automatically creates
a messaging engine on the application server.
- Create a WebSphere MQ client link on the messaging engine. Specify the following property values:
- Name
- This can be any name that is useful for your administrative purposes.
It is not used by the application environment.
- MQ channel name
- This is the name of the channel for the WebSphere MQ client link, used
to flow messages between the WebSphere Version 5 application and the bus.
This name must match the receiving channel name configured for the WebSphere
Version 5:
WAS.JMS.SVRCONN
This is the default value shown when
you first display the WebSphere MQ client link settings panel.
- Queue manager name
- This is the virtual queue manager name that is associated with the messaging
engine, and by which the messaging engine is known to WebSphere Version 5
applications. Type the queue manager name in the form:
WAS_node_name_jmsserver
Where:- node_name
- is the name of the WebSphere Application Server version 6 node.
The correct value is shown by default when you first display
the WebSphere MQ client link settings panel.
- Default queue manager
- Select this check box if you want the MQ client link to be used as the
default for applications that cannot find a suitable MQ client link to use.
If
a WebSphere Version 5 application specifies that it wants to connect to a
non-default queue manager name, you can configure another WebSphere MQ client
link with that queue manager name. If a WebSphere MQ client link cannot be
found with the required queue manager name, the connection is rejected. Alternatively,
you can select this option on a WebSphere MQ client link, which is used instead
of rejecting the connection.
- Define a port called JMSSERVER_QUEUED_ADDRESS on the application
server. The port number must be the same used by the SIB_MQ_ENDPOINT_ADDRESS
port.
Specify the following property values:
- Port name
- For Well-known Port, select JMSSERVER_QUEUED_ADDRESS
- Host
- Type the IP address, domain name server (DNS) host name with domain name
suffix, or the short DNS host name of the WebSphere version 6 node.
- Port
- Type the port number used by the SIB_MQ_ENDPOINT_ADDRESS port. By default,
this is 5558.
- If the application looks up JMS resources in the WebSphere version
6 server JNDI, configure the JMS resources on WebSphere version 6 as V5 Default
Messaging JMS resources.
- For each JMS queue destination that the application uses, create
a V5 Default Messaging WebSphere queue destination.
- For each JMS queue destination that the application uses, create a bus destination with the same name. Assign
the bus destination to a bus member in the same bus as the jmsserver bus
member.
- Configure JMS connection factories as V5 Default Messaging WebSphere queue
connection factories and topic connection factories.
- If the application looks up JMS resources outside the WebSphere
version 6 server JNDI, configure the JMS connection factory to point to the
WebSphere version 6 node.
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.
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.