Technical data

17 Managing JMS
17-10 Administration Guide
Configuring Destinations
A destination identifies a queue (Point-To-Point) or a topic (Pub/Sub) for a JMS server.
After defining a JMS server, configure one or more destination for each JMS server.
You configure destinations explicitly or by configuring a destination template that can
be used to define multiple destinations with similar attribute settings, as described in
“Configuring JMS Templates” on page 17-11.
To configure destinations explicitly, use the Destinations node in the Administration
Console, and define the following configuration attributes:
n General configuration attributes, including:
l Name and type (queue or topic) of the destination.
l Name for accessing the destination within the JNDI namespace.
l Whether or not a store is enabled for storing persistent messages.
l The JMS template used for creating destinations.
l Keys used to define the sort order for a specific destination.
Note: JMS destinations have unique naming restrictions 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 on the destination.
n Message attributes that can be overridden (such as priority, time-to-live,
time-to-deliver, and delivery mode).
n Message redelivery attributes, including redelivery delay override, redelivery
limit, and error destination.
n Multicasting attributes, including multicast address, time-to-live (TTL), and port
(for topics only).
For instructions on creating and configuring a destination, see “JMS Destinations” in
the Administration Console Online Help.
Some destination attributes are dynamically configurable. When attributes are
modified at run time, only incoming messages are affected; stored messages are not
affected.