Before you can deploy a new instance of Access Manager, you must create and start the new web container instance using the administration tools for the web container. For information, refer to the specific web container documentation:
For Web Server, see http://docs.sun.com/coll/1308.1
For Application Server, see http://docs.sun.com/coll/1310.1
The steps described in this section only apply to an Access Manager instance that has been installed with the Configure Now option. If you are planning to use WebLogic or WebSphere as web containers, you must use the Configure Later option when installing Access Manager. See Chapter 2, Installing and Configuring Third-Party Web Containers for more information.
This section describes how to deploy an additional Access Manager instance on a different host server and update the Platform Server List.
Log in as an administrator, depending on the web container for the instance. For example, if Web Server 6.1 will be the web container for the new instance, log in either as superuser (root) or as the user account for the Web Server Administration Server.
Copy the amsamplesilent file to a writable directory and make that directory your current directory. For example, you might create a directory named /newinstances.
Tip Rename the copy of the amsamplesilent file to describe the new instance you want to deploy. For example, the following steps use an input file named amnewws6instance to install a new instance for Web Server 6.1.
Set the following variables in the new amnewws6instance file:
Set other variables in the amnewws6instance file as required for the new instance you want to create. For a description of these variables, refer to the tables in the following sections:
Important All Access Manager instances must use the same value for the password encryption key. To set the AM_ENC_PWD variable for this instance, copy the value from the am.encryption.pwd property in the AMConfig.properties file for the first instance.
In case you might need to uninstall this instance later, save the amnewws6instance file.
Run the amconfig, specifying the new amnewws6instance file. For example, on Solaris systems:
# cd opt/SUNWam/bin/ # ./amconfig -s ./newinstances/amnewws6instance
The -s option runs the amconfig script in silent mode.
The amconfig script calls other configuration scripts as needed, using variables in the amnewws6instance file to deploy the new instance.
When you crate an additional container instance, you must update the Access Manager Platform Server list to reflect the addition of the container(s).
Log in to the Access Manager Console as the top-level administrator.
Click on the Service Configuration tab.
Click on the Platform service.
Enter the following information for the new instance in the Server List:
The instance number should be the next available number that is not in use.