Instead of creating name space bindings from a program, you can
configure name space bindings using the administrative console. Name servers
add these configured bindings to the name space view by reading the configuration
data for the bindings. Configured bindings are created each time a server
starts, even when the binding is created in a transient partition of the name
space. One major use of configured bindings is to provide fixed qualified
names for server application objects.
Before you begin
Assemble and deploy your application onto an application server. If
the application is a client to an application running in another server process,
specify qualified jndiName values for the other application's server objects
during assembly or
deployment.
For more information on qualified names, refer to
Lookup names support in deployment descriptors and thin clients.
About this task
A deployed application requires qualified fixed names if the application
is accessed by thin client applications or by J2EE client applications or
server applications running in another server process.
When you configure
a name space binding, you create a qualified fixed name for a server object.
A fixed name does not change if the object is moved to another server. A qualified
fixed name with a cell scope has the form:
cell/persistent/fixedName
where fixedName is
an arbitrary fixed name.
You can configure name space bindings, and
thus qualified fixed names, for 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 name
space that is accessible using a JNDI indirect lookup
To view or configure a name space binding for an object of a deployed
application, complete the following:
Procedure
- Go to the Name Space Bindings
page.
In the administrative console, click Environment
> Naming > Name Space Bindings.
- Select the desired scope.
The scope determines where
in the name space the name space binding is created. It also affects which
name servers contain the binding in the name space that they manage. Regardless
of the scope, a name space binding is accessible from all name servers in
the cell. However, the scope can affect whether the lookup can be resolved
locally by a name server or whether the name server must make a remote call
to another name server to resolve the binding.
Only name space bindings
created with the selected scope are visible in the collection table on the
page. By changing the scope, you can see and create bindings in other scopes.
- Select a scope.
If you are creating a new name
space binding, refer to the table below as a guide in selecting a scope:
Scope |
Description |
Cell |
Cell-scoped bindings are created under the cell persistent
root context. Select Cell if the name space binding is not specific
to any particular node or server, or if you do not want the binding to be
associated with any specific node or server. For example, you can use cell-scoped bindings to create
fixed qualified names for enterprise beans. Fixed qualified names do not have
any node or server
names embedded within them. |
Node |
Node-scoped bindings are created under the node persistent
root context for the selected node. Select Node if the name space binding
is specific to a particular node, or if you want the binding to be associated
with a specific node. |
Server |
Server-scoped bindings are created under the server
root context for the selected server. Select Server if a binding is
to be used only by clients of an application running on a particular server,
or if you want to configure a binding with the same name on different servers
which resolve to different objects. Note that two servers can have configured
bindings with the same name but resolve to different objects. Server-scoped
bindings are created in the process of the selected application server. Therefore,
the name server running in the selected application server can resolve those
bindings locally. No remote invocations to other name servers are necessary
to resolve the bindings. However, all other name servers in the cell must
make remote calls to the selected server in order to resolve the bindings.
For example, in order for the name server running in server1 in node node1 to
resolve the name cell/nodes/node1/servers/server2/serverScopedConfiguredBinding,
it must make a remote call to server2 in node1. Only the name
server in server2 in node1 can resolve that name without invoking
any other name servers.
|
- Click Apply.
- Create a new name space binding.
- Open the New Name Space Binding wizard.
On the Name Space Bindings page, click New.
- On the Specify binding
type panel, select the binding type.
The name space
binding can be for a constant string value, an EJB home, a CORBA CosNaming
NamingContext or CORBA leaf node object, or an object that you can look up
indirectly using JNDI.
- On the Specify basic properties panel, specify the binding
identifier and other properties for the binding.
For
property descriptions, refer to the following:
- On the Summary panel, verify the settings and click Finish.
The name of the new binding is displayed in the collection table
on the Name Space Bindings page.
- Optional: Edit a previously created binding.
- From the collection table on the Name
Space Bindings page, click the name of the binding that you want to
edit.
- Edit the binding properties as desired. Step 3(c) provides links to property descriptions.
- Click OK.
Results
Cell-scoped bindings are created under the cell persistent root context.
Node-scoped bindings are created under the node persistent root context for
the specified node. Server-scoped bindings are created under the server root
context for the selected server.