This procedure assumes that you have just completed To Verify That the Administrator Session Fails Over.
Access https://lb-2.example.com:1081/opensso/UI/Login from a second browser window.
Log in to the OpenSSO Enterprise console as testuser1.
testuser1
password
A page with a message that reads You're logged in is displayed. Since the User Profile attribute was set to Ignored, the user's profile is not displayed following a successful login. Because OpenSSO Enterprise 1 was stopped, the user session is created in OpenSSO Enterprise 2.
Leave browser window 2 open.
Using browser window 1, click the Sessions tab.
In the View field, select osso-2.example.com:1081 from the drop down list.
Verify that amadmin and testuser1 exist in the Sessions table.
On the osso–1 host machine, change to the bin directory.
# cd /export/osso80adm/domains/ossodomain/bin |
Start OpenSSO Enterprise 1.
# ./startserv |
Both OpenSSO Enterprise 1 and OpenSSO Enterprise 2 are up and running.
On the osso–2 host machine, change to the bin directory.
# cd /export/osso80adm/domains/ossodomain/bin |
Stop OpenSSO Enterprise 2.
# ./stopserv |
Using browser window 1, click the Sessions tab and do the following sub procedure.
In the View field, select osso-1.example.com:1081.
Verify that amadmin and testuser1 exist in the Sessions table. This indicates that the session successfully failed over to OpenSSO Enterprise 1.
If testuser1 is not displayed, refresh the browser window 2 page.
In the View field, select osso-2.example.com:1081
You will see an error message indicating the server is down.
Log out of the consoles and the host machines.