WebSphere Application Server Network Deployment, Version 6.0.x     Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Configuring name space bindings

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 interoperability with Java Naming and Directory Interface (JNDI) clients running on previous versions of the WebSphere Application Server.

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.

Why and when to perform 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:

To view or configure a name space binding for an object of a deployed application, complete the following:

Steps for this task

  1. Go to the Name Space Bindings page.

    In the administrative console, click Environment > Naming > Name Space Bindings.

  2. Select the desired scope.

    The scope determines what name space bindings are visible in the collection table on the page. By changing the scope, you can see other variables that apply to a binding and change the contents of the collection table.

    1. Select a cell, node or server scope.

      The term server includes clusters in regard to name space bindings.

      If you are creating a new name space binding, select a scope that gives the binding the desired visibility:

      Scope Description
      Cell 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. Selecting Cell extends the visibility of the binding to all servers within the named cell. All of the users in the cell can look up and use the cell-scoped binding.

      A name space binding must be unique within a cell. Thus, you might use a cell-scoped binding to create fixed qualified names for enterprise beans.

      The cell scope is the most general scope and does not override any other scope. Cell-scoped bindings are overridden by any name space bindings that are defined within server or node scopes that are in the cell and have the same JNDI name.

      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. Selecting Node limits the visibility of the binding to all of the servers on the named node. All of the users of servers on the node can look up and use the node-scoped binding.

      The node scope has precedence over the cell scope. Node-scoped bindings override cell-scoped bindings. However, node-scoped bindings are overridden by any name space bindings that are defined within server scopes that are on the node and have the same JNDI name.

      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. Selecting Server limits the visibility to the named server.

      The server scope is the narrowest scope for name space bindings. The server scope has precedence over the cell and node scopes. Server-scoped bindings override any name space bindings that have the same JNDI name defined within the cell and node scopes.

    2. Click Apply.
  3. Create a new name space binding.
    1. Open the New Name Space Binding wizard.

      On the Name Space Bindings page, click New.

    2. 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.

    3. On the Specify basic properties panel, specify the binding identifier and other properties for the binding.

      For property descriptions, refer to the following:

    4. 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.
  4. Optional: Edit a previously created binding.
    1. From the collection table on the Name Space Bindings page, click the name of the binding that you want to edit.
    2. Edit the binding properties as desired. Step 3(c) provides links to property descriptions.
    3. Click OK.

Result

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. If the target server of a server-scoped binding is a cluster, the binding is created under the server root context of each cluster member.

What to do next




Sub-topics
Name space binding collection
Specify binding type settings
String binding settings
EJB binding settings
CORBA object binding settings
Indirect lookup binding settings

Related concepts
Naming
Name space bindings
Name space federation
Configured name bindings

Task topic    

Terms of Use | Feedback

Last updated: Dec 11, 2005 4:07:15 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/tnam_view_bindings.html

© Copyright IBM Corporation 2002, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)