This procedure assumes that you have just completed To Verify That the Administrator Session Fails Over.
Access http://LoadBalancer-3.example.com:7070/amserver/UI/Login?realm=users from a second browser window.
Log in to the Access Manager console as testuser1.
testuser1
password
The Edit User page for testuser1 is displayed. Because Access Manager 1 was stopped, the user session is created in Access Manager 2.
Leave browser window 2 open.
Using browser window 1, click the Sessions tab.
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.
On the AccessManager–1 host machine, change to the bin directory.
# cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/bin |
Start AccessManager–1.
# ./startserv |
Both Access Manager–1 and Access Manager–2 are up and running.
On the AccessManager–2 host machine, change to the bin directory.
# cd /opt/SUNWwbsvr/https-AccessManager-2.example.com/bin |
Stop Access Manager–2.
# ./stopserv |
Using browser window 1, click the Sessions tab.
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.
If testuser1 is not displayed, refresh the browser window 2 page.
In the View field, select Access Manager-2.example.com:1080
You will see an error message indicating the server is down.
Log out of the consoles and the host machines.