Deployment Example 1: Access Manager 7.0 Load Balancing, Distributed Authentication UI, and Session Failover

ProcedureTo Verify Successful Directory Server Load Balancing and System Failover

For each of the Access Manager servers, perform the following steps to confirm its directory accesses are all directed to one and only one Directory Server instance, and that system failover and recover work properly. The following section describes how to perform the sanity check for the first Access Manager instance. Substitute the console URL with that of the second Access Manager instance when you perform the task for the second Access Manager instance.

  1. Confirm that the load balancer is properly configured for simple persistence.

    1. As a root user, log into host DirectoryServer-1 and host DirectoryServer-2.

    2. For each server, use the tail command to watch the Directory Server access log.

      # tail-f logs/access

    3. Start a new browser and go to the Access Manager 1 URL.

      Example: http://AccessManager-1.example.com:1080/amserver/console

    4. Log in to the Access Manager console using the following information:

      Username

      amadmin

      Password

      4m4dmin1

    5. Navigate inside the Access Manager console while paying attention to the Directory Server access log.

      In the access log, you should see all directory accesses are directed to one Directory Server instance only, excluding the health check probing from the load balancer device. The navigation should not have any errors. Logout and close the browser if successful.

  2. Confirm that Directory Server failover works properly.

    1. Shut down Directory Server 1.

    2. Start a new browser and go to the Access Manager URL.

      Example: http://AccessManager-1.example.com:1080/amserver/console

    3. Log in to the Access Manager console using the following information:

      Username

      amadmin

      Password

      4m4dmin1

    4. Navigate inside the Access Manager console while paying attention to the Directory Server access logs.

      # cd /var/opt/mps/serverroot/slapd-data/logs

      In the access logs, you should see all directory accesses are directed only to Directory Server 2. The navigation should not have any errors. Log out and close the browser if successful.

    5. Restart Directory Server 1, and stop Directory Server 2.

    6. Start a new browser go to the Access Manager URL.

      Example: http://AccessManager-1.example.com:1080/amserver/console

    7. Log in to the Access Manager console using the following information:

      Username

      amadmin

      Password

      4m4dmin1

    8. Navigate inside the Access Manager console,

      Watch the access logs of both Directory Server instances. You should see all directory accesses (excluding health checks by load balancer) are directed to only Directory Server 1. The navigation should not have any errors.

    9. Log out and close the browser if successful.

  3. Restart Directory Server 2.

    Confirm that both Directory Servers are restarted and running.