To Verify Successful Directory Server Load Balancing and System Failover for Access Manager 1 and Access Manager 2

Perform the following steps to confirm that Access Manager directory requests are directed to only one instance of Directory Server, and that system failover and recovery work properly. The steps in this procedure are specific to Access Manager 1. Substitute http://AccessManager-2.example.com:1080/amserver/console where appropriate to perform this procedure for Access Manager 2.

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

   1. As a root user, log in to the DirectoryServer–1 and the DirectoryServer–2 host machines.

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

      # cd /var/opt/mps/am-config/logs # tail-f logs/access

   3. Access http://AccessManager-1.example.com:1080/amserver/console from a web browser and log in to the Access Manager 1 console as the default administrator.

      Username

      amadmin

      Password

      4m4dmin1

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

      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.

   5. Log out of the Access Manager 1 console and close the browser when successful.

2. Confirm that Directory Server failover is working properly.

   1. Stop Directory Server 1 instance.

      # cd /var/opt/mps/serverroot/ds6/bin # ./dsadm stop /var/opt/mps/am-config Server stopped

   2. Access http://AccessManager-1.example.com:1080/amserver/console from a web browser and log in to the Access Manager 1 console as the default administrator.

      Username

      amadmin

      Password

      4m4dmin1

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

      You should see all directory accesses are directed to Directory Server 2. The navigation should not have any errors.

   4. Log out and close the browser when successful.

   5. Start the Directory Server 1 instance.

      # cd /var/opt/mps/serverroot/ds6/bin # ./dsadm start /var/opt/mps/am-config Server started

   6. Stop Directory Server 2 instance.

      # cd /var/opt/mps/serverroot/ds6/bin # ./dsadm stop /var/opt/mps/am-config Server stopped

   7. Access http://AccessManager-1.example.com:1080/amserver/console from a web browser and log in as the administrator, if necessary.

      Username

      amadmin

      Password

      4m4dmin1

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

      You should see all directory accesses are directed to Directory Server 1. The navigation should not have any errors.

   9. Log out and close the browser when successful.

   10. Start the Directory Server 2 instance.

       # cd /var/opt/mps/serverroot/ds6/bin # ./dsadm start /var/opt/mps/am-config Server started

3. Confirm that both Directory Servers are running and log out of both host machines.

4. Repeat this procedure for Access Manager 2.

   Substitute http://AccessManager-2.example.com:1080/amserver/console where applicable and perform these steps again.