Technical data

17 Managing JMS
17-8 Administration Guide
n Target a WebLogic Server instance that is associated with a JMS server. When
the target WebLogic Server boots, the JMS server boots as well. If no target
WebLogic Server is specified, the JMS server will not boot.
Note: The deployment of a JMS server differs from that of a connection factory or
template. A JMS server is deployed on a single server. A connection factory
or template can be instantiated on multiple servers simultaneously.
For instructions on creating and configuring a JMS server, see “JMS Servers” in the
Administration Console Online Help.
Configuring Connection Factories
Connection factories are objects that enable JMS clients to create JMS connections. A
connection factory supports concurrent use, enabling multiple threads to access the
object simultaneously. You define and configure one or more connection factories to
create connections with predefined attributes. WebLogic Server adds them to the JNDI
space during startup, and the application then retrieves a connection factory using
WebLogic JNDI.
You can establish cluster-wide, transparent access to destinations from any server in
the cluster by configuring multiple connection factories and using targets to assign
them to WebLogic Servers. Each connection factory can be deployed on multiple
WebLogic Servers. For more information on JMS clustering, refer to “WebLogic JMS
Fundamentals” in Programming WebLogic JMS.
To configure connection factories, use the Connection Factories node in the
Administration Console to define the following:
n General configuration attributes, including:
l Name of the connection factory.
l Name for accessing the connection factory within the JNDI namespace.
l Client identifier (client ID) that can be used for clients with durable
subscribers. (For more information about durable subscribers, see
Developing a WebLogic JMS Application” in Programming WebLogic
JMS.)
l Default message delivery attributes (that is, priority, time-to-live,
time-to-deliver, and mode).