On Windows systems, run amconfig.bat with configuration parameters specified in the AMConfigurator.properties file (or a copy of the file).
Login as (or become) superuser (root).
Copy the amsamplesilent file and rename the file to describe the new instance you want to configure.
For example, if you plan to configure an Access Manager instance for WebLogic Application Server, you might name the file as am_weblogic_server.
Set the variables in the am_weblogic_server file to configure (or reconfigure) the Access Manager instance. For example:
AM_REALM=enabled DEPLOY_LEVEL=1 NEW_INSTANCE=false WEB_CONTAINER=WAS5 # WebLogic Application Server is the web container DIRECTORY_MODE=4 # Directory Server is provisioned with user data AM_ENC_PW=password-encryption-key-value ...
In a multiple server deployment that shares the same Directory Server, all Access Manager instances must use the same value for the password encryption key. Before you run the amconfig script, set the AM_ENC_PWD variable in the copy of the amsamplesilent file with the same encryption key value used for other instances.
For example, on Solaris systems with Access Manager installed in the default directory, run amconfig using the new am_weblogic_server file as the configuration input file:
# cd /opt/SUNWam/bin/ # ./amconfig -s ./am_weblogic_server
The amconfigscript reads the variables in the am_weblogic_server file and then runs in silent mode (-s option) to configure Access Manager for the WebLogic Application Server web container.
For more information about the amsamplesilent file and running the amconfig script, see Chapter 2, Running the Access Manager amconfig ScriptChapter 2.
Restart the web container.
In case you might need to reconfigure or uninstall this instance later, save the new am_weblogic_server file.