Use the following list of procedures as a checklist for configuring and verifying session failover.
Access http://LoadBalancer-3.example.com:7070/amserver/UI/Login from a web browser.
Log in to the Access Manager console as the administrator.
amadmin
4m4dmin1
Click the Configuration tab.
Under Global properties, click Session.
Under Secondary Configuration Instance, click New.
In the Add Sub Configuration page, provide the following information.
Enter the load balancer URL https://loadbalancer-3.example.com:9443
The case of the load balancer URL should match that of the Primary Site ID.
Enter msgquser
Enter m5gqu5er
Enter m5gqu5er
Keep the default value of 5000.
Enter MessageQueue-1.example.com:7777,MessageQueue-2.example.com:7777.
This is the Message Queue broker address list. Enter multiple values using a comma and no space.
Click Add.
Click Save.
Log out of the Access Manager console.
Restart the Web Server 1 instance.
Restart the Web Server 2 instance.
Both Access Manager 1 and Access Manager 2 should be up and running before you begin this verification procedure.
As a root user, log in to the AccessManager–2 host machine.
Change to the bin directory.
# cd /opt/SUNWwbsvr/https-AccessManager-2.example.com/bin |
Stop Access Manager 2.
# ./stopserv |
Access http://LoadBalancer-3.example.com:7070/amserver/UI/Login from a web browser.
Log in to the Access Manager console as the administrator.
amadmin
4m4dmin1
Click the Sessions tab.
In the View field, select Access Manager-1.example.com:1080 from the drop down list.
Verify that only amadmin exists in the Sessions table.
In the View field, select Access Manager-2.example.com:1080 from the drop down list.
You will see an error message indicating the server is down.
Leave this browser window 1 open.
Start Access Manager 2.
# ./startserv |
As a root user, log in to the AccessManager–1 host machine.
Change to the bin directory.
# cd /opt/SUNWwbsvr/https-AccessManager-1.example.com/bin |
Stop Access Manager 1.
# ./stopserv |
Going back to the Access Manager console in browser window 1, under the Sessions tab, select Access Manager-1.example.com:1080 from the View drop down list.
You will see an error message indicating the server is down.
Now select Access Manager-2.example.com:1080 from the View drop down list.
Verify that only amadmin exists in the Sessions table. This indicates that although AccessManager–1 was stopped, the Access Manager LoadBalancer-3 directed the request to AccessManager–2 and a session for amadmin was successfully created in AccessManager–2. If session failover was not enabled, it would have resulted in a login page.
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.