Configuring Basic JMS System Resources 3-9
namejmsserver1groupname targetjmsserver1target
sub-deployment descriptor-file-namejmsjmssysmod-jms.xmldescriptor-file-name
jms-system-resource
To help manage your subdeployments for a JMS system module, the Administration Console provides subdeployment management pages. For more information, see
Configure subdeployments in JMS system modules in the Oracle WebLogic Server Administration Console Help.
For information about deploying stand-alone JMS modules, see Deploying JDBC, JMS, and WLDF Application Modules in Deploying Applications to Oracle WebLogic
Server.
3.6 Connection Factory Configuration
Connection factories are resources that enable JMS clients to create JMS connections. A connection factory supports concurrent use, enabling multiple threads to access the
object simultaneously. WebLogic JMS provides pre-configured default connection factories that can be enabled or disabled on a per-server basis, as described in
Section 3.6.1, Using a Default Connection Factory. Otherwise, you can configure one or more connection factories to create connections
with predefined options that better suit your application. Within each JMS module, connection factory resource names must be unique. And, all connection factory JNDI
names in any JMS module must be unique across an entire WebLogic domain, as defined in
Section 3.3, JMS Configuration Naming Requirements. WebLogic Server
adds them to the JNDI space during startup, and the application then retrieves a connection factory using the WebLogic JNDI APIs.
You can establish cluster-wide, transparent access to JMS destinations from any server in the cluster, either by using the default connection factories for each server instance,
or by configuring one or more connection factories and targeting them to one or more server instances in the cluster. This way, each connection factory can be deployed on
multiple WebLogic Server instances. For more information on configuring JMS clustering, see
Section 4.1, Configuring WebLogic JMS Clustering.
3.6.1 Using a Default Connection Factory
WebLogic Server defines two default connection factories, which can be looked up using the following JNDI names:
■
weblogic.jms.ConnectionFactory
■
weblogic.jms.XAConnectionFactory You only need to configure a new connection factory if the pre-configured settings of
the default factories are not suitable for your application. For more information on using the default connection factories, see Understanding WebLogic JMS in
Programming JMS for Oracle WebLogic Server.
The main difference between the pre-configured settings for the default connection factories and a user-defined connection factory is the default value for the XA
Connection Factory Enabled option to enable JTA transactions. For more information about the XA Connection Factory Enabled option, and to see the default values for the
other connection factory options, see JMSConnectionFactoryBean in the Oracle WebLogic Server MBean Reference.
3-10 Configuring and Managing JMS for Oracle WebLogic Server
Also, using default connection factories means that you have no control over targeting the WebLogic Server instances where the connection factory may be deployed.
However, you can enable and or disable the default connection factories on a per-WebLogic Server basis, as defined in Server: Configuration: Services in the Oracle
WebLogic Server Administration Console Help.
3.6.2 Connection Factory Configuration Parameters
