Chapter 5 Naming Services

Using an LDAP server with EAServer

To add persistent object name storage capabilities to EAServer, you can use an external directory naming service, such as an LDAP server. The server properties include an optional URL for specifying the port for the external name server.

When you use an external name server, EAServer uses JNDI to communicate with the name server through the specified URL.

LDAP object schema and EAServer objects

LDAP servers have predefined schema for common objects such as country, organization, and organizational unit. EAServer uses the following format for an LDAP-compatible initial context:

ou=<organizational unit>, o=<organization>, c=<country>

Storing EAServer object bindings on an LDAP server

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

Steps How the EAServer name server connects to an LDAP server

  1. On start-up, the EAServer name server connects to the LDAP server using the URL specified in the EAServer name server's Naming Service properties.
  2. The EAServer name server authenticates the connection to the LDAP server using the manager DN specified in the EAServer name server's Naming Service properties.
  3. The EAServer name server attempts to retrieve any existing matching name contexts from the LDAP server. If successful, EAServer uses the existing name context information.
  4. The EAServer name server prepares the server object with the required attributes.
  5. The EAServer 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. EAServer adds any new package/component name context information, or modifies the existing information if necessary.

 

Copyright © 2002 Sybase, Inc. All rights reserved.