Specify binding type settings
Use this page to select the type of namespace binding that you want.
To view this administrative console page, click
.You can configure a namespace 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 WebSphere® Application Server namespace that is accessible using a Java™ Naming and Directory Interface (JNDI) indirect lookup
On this page, select a binding type and then click Next.
Binding type
Specifies the type of binding configured.
String | Select String to configure
a namespace binding for a string constant value. To configure a String binding, you need the following information:
You can create a file that maps multiple variable names to values and specify the file name for the String value. By default, a name server performs variable substitution on the string value of a String namespace binding. Thus, by default, the com.ibm.websphere.naming.expandStringBindings property is set to true and a name server expands the value of String bindings. Tip: Variable substitution
can result in errors or unexpected changes to a string. For example,
with variable substitution, a $$ string is expanded
as $. You can disable variable substitution and cause
the name server to treat the String value as
a literal or constant. Create a custom property with Name set
to com.ibm.websphere.naming.expandStringBindings and Value set
to false. You can define a custom property at the
cell, node, server, or name server scope. Create the custom property
on a console page for the appropriate scope:
|
---|---|
EJB | Select EJB to configure
a namespace 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, you need the following information:
On stand-alone 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 namespace 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, you need the following information:
|
Indirect | Select Indirect to configure
a namespace binding for an object bound in a WebSphere Application Server namespace that
is accessible using a 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 namespace. 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, you need the following information:
The following information is optional:
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. |