Version 5 JMS server settings
The JMS functions on a V5 node in a dmgr cell are served by a JMS server. To set the configuration properties of the selected JMS server.
JMS servers are supported only to aid migration of WAS V5 nodes to WAS Version 6.
To configure a general set of JMS server properties, which add to the default values of properties configured automatically for the V5 default messaging provider.
JMS servers make use of WebSphere MQ properties and, in general, the default values of those properties are adequate. However, if we are running high messaging loads, we might have to change some WebSphere MQ properties; for example, properties for log file locations, file pages, and buffer pages.
See 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 WAS.
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 admin purposes within IBM WAS.
This string should not be changed.
Data type String Default WebSphere Internal JMS Server
- Number of threads
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.
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 admin 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 String Units Queue name 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 admin object defined for the queue.
- Initial State
The state that you want the JMS server to have when it is next restarted.
Data type Enum Default Started Range
- Started
- The JMS server is started automatically.
- Stopped
- The JMS server is not started automatically. If any deployed enterprise applications are to use JMS server functions provided by the JMS server, the system administrator must start the JMS server manually or select the Started value of this property then restart the JMS server.
To restart a JMS server on a V5 node, stop then restart that JMS server.
Related tasks
Manage V5 JMS servers in a dmgr cell
Related
Mapping of admin console panel names to command names and WebSphere MQ names
Related information
JMS interfaces - explicit polling for messages