Fusion Middleware Control Help for WebLogic Server

Previous Next Open TOC in new window
Content starts here

Foreign Server Connection Factory: Configuration: General

Configuration Options     

A foreign connection factory is a connection factory that resides on another server instance and is accessible via JNDI. A remote connection factory can be used to refer to another instance of WebLogic Server running in a different cluster or server, or a foreign provider, as long as that provider supports JNDI.

Configuration Options

Name Description
Name

The name of this foreign connection factory.

MBean Attribute:
WebLogicMBean.Name

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

Local JNDI Name

The name that the remote object will be bound to in the local server's JNDI tree. This is the name that should be used to look up the object on the local server.

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

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

Remote JNDI Name

The name of the remote object that will be looked up in the remote JNDI directory.

MBean Attribute (Does not apply to application modules) :
ForeignJNDIObjectBean.RemoteJNDIName

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

User Name

The user name that is passed when opening a connection to the remote server (represented by this foreign connection factory).

MBean Attribute (Does not apply to application modules) :
ForeignConnectionFactoryBean.Username

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

Connection Health Checking

Controls connection health checking for JMS resource reference pools that access this JMS foreign connection factory mapping. The default value is Enabled.

Oracle recommends selecting Disabled only when directed to do so by customer support.

MBean Attribute (Does not apply to application modules) :
ForeignConnectionFactoryBean.ConnectionHealthChecking

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


Back to Top