Log in to the Access Manager Console.
Confirm that Application Server on am1 is running.
# /opt/SUNWappserver/appserver/bin/asadmin list-domains --user admin --terse=true
When prompted, type the app-server-admin-password.
If the Application Server is not running, then start it.
# /opt/SUNWappserver/appserver/bin/asadmin start-domain --user admin domain1
When prompted, type the app-server-admin-password.
Start a browser.
Go to the Access Manager login page:
http://am.pstest.com/amconsole
The Access Manager Console login page opens.
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.
In the Access Manager Console main page, click the Service Configuration tab.
In the Service Configuration tab, navigate to the New Secondary Configuration dialog box.
Locate the Service Name pane on the left side of the tab.
In the Service Name pane, scroll down and click the arrow to the right of Session.
The Session detail is displayed in the right pane.
In the Session detail pane, locate the Secondary Configuration Instances and click New.
The New Secondary Configuration dialog box opens.
In the New Secondary Configuration dialog box, type the following values and click Add.
Input Field |
Value |
---|---|
Instance Name |
http://am.pstest.com:80 (this is the URL for the load balancer) |
Session Store User |
am-svr-usr (the user name you establish in the following procedure for connecting to the Message Queue Server) |
Session Store Password |
am-svr-usr-password (the password you set in the following procedure) |
Maximum Wait Time |
5000 |
Database URL |
am1.pstest.com:7777,am2.pstest.com:7777 ( the list of broker addresses in the Message Queue broker cluster) |
The Secondary Configuration dialog box closes.
Click Save to save your changes.