In a simple Directory Proxy Server deployment, a client request is first processed by a client connection policy as illustrated in Figure 1, “Process Flow for Directory Proxy Server”.
The client connection policy contains a subtree view, which defines the portion of the DIT available to clients. Once the Directory Proxy Server determines that the DIT is available, it passes the request to the request processor, which defines the logic for processing the request. The request processor then passes the request to a load-balancing algorithm, which determines the server in a set of servers responsible for handling the request. Finally, the request is passed to the LDAP external server. The LDAP external server contains properties that define the server’s location in a topology and the health checks used to determine if the server is functioning properly. This information may be used by the load-balancing algorithm in the course of determining how to route requests.