11.2.1 Naming Components
WebSphere application clients use the naming service to obtain application object references, such as EJB homes, that are bound into the name space.
In a name space all non-leaf objects are called contexts. For example, the name...
myApp/myEJB
...consists of the non-leaf binding, myApp, which is a context and the leaf binding, myEJB.
The initial context is the starting point, the root, of a name space.
The object bound with the name myEJB in this example is an EJB home reference.
Naming clients typically use JNDI to perform naming operations.
Naming clients can also use the CosNaming interface.
Notice that all WAS processes host their own naming service and local name space. Also the name servers in the deployment manager and node agents are listening on their default ports of 9809 and 2809, respectively. The name servers within each appserver are listening from a starting default port of 9810.