JMS server settings: WAS ND

JMS server settings

The JMS functions on a node within the WebSphere Application Server administration domain are served by the JMS server on that node. Use this panel to view or change the configuration properties of the selected JMS server.

You can use this panel 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.

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, 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.

Name

The name by which the JMS server is known for administrative purposes within IBM WebSphere Application Server.
This name should not be changed.

Data type String
Units Not applicable
Default WebSphere Internal JMS Server
Range Not applicable

Description

A description of the JMS server, for administrative purposes within IBM WebSphere Application Server.
This string should not be changed.

Data type String
Default WebSphere Internal JMS Server

Number of threads

The number of concurrent threads used to match publications to subscribers.
The number of concurrent threads should only be set to a small number. (Set this value a little higher than the number of concurrent message publishers.)

Data type Integer
Units Threads
Default 1
Range Greater than or equal to 1.

Queue Names

The names of the queues hosted by this JMS server. Each queue name must be added on a separate line.
Each queue listed in this field must have a separate queue administrative object with the same administrative name. To make a queue available to applications, define a WebSphere queue and add its name to this field on the JMS Server panel for the host on which you want the queue to be hosted.

Data type ASCII
Units Queue name
Default Not applicable
Range Each entry in this field is a queue name of up to 45 characters, which must match exactly (including use of upper- and lowercase characters) the WebSphere queue administrative object defined for the queue.

Initial state

The state that you want the JMS server to have when it is next restarted on Application Server.
After setting this property to STARTED, you can restart the JMS server for an appserver by stopping and restarting that application server. (On Application Server, the JMS server is a component of an appserver.)

To start the JMS server for a node in a deployment manager cell, stop then restart that JMS server.

Data type Enum
Units Not applicable
Default STARTED
Range

SARTED

The JMS server is started automatically when the appserver starts.

STOPPED

The JMS server is not started automatically when the appserver starts. If any deployed enterprise applications are to use functions provided by the JMS server, the system administrator must start the appserver manually or select the Started value of this property then restart the application server.

Managing JMS servers on an Application Server node
Managing JMS servers in a deployment manager cell

Data type	String
Units	Not applicable
Default	WebSphere Internal JMS Server
Range	Not applicable

Data type	Integer
Units	Threads
Default	1
Range	Greater than or equal to 1.

Data type	ASCII
Units	Queue name
Default	Not applicable
Range	Each entry in this field is a queue name of up to 45 characters, which must match exactly (including use of upper- and lowercase characters) the WebSphere queue administrative object defined for the queue.

Data type	Enum
Units	Not applicable
Default	STARTED
Range	SARTED The JMS server is started automatically when the appserver starts. STOPPED The JMS server is not started automatically when the appserver starts. If any deployed enterprise applications are to use functions provided by the JMS server, the system administrator must start the appserver manually or select the Started value of this property then restart the application server.