To Verify that the User Session Fails Over

Before You Begin

This procedure assumes that you have just completed To Verify That the Administrator Session Fails Over.

1. Access http://LoadBalancer-3.example.com:7070/amserver/UI/Login?realm=users from a second browser window.

2. Log in to the Access Manager console as testuser1.

   Username

   testuser1

   Password

   password

   The Edit User page for testuser1 is displayed. Because Access Manager 1 was stopped, the user session is created in Access Manager 2.

3. Leave browser window 2 open.

4. Using browser window 1, click the Sessions tab.

5. In the View field, select Access Manager-2.example.com:1080 from the drop down list.

   Verify that amadmin and testuser1 exist in the Sessions table.

6. On the AccessManager–1 host machine, change to the bin directory.

   # cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/bin

7. Start AccessManager–1.

   # ./startserv

   Both Access Manager–1 and Access Manager–2 are up and running.

8. On the AccessManager–2 host machine, change to the bin directory.

   # cd /opt/SUNWwbsvr/https-AccessManager-2.example.com/bin

9. Stop Access Manager–2.

   # ./stopserv

10. Using browser window 1, click the Sessions tab.

    1. In the View field, select Access Manager-1.example.com:1080.

       Verify that amadmin and testuser1 exist in the Sessions table. This indicates that the session successfully failed over to AccessManager–1.

       ---

       Tip –

       If testuser1 is not displayed, refresh the browser window 2 page.

       ---

    2. In the View field, select Access Manager-2.example.com:1080

       You will see an error message indicating the server is down.

11. Log out of the consoles and the host machines.