11.1 Naming Features
The following are features of a WAS V6 name space that remain unchanged from WAS V5:
- Distributed name space
For additional scalability, the name space for a cell is distributed among the various servers. The deployment manager, node agent, and appserver processes all host a name server.
The default initial context for a server is its server root. System artifacts, such as EJB homes and resources, are bound to the server root of the server with which they are associated.
- Transient and persistent partitions
Server roots are transient. Cell and node roots are persistent.
- Federated name space structure
A name space is a collection of all names bound to a particular name server. A name space can contain naming context bindings to contexts located in other servers, which case the name space is said to be a federated name space.
The name space for the WAS V6 cell is federated among the deployment manager, node agents, and appservers of the cell. Every server process hosts a name server. All name servers provide the same logical view of the cell name space, with the various server roots and persistent partitions of the name space being interconnected by means of the single logical name space.
- Configured bindings
Administrators can configure bindings into the name space. A configured binding is different from a programmatic binding in that the system creates the binding every time a server is started, even if the target context is in a transient partition.
- Interoperable Naming Service (INS) object URLs
WAS supports CORBA object URLs...
...as JNDI provider URLs and lookup names.