A simple PingDirectory server deployment is illustrated in the following figure.

Canvas 1 Layer 1 Client request Client connection policy Subtree view Desktop Proxying request processor Load balancing algorithm Server 4 Server 4 Server 4 LDAP external servers

Processing steps

  1. A client request is initiated.
  2. The client connection policy processes the client request.
  3. The client connection policy contains a subtree view, which defines the portion of the directory information tree (DIT) available to clients and determines if the DIT is available.
  4. After the PingDirectory server determines that the DIT is available, it passes the request to the request processor, which defines the logic for processing the request.
  5. The request processor passes the request to a load-balancing algorithm, which determines the server in a set of servers responsible for handling the request.
  6. The request is passed to the LDAP external server.
    Note:

    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 can be used by the load-balancing algorithm for determining how to route requests.