Administer JMS servers in Network Deployment

 

Overview

If you are running WAS Network Deployment, you can manage JMS servers separately from the application servers. After you federate a JMS-enabled application server into a Network Deployment cell, the JMS server is displayed separately in the administrative console under Servers > JMS Servers

In the base WAS product, the embedded Java Message Service (JMS) server runs as part of each application server.

By default, when you create an instance in WAS, an embedded JMS server is created with the instance. To use the embedded JMS server with the applications, configure JMS resources such as queue connection factories, queues, topic connection factories, and topics.

In WAS Network Deployment, the JMS server does not start when you start the application server. You must start and stop JMS servers separately.

 

Modify JMS servers

To modify a JMS server, follow these steps:

  1. Start the administrative console.

  2. Expand...

    Servers | JMS Servers

  3. On the JMS Servers page, click the name of the JMS server that you want to modify.

  4. Make the changes.

  5. Click OK.

  6. Save the configuration.

 

Start JMS servers

To start a JMS server in WAS Network Deployment, follow these steps:

  1. Start the administrative console.

  2. Expand...

    Servers | JMS Servers

  3. On the JMS Servers page, select the checkbox for the JMS server that you want to start.

  4. Click Start.

 

Stop JMS servers

To stop a JMS server in WAS Network Deployment, follow these steps:

  1. Start the administrative console.

  2. Expand...

    Servers | JMS Servers

  3. On the JMS Servers page, select the checkbox for the JMS server that you want to stop.

  4. Click Stop.

 

See also