Specify binding type settings

Specify binding type settings

Use this panel to select the type of name space binding that you want.
To view this console panel, click Environment > Naming > Name Space Bindings > New.
You can configure a name space binding for any of the following objects:

A string constant value

An enterprise bean (EJB) home installed on a server in the cell

A CORBA object available from a CosNaming name server

An object bound in a WAS name space that is accessible using a JNDI indirect lookup

On this panel, select a binding type and then click Next.

Binding type

Timeype of binding configured.

String Select String to configure a name space binding for a string constant value.
To configure a String binding, we need the following information:

The string constant value

The target root context for the configured binding (scope)

The name of the configured binding, relative to the target root context

EJB Select EJB to configure a name space binding for an EJB home installed on a server in the cell. Use a cell-scoped EJB binding to create a fixed qualified lookup name for an enterprise bean. A fixed qualified lookup name is not dependent on the cell topology.
To configure an EJB home binding, we need the following information:

The JNDI name of the EJB server or server cluster where the enterprise bean is deployed

The target root context for the configured binding (scope)

The name of the configured binding, relative to the target root context

On standalone servers, do not configure an EJB binding that resolves to another server. The name server cannot read configuration data for other servers. That data is required to construct the binding.
CORBA Select CORBA to configure a name space binding for a Common Object Request Broker: Architecture and Specification (CORBA) object available from a Object Management Group (OMG) Interoperable Naming (CosNaming) name server. Identify a CORBA object bound into an INS compliant CosNaming server with a corbaname URL. The referenced object does not have to be available until the binding is actually referenced by an application.
To configure a CORBA binding, we need the following information:

The corbaname URL of the CORBA object

An indicator if the bound object is a context or leaf node object (to set the correct CORBA binding type of context or object)

The target root context for the configured binding

The name of the configured binding, relative to the target root context

Indirect Select Indirect to configure a name space binding for an object bound in a WAS name space that is accessible using a Java Naming and Directory Interface (JNDI) indirect lookup. You can select Indirect for CORBA objects as well as for javax.naming.Referenceable, javax.naming.Reference, and java.io.Serializable objects.
The target object itself is not bound to the name space. Only the information required to look up the object is bound. Therefore, the referenced name server does not have to be running until the binding is actually referenced by some application.
To configure an indirect JNDI lookup binding, we need the following information:

The JNDI provider URL of the name server where the object resides

The JNDI lookup name of the object

The target root context for the configured binding (scope)

The name of the configured binding, relative to the target root context

The following information is optional:

The JNDI initial context factory class name. The default is the WebSphere Application Server initial context factory, com.ibm.websphere.naming.WsnInitialContextFactory.

Additional properties to pass to the javax.naming.InitialContext constructor.

A cell-scoped indirect binding is useful when creating a fixed qualified lookup name for a bound object so that the qualified lookup name is not dependent on the cell topology.

Related tasks

Configure name space bindings

Related Reference
Name space binding collection

Reference topic

String	Select String to configure a name space binding for a string constant value. To configure a String binding, we need the following information: The string constant value The target root context for the configured binding (scope) The name of the configured binding, relative to the target root context
EJB	Select EJB to configure a name space binding for an EJB home installed on a server in the cell. Use a cell-scoped EJB binding to create a fixed qualified lookup name for an enterprise bean. A fixed qualified lookup name is not dependent on the cell topology. To configure an EJB home binding, we need the following information: The JNDI name of the EJB server or server cluster where the enterprise bean is deployed The target root context for the configured binding (scope) The name of the configured binding, relative to the target root context On standalone servers, do not configure an EJB binding that resolves to another server. The name server cannot read configuration data for other servers. That data is required to construct the binding.
CORBA	Select CORBA to configure a name space binding for a Common Object Request Broker: Architecture and Specification (CORBA) object available from a Object Management Group (OMG) Interoperable Naming (CosNaming) name server. Identify a CORBA object bound into an INS compliant CosNaming server with a corbaname URL. The referenced object does not have to be available until the binding is actually referenced by an application. To configure a CORBA binding, we need the following information: The corbaname URL of the CORBA object An indicator if the bound object is a context or leaf node object (to set the correct CORBA binding type of context or object) The target root context for the configured binding The name of the configured binding, relative to the target root context
Indirect	Select Indirect to configure a name space binding for an object bound in a WAS name space that is accessible using a Java Naming and Directory Interface (JNDI) indirect lookup. You can select Indirect for CORBA objects as well as for javax.naming.Referenceable, javax.naming.Reference, and java.io.Serializable objects. The target object itself is not bound to the name space. Only the information required to look up the object is bound. Therefore, the referenced name server does not have to be running until the binding is actually referenced by some application. To configure an indirect JNDI lookup binding, we need the following information: The JNDI provider URL of the name server where the object resides The JNDI lookup name of the object The target root context for the configured binding (scope) The name of the configured binding, relative to the target root context The following information is optional: The JNDI initial context factory class name. The default is the WebSphere Application Server initial context factory, com.ibm.websphere.naming.WsnInitialContextFactory. Additional properties to pass to the javax.naming.InitialContext constructor. A cell-scoped indirect binding is useful when creating a fixed qualified lookup name for a bound object so that the qualified lookup name is not dependent on the cell topology.