Skip navigation.

Administration Console Online Help

PreviousNextvertical dots separating previous/next from contents/index/pdfContents

Foreign Servers: Configuration: General

Configuration Options     Related Tasks     Related Topics

A foreign server represents a JNDI provider that resides outside a WebLogic Server. It contains information that allows WebLogic Server to reach the remote JNDI provider. This way, a number of connection factory and destination objects (queues or topics) can be defined on one JNDI directory. Use this page to configure a foreign server.

Configuration Options

Name Description

The name of this foreign server.

JNDI Initial Context Factory

The name of the class that must be instantiated to access the JNDI provider. This class name depends on the JNDI provider and the vendor that are being used.

This value corresponds to the standard JNDI property, java.naming.factory.initial.

Note: This value defaults to weblogic.jndi.WLInitialContextFactory, which is the correct value for WebLogic Server.

MBean Attribute (Does not apply to application modules):

JNDI Connection URL

The URL that WebLogic Server will use to contact the JNDI provider. The syntax of this URL depends on which JNDI provider is being used. For WebLogic JMS, leave this field blank if you are referencing WebLogic JMS objects within the same cluster.

This value corresponds to the standard JNDI property, java.naming.provider.url.

Note: If this value is not specified, look-ups will be performed on the JNDI server within the WebLogic Server instance where this connection factory is deployed.

MBean Attribute (Does not apply to application modules):

JNDI Properties

Any additional properties that must be set for the JNDI provider. These properties will be passed directly to the constructor for the JNDI provider's InitialContext class.

Some foreign providers require other properties to be set while obtaining an initial naming context. These properties can be set with a property bean

MBean Attribute (Does not apply to application modules):

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

Related Tasks

Related Topics


Skip navigation bar   Back to Top