Use this task to manage JMS servers on nodes in a WebSphere Application Server deployment manager cell.
Before you begin
Before starting a JMS server, ensure that the following WebSphere MQ messages are not being suppressed by the message processing facility (MPF):
CSQV086E CSQY022I CSQY003I CSQX022I CSQM132I CSQ9022I CSQX017I CSQ3104I CSQ3106E
Why and when to perform this task
In a WebSphere Application Server deployment manager cell, each node can have at most one JMS server, and any application server within the cell can access JMS resources served by any of those JMS servers.
You can use the WebSphere administrative console to display a list of all 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 WebSphere MQ properties configured automatically for the embedded WebSphere JMS provider.
Note: In general, the default values of WebSphere
MQ properties are adequate for WebSphere internal 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 WebSphere internal JMS server, use the administrative console to complete the following steps:
Steps for this task
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.