Use this task to manage JMS servers on an Application Server node that is not part of a deployment manager cell.
Why and when to perform this task
On an Application Server node that is not part of a deployment manager cell, each application server has an internal JMS server that runs as part of the application server process and is administered as additional properties of the application server. A JMS server enables the application server to access JMS resources.
If you want to start a JMS server that is not part of a deployment manager cell, you start the associated application server.
A JMS server makes use of separate WebSphere MQ processes. If a WebSphere MQ process fails and restarts while the JMS server is running, you must restart the application server. This shutdown also can affect other installed applications.
Before starting the application server, ensure that the required WebSphere MQ messages are not being suppressed by the message processing facility (MPF). For more information about starting application servers, see Starting servers.
You can use the WebSphere administrative console to configure a general set of JMS server properties, which add to the default values of properties configured automatically for the embedded WebSphere JMS provider.
To configure JMS server properties, use the administrative console to complete the following steps:
Steps for this task
If you want the JMS server to be started automatically when the application server is next started, set the Initial state property to started.
If you want to add a new queue to be hosted by the JMS server, add the administrative name of the queue to the Queue Names field. (The name must match the name of a WebSphere Queue administrative object, including the use of upper- and lowercase.) Similarly, if you want to remove a queue from the JMS server, remove its name from that field.