Foreign JMS Server --> Configuration --> General

Foreign JMS Server --> Configuration --> General

Tasks Related Topics Attributes

Overview

This tab defines general configuration attributes for an instance of a foreign JMS server. A foreign JMS server represents a JNDI provider that is outside the WebLogic JMS server. It contains information that allows a local WebLogic Server to reach a remote JNDI provider, thereby allowing for a number of foreign JMS connection factory and destination objects to be defined on one JNDI directory.

Tasks

Creating a Foreign JMS Server

Related Topics

Using Foreign JMS Providers with WebLogic Server white paper on dev2dev.bea.com

Attributes

Attribute Label

Description

Value Constraints
Name The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management.
configuration.
ForeignJMSServerMBeanAttribute: Name

JNDI Initial Context Factory The name of the class that must be instantiated to access the JNDI provider. This class name depends on the provider and vendor that are being used. It defaults to weblogic.jndi.WLInitialContextFactory, which is the correct value for WebLogic Server. This value corresponds to the standard JNDI property, java.naming.factory.initial.MBean: weblogic.management.
configuration.
ForeignJMSServerMBeanAttribute: InitialContextFactory Default: weblogic.jndi.WLInitialContextFactoryDynamic: yes
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. This value corresponds to the standard JNDI property, java.naming.provider.url. For WebLogic JMS, leave this field blank if you are referencing WebLogic JMS objects within the same cluster. When no URL is specified, look-ups will be performed on the JNDI server within the WebLogic Server instance where this connection factory is deployed.MBean: weblogic.management.
configuration.
ForeignJMSServerMBeanAttribute: ConnectionURL Dynamic: yes
JNDI Properties Additional properties that must be set for the particular JNDI provider. These properties will be passed directly to the constructor for the JNDI provider's InitialContext class.This field must be filled in using a name=value<return>name=value format.MBean: weblogic.management.
configuration.
ForeignJMSServerMBeanAttribute: JNDIProperties Dynamic: yes

Attribute Label	Description	Value Constraints
Name	The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.MBean: weblogic.management. configuration. ForeignJMSServerMBeanAttribute: Name
JNDI Initial Context Factory	The name of the class that must be instantiated to access the JNDI provider. This class name depends on the provider and vendor that are being used. It defaults to weblogic.jndi.WLInitialContextFactory, which is the correct value for WebLogic Server. This value corresponds to the standard JNDI property, java.naming.factory.initial.MBean: weblogic.management. configuration. ForeignJMSServerMBeanAttribute: InitialContextFactory	Default: weblogic.jndi.WLInitialContextFactoryDynamic: yes
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. This value corresponds to the standard JNDI property, java.naming.provider.url. For WebLogic JMS, leave this field blank if you are referencing WebLogic JMS objects within the same cluster. When no URL is specified, look-ups will be performed on the JNDI server within the WebLogic Server instance where this connection factory is deployed.MBean: weblogic.management. configuration. ForeignJMSServerMBeanAttribute: ConnectionURL	Dynamic: yes
JNDI Properties	Additional properties that must be set for the particular JNDI provider. These properties will be passed directly to the constructor for the JNDI provider's InitialContext class.This field must be filled in using a name=value<return>name=value format.MBean: weblogic.management. configuration. ForeignJMSServerMBeanAttribute: JNDIProperties	Dynamic: yes