In this procedure, you configure both Access Manager 1 and Access Manager 2 to operate as two instances of a single server. All configuration takes place on the Access Manager 1 host. There is no need to repeat the steps on the Access Manager 2 host.
On AccessManager-1, start a new browser, and go to the URL for the Access Manager console.
Example: http://AccessManager-1.example.com:1080/amserver/console
Log in to the Access Manager console using the following information:
amadmin
4m4dmin1
On the Access Control tab, under Realm Name, click the top-level realm.
In this example, the top-level realm is example.
On the General tab, under Realm Attributes, add AccessManager—2.example.com to the Realms/DNS Aliases list.
Go to Realms > Configuration.
On the Configuration tab, click System Properties > Platform.
On the Platform page, add a new instance name.
Click the Log Out button to log out of the console.
Verify that both Access Manager servers are configured properly.
As a root user, log in to host AccessManager-1.
Restart the Access Manager server by restarting the Web Server.
# cd /opt/SUNWwbsvr/https-AccessManager-1.example.com # ./stop; ./start |
Check for errors on the start-up screen and in the Web Server error log as the server restarts.
As a root user, log in to host AccessManager-2.
Restart the Access Manager server by restarting the Web Server.
# cd /opt/SUNWwbsvr/https-AccessManager-2.example.com # ./stop; ./start |
Check for errors on the start-up screen and in the Web Server error log as the server restarts.
Start a new browser and to go the URL for the other Access Manager server.
Example: http://AccessManager-2.example.com:1080/amserver/console
Log in as to the Access Manager console using the following information:
amadmin
4m4dmin1
If you can log in successfully, close the browser.
If you cannot log in successfully, restart Access Manager 2. Be sure that the Access Manager 2 host can access the Directory Server 1 host.
Log out of the Access Manager console.
When you cannot log in successfully, one way to troubleshoot is to log in using the fully qualified name for the user amadmin . If you can authenticate using the fully qualified name, you can focus on issues other than authentication and log in. In the file /etc/opt/SUNWam/config/AMConfig.properties, look for the following entry:
com.sun.identity.authentication.super.user=uid=amAdmin,ou=People,o=example.com
Use the fully qualified User Name uid=amAdmin,ou=People,o=example.com to log in.