Use this task to create a link that enables a messaging engine
to handle message requests from Version 5 JMS applications.
Why and when to perform this task
The WebSphere MQ client link enables WebSphere Application Server
Version 5 J2EE applications to use messaging resources of the WebSphere Application
Server Version 6 default messaging provider that are backed by destinations
on the service integration bus.
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.
If you migrate a Version 5 node to Version 6, a default WebSphere
MQ link, with the name Default.MQClientLink, is created for the application
servers on that node. You only need to create another WebSphere MQ client
link if you want some Version 5 JMS applications to use a different channel
to connect to the messaging engine, or want to present a messaging engine
as a non-default queue manager name.
If you create a WebSphere MQ client
link, you only need to manually specify values for a subset of the available
properties. You can choose to specify values for other optional properties
in this task, or if wanted at a later time by changing the configuration of
the client link.
To create
a WebSphere MQ client link, use the administrative console to complete the
following steps.
Steps for this task
- List the WebSphere MQ client links for the messaging engine that
the Version 5 JMS applications are to connect to. Click bus_name . This displays any existing WebSphere MQ client links
in the content pane.
- Click New in the content pane.
- Specify the following required properties for the WebSphere MQ
client link:
- 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 Application Server 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 Application
Server 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.
On
a managed node in a network deployment cell, an application server with the
name jmsserver is used for interoperation with WebSphere Application Server
Version 5 applications, to represent the JMS server that was used in WebSphere
Application Server Version 5. For this server, the WebSphere MQ client link
has the queue manager name WAS_nodeName_jmsserver.
You should not use this queue manager name on any other WebSphere MQ link
that is assigned to a messaging engine on the same node.
- 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 Application Server 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.
- Optional: If you want to specify other optional properties,
see the property descriptions in WebSphere MQ client link settings.
- Click OK.
- Save your changes to the master configuration.
To enable WebSphere Application Server Version 5 applications to
use messaging resources of the WebSphere Application Server Version 6, ensure
you complete all the steps in the task
Managing WebSphere Application Server Version 5 JMS use of WebSphere Application Server Version 6 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.