Manage V5 JMS servers in a deployment manager cell

Use this task to manage JMS servers on WebSphere Application Server V5 nodes in a deployment manager cell.

Overview

The use of JMS servers is only intended to support migration from WebSphere Application Server V5 nodes to WebSphere Application Server V6.

In a WebSphere Application Server deployment manager cell, each V5 node can have at most one JMS server, and any V5 application server within the cell can use JMS resources served by any of those JMS servers. Applications on WebSphere Application Server V6 can also use JMS resources served by any of those JMS servers.

You can use the WebSphere administrative console to display a list of all V5 JMS servers, to show and control their runtime status. You can also configure a general set of JMS server properties, which add to the default values of properties configured automatically for the V5 default messaging provider.

Note: In general, the default values of properties for the V5 default messaging provider are adequate for JMS servers. However, if you are running high messaging loads, you may need to change some WebSphere MQ properties; for example, WebSphere MQ properties for log file locations, file pages, and buffer pages. For more information about configuring WebSphere MQ properties, see the WebSphere MQ System Administration book, SC33-1873, which is available from the IBM Publications Center or from the WebSphere MQ collection kit, SK2T-0730.

To manage a V5 JMS server, use the administrative console to complete the following steps:

Procedure

1. In the navigation pane, select Servers > JMS Servers This displays a table of the JMS servers, showing their runtime status.

2. Optional: If you want to change the runtime status of a JMS server, complete the following steps:

   1. In the table of JMS servers, select the JMS servers that you want to act on.

      • To act on one or more specific JMS servers, select the check box next to the JMS server name.

      • To act on all JMS servers, select the check box next to the JMS servers title of the table.

   2. Click one of the actions displayed to change the status of the JMS servers; for example, click Stop to stop a JMS server.

   The status of the JMS servers that you have acted on is updated to show the result of your actions.

3. Optional: If you want to change the properties of a JMS server, complete the following steps:

   1. Click the name of the server

   2. Set one or more of the following configuration properties:

      Initial state

      If you want the JMS server to be started automatically when the application server is next started, set this property to Started.

      Number of threads

      Set the number of concurrent threads to be used by the publish/subscribe matching engine. The number of concurrent threads should only be set to a small number.

4. Optional: If you want the JMS server to host a new JMS queue, add the queue name to the Queue Names field.

   The name must match the name of a JMS Queue administrative object, including the use of upper- and lowercase.

5. Optional: If you want to stop the JMS server hosting a JMS queue, remove the queue name from the Queue Names field.

6. Click OK.

7. Save your changes to the master configuration.

8. To have the changed configuration take effect, stop then restart the JMS server.