WAS v8.5 > Administer applications and their environmentAdminister naming and directory
This page provides a starting point for finding information about naming support. Naming includes both server-side and client-side components. The server-side component is a Common Object Request Broker Architecture (CORBA) naming service (CosNaming). The client-side component is a JNDI service provider. JNDI is a core component in the Java EE programming model.
WAS v8.5 JNDI service provider can be used to interoperate with any CosNaming name server implementation. Yet product name servers implement an extension to CosNaming, and the JNDI service provider uses those WebSphere extensions to provide greater capability than CosNaming alone. Some added capabilities are binding and looking up of non-CORBA objects.
Java EE applications use the JNDI service provider supported by WAS to obtain references to objects related to server applications, such as EJB homes, which have been bound into a CosNaming name space.
Subtopics
- Configure namespace bindings
Instead of creating namespace bindings from a program, we can configure namespace bindings using the dmgr console. Name servers add these configured bindings to the namespace 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 namespace. One major use of configured bindings is to provide fixed qualified names for server application objects.- Configure name servers
Name servers add configured name space bindings to the name space view by reading the configuration data for the bindings. If we use configured bindings, we do not need to create name space bindings from a program.
Related information:
End-to-end paths for Naming and directory
Migrating Naming and directory
Naming and directory
Scripting for naming and directory
Develop Naming and directory
Troubleshooting Naming and directory