Storing EJB Server object bindings on an LDAP server

When you use an LDAP server with an EJB Server name server, the CosNaming component binds all implemented objects on the servers that use the designated EJB Server name server, and stores the name context information on the LDAP server. If EJB Server detects previously-bound objects on the external name server, it updates the existing bindings with current name context information. When you shut down the EJB Server, it unbinds the stored information.

To connect an EJB Server name server to an LDAP server:

1. On start-up, the EJB Server name server connects to the LDAP server using the URL specified in the EJB Server name server’s Naming Service properties.

2. The EJB Server name server authenticates the connection to the LDAP server using the manager DN specified in the EJB Server name server’s Naming Service properties.

3. The EJB Server name server attempts to retrieve any existing matching name contexts from the LDAP server. If successful, the EJB Server name server uses the existing name context information.

4. The EJB Server name server prepares the server object with the required attributes.

5. The EJB Server name server attempts to add the server object to the LDAP server. If the object already exists, the LDAP server updates the existing object with the current attributes.

6. The EJB Server server adds any new package/component name context information, or modifies the existing information if necessary.