Manage V5 JMS servers in a dmgr cell

Use this task to manage JMS servers on WAS V5 nodes in a dmgr cell.

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

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

Use the WebSphere admin console to display a list of all V5 JMS servers, to show and control their runtime status. We 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.

In general, the default values of properties for the V5 default messaging provider are adequate for JMS servers. However, if we are running high messaging loads, we might have to change some WebSphere MQ properties; for example, WebSphere MQ properties for log file locations, file pages, and buffer pages.

See 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 admin console to complete the following steps:

 

1. In the navigation pane, select Servers > Server Types > V5 JMS servers .

   This displays a table of the JMS servers, showing their runtime status.

2. To change the runtime status of a JMS server...

   1. In the table of JMS servers, select the JMS servers 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 we have acted on is updated to show the result of the actions.

3. To change the properties of a JMS server...

   1. Click the name of the server

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

      Initial state

      If we want the JMS server to be started automatically when the appserver 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. If we 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. To stop the JMS server hosting a JMS queue, remove the queue name from the Queue Names field.

6. Click OK.

7. Save the changes to the master configuration.

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

Version 5 JMS server settings

 

Related tasks

Maintain (deprecated) V5 default messaging resources