The EJB Server naming service relies on an “initial” or default name context for each EJB Server. You set the initial context when you set up the EJB Server Naming Service properties.
The server name context syntax follows a specific organization or schema. You can use this schema to represent the hierarchy of objects in the namespace, for example by geographic region, organizational unit, and so on.
If you use an EJB Server as the name EJB Server server uses this format:
<Level 1>/<Level 2>/<Level 3>/...
The number of levels depends on the hierarchy you want to represent. For example:
US/sybase/finance US/sybase/marketing US/sybase/sales
If you use an LDAP server as an external naming service, the initial context must follow the syntax and schema of the LDAP server. LDAP servers have predefined schema for common objects such as country, organization, and organizational unit. EJB Server uses the following format for an LDAP-compatible initial context:
ou=<organizational unit>, o=<organization>, c=<country>
Using the previous examples, the initial contexts would be:
ou=finance,o=sybase,c=US ou=marketing,o=sybase,c=US ou=sales,o=sybase,c=US
On start-up, the name server binds all object implementations on an EJB Server to the initial context of the server on which the object is installed. Once the server binds an object, the structure of the resulting name context is:
<initial context>/<package>/<component>
where
<initial context> is the initial context property for the server where the component is installed.
<package> is the name of the package being bound, as displayed in the Adaptive Server plug-in.
<component> is the name of the component being bound, as displayed in the Adaptive Server plug-in.
You can set the server properties to enable password
protection for name binding on a EJB Server name server. See “Name binding password security”.
