Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with a third-party or (deprecated) V5 default messaging provider > Maintain (deprecated) v5 default messaging resources

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 dmgr 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 WAS v6 can also use JMS resources served by any of those JMS servers.

We can 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 you are running high messaging loads, you might have 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 System administration section of the WebSphere MQ information center.

To manage a v5 JMS server, use the admin console...

Procedure

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. Optional: 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 your actions.

3. Optional: 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 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.
   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.

4. Optional: To stop the JMS server hosting a JMS queue, remove the queue name from the Queue Names field.

5. Click OK.

6. Save your changes to the master configuration.

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

Related

Version 5 JMS server settings
Maintain (deprecated) v5 default messaging resources

Related

WebSphere MQ library

+

Search Tips   |   Advanced Search