To Deploy an Additional Access Manager Instance

1. 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.

2. 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.

3. Set the following variables in the new amnewws6instance file:

   DEPLOY_LEVEL=1 NEW_INSTANCE=true

   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:

   • Access Manager Configuration Variables

     • Web Container Configuration Variables

     • Directory Server Configuration Variables

       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.

4. 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.