To Verify Load Balancing for the Access Manager Service

This procedure verifies the following:

• that you can interact with Access Manager instances through the load balancer

• that the load balancer provides service failover when an Access Manager instance fails

1. Start the Access Manager instances on am1 and am2, if they are not already running.

2. Start a browser.

3. Go to the Access Manager Console login page by using the load balancer URL

   http://am.pstest.com/amconsole

   The Access Manager Console login page opens.

4. Log in to the Access Manager Console by typing the following values and clicking Login.

   Input Field	Value
   User ID	amadmin
   Password	access-manager-admin-password

   The Access Manager Console opens, which confirms that the load balancer has routed the login request to one of the Access Manager instances.

5. Determine which Access Manager instance handled the login request in Step 4.

   1. Click on the Current Sessions tab.

      The left panel shows both Access Manager instances: http://am1.pstest.com:80 and http://am2.pstest.com:80

   2. Check for an amadmin session on each instance.

      You can display the sessions existing on each instance by clicking on the small triangle adjacent to each.

   3. Note the instance that owns the amadmin session.

6. Simulate a failure of the Access Manager instance that was noted in Step 5.

   Failure of an Access Manager instance can result from a computer failure, a software failure, or a network failure. The method employed for simulating a failure in this service failover verification procedure is to shut down the Access Manager instance (by shutting down the Application Server instance in which it runs). Additionally, you could also simulate failure by unplugging the network cable or disabling the interface.

   Run the following command on the computer (am1 or am2) hosting the instance identified in Step 5.

   # /opt/SUNWappserver/appserver/bin/asadmin stop-domain

7. In the Access Manager Console, click on the Identity Management tab.

   If service failover has succeeded, the login page should once again be displayed, indicating that content is now being served from the remaining Access Manager instance.

8. Log in once again, as directed in Step 4.

9. Confirm the service failover.

   1. Click on the Current Sessions tab.

      The left panel shows both Access Manager instances: http://am1.pstest.com:80 and http://am2.pstest.com:80

   2. Check for an amadmin session on the failed instance.

      You can display the existing sessions by clicking on the small triangle adjacent to the instance. In this case, an “Failed to get the valid sessions...” error message should be displayed (the instance is shut down).

   3. Check for an amadmin session on the remaining instance.

      In this case, an amadmin session should be displayed.

10. Recover the simulated failure of your original Access Manager instance.

    Run the following command on the computer (am1 or am2) on which the Application Server instance was shut down in Step 6.

    # /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1

    When prompted, type the app-server-admin-password.