| |
Foreign Connection Factories
Column Display Related Tasks Related Topics
A foreign connection factory represents a connection factory that resides on another server, and which 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.
This page summarizes the foreign connection factories that have been created for this domain.
Column Display
You can show fewer or additional data points on this page by expanding Customize this table and modifying the Column Display list. Each data point displays in its own table column.
The following table lists all of the data points that you can display in columns on this page.
Name Description Name The name of this entity, represented in XML as an attribute.
Many of the elements within the JMS module are named entities. All of the named entities encased by a type in the XML file must be unique. This is the identifier used to delineate a particular entity within the JMS module.
This attribute cannot be modified externally from the module (for example, with a deployment plan) because it may be used inside the module referentially.
MBean Attribute (Does not apply to application modules) :
ForeignConnectionFactoryBean.NameChanges 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) :
ForeignConnectionFactoryBean.LocalJNDINameChanges 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) :
ForeignConnectionFactoryBean.RemoteJNDINameChanges take effect after you redeploy the module or restart the server.
|