Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

JMS Connection Factory: Configuration: General

Configuration Options     Related Tasks     Related Topics

Use this page to define the general configuration parameters for this JMS connection factory, which includes various client connection, default delivery, load balancing, and security parameters.

Configuration Options

Name Description
Name

The name of this JMS connection factory.

MBean Attribute:
WebLogicMBean.Name

Changes take effect after you redeploy the module or restart the server.

JNDI Name

The global JNDI name used to look up a connection factory within a clustered JNDI namespace.

In a clustered environment, this name is propagated to the entire cluster. If you want the JNDI name to be bound only on the local server, and not propagated to the rest of the cluster, then use the Local JNDI Name setting.

If not specified, then the connection factory is not bound into a clustered JNDI namespace.

MBean Attribute (Does not apply to application modules) :
JMSConnectionFactoryBean.JNDIName

Local JNDI Name

The local JNDI name used to look up the connection factory within the JNDI namespace of the server where the connection factory is targeted. In a clustered environment, this name is bound only on the local server instance and is not propagated to the rest of the cluster.

If not specified, then the connection factory is not bound into the local JNDI namespace.

MBean Attribute (Does not apply to application modules) :
JMSConnectionFactoryBean.LocalJNDIName

Default Targeting Enabled

Specifies whether this JMS resource defaults to the parent module's targeting or uses the subdeployment targeting mechanism.

When set to true, this resource implicitly inherits the targeting of its parent module. When set to false, this resource gets targeted based its subdeployment's targets, if one is specified.

MBean Attribute (Does not apply to application modules) :
JMSConnectionFactoryBean.DefaultTargetingEnabled

Changes take effect after you redeploy the module or restart the server.

Related Tasks

Related Topics


Back to Top