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

Create a WebSphere MQ client link

Use this task to create a link that enables a messaging engine to handle message requests from JMS applications developed for WAS v5.1. The WebSphere MQ client link is provided only for use with JMS applications developed for WAS v5.1.

The WebSphere MQ client link enables WAS v5.1 Java EE applications to use messaging resources of the default messaging provider of later versions 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 WAS v5.1 1 JMS applications.

If you migrate a v5.1 node to a later version, a default WebSphere MQ client link, with the name Default.MQClientLink, is created for the application servers on that node. You only have to create another WebSphere MQ client link if you want some v5.1 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 have to manually specify values for a subset of the available properties. We 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.

Tip: Creating a WebSphere MQ client link is only part of the task to enable WAS v5.1 applications to use messaging resources of the default messaging provider on a later version of the product. For more information about the overall task, see Enable WAS v5.1 JMS usage of messaging resources in later versions of the product.

To create a WebSphere MQ client link, use the administrative console to complete the following steps.

Procedure

1. List the WebSphere MQ client links for the messaging engine that the v5.1 JMS applications are to connect to. Click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional Properties] WebSphere MQ client links . This displays any existing WebSphere MQ client links in the content pane.

2. Click New in the content pane.
3. 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 JMS application developed for WAS v5.1 and the bus. This name must match the receiving channel name configured for WAS v5.1:

   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 WAS v5.1 applications. Type the queue manager name in the form:

   WAS_node_name_server_name
   
   

   Where:

   node_name
   is the name of the WAS node on the later version of the product.
   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 WAS Network Deployment cell, an application server with the name jmsserver is used for interoperation with WAS v5.1 applications, to represent the JMS server that was used in WAS v5.1. 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 client 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 JMS application developed for WAS v5.1 specifies that it is 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.

4. Optional: To specify other optional properties, see the property descriptions in WebSphere MQ client link [Settings].

5. Click OK.

6. Save your changes to the master configuration.

What to do next

To enable WAS v5.1 applications to use messaging resources of later versions, ensure you complete all the steps in the task Enable WAS v5.1 JMS usage of messaging resources in later versions of the product.
WebSphere MQ client links [Collection]
WebSphere MQ client link [Settings]
1 To make reading easier in this topic, the abbreviation " Version 5.1 " is sometimes used to refer to " WAS v5.1 ". For example, " Version 5.1 JMS resources" refers to JMS resources provided by

+

Search Tips   |   Advanced Search