Technical data

Configuring JMS
Administration Guide 17-7
Note: For more information on configuring a Connection Factory, see
“Configuring Connection Factories” on page 17-8.
8. Optionally, use the Destination Keys node to define the sort order for a specific
destination. For more information, see “Configuring Destination Keys” on page
17-12.
9. Optionally, create JMS Session Pools, which enable your applications to process
messages concurrently, and Connection Consumers (queues or topics) that
retrieve server sessions and process messages. For more information, see
“Configuring Session Pools” on page 17-16 and “Configuring Connection
Consumers” on page 17-16.
Configuring JMS Servers
A JMS server manages connections and message requests on behalf of clients.
To create a JMS server, use the Servers node in the Administration Console and define
the following:
n General configuration attributes, including:
l Name of the JMS server.
l Persistent store (file or JDBC database) required for persistent messaging. If
you do not assign a persistent store for a JMS server, persistent messaging is
not supported on that server.
l Paging store (file recommended) required for paging. If you do not assign a
paging store for a JMS server, paging is not support on that server.
l Temporary template that is used to create all temporary destinations,
including temporary queues and temporary topics.
Note: JMS servers must be uniquely named within a domain. For more
information, see “JMS Configuration Naming Rules” on page 17-3.
n Thresholds and quotas for messages and bytes (maximum number, and high and
low thresholds), and whether or not bytes paging and/or messages paging is
enabled.