Technical data

Configuring JMS
Administration Guide 17-11
Configuring JMS Templates
A JMS template provides an efficient means of defining multiple destinations with
similar attribute settings. JMS templates offer the following benefits:
n You do not need to re-enter every attribute setting each time you define a new
destination; you can use the JMS template and override any setting to which you
want to assign a new value.
n You can modify shared attribute settings dynamically simply by modifying the
template.
To define the JMS template configuration attributes for destinations, use the Templates
node in the Administration Console. The configurable attributes for a JMS template are
the same as those configured for a destination. These configuration attributes are
inherited by the destinations that use them, with the following exceptions:
n If the destination that is using a JMS template specifies an override value for an
attribute, the override value is used.
n If the destination that is using a JMS template specifies a message redelivery
value for an attribute, that redelivery value is used.
n The Name attribute is not inherited by the destination. This name is valid for the
JMS template only. You must explicitly define a unique name for all
destinations.
Note: JMS templates have unique naming restrictions within a domain. For more
information, see “JMS Configuration Naming Rules” on page 17-3.
n The JNDI Name, Enable Store, and Template attributes are not defined for JMS
templates.
n The Multicast attributes are not defined for JMS templates because they apply
only to topics.
Any attributes that are not explicitly defined for a destination are assigned default
values. If no default value exists, be sure to specify a value within the JMS template or
as a destination attribute override. If you do not do so, the configuration information
remains incomplete, the WebLogic JMS configuration fails, and the WebLogic JMS
does not boot.