For a new installation, always install the first instance of Access Manager 7 2005Q4 by running the Sun Java Enterprise System (Java ES) installer. When you run the installer, you can select either of these configuration options for Access Manager:
The Configure Later option installs the Access Manager 7 2005Q4 components, and then after installation, you must manually configure them or run the Access Manager scripts as described in Configuring and Reconfiguring an Instance of Access Manager. If you choose this option, then none of the products that you are currently installing will be configured. For example, if you choose to install Access Manager and Application Server and select the Configure Later option, neither application will be configured.
If you are installing BEA WebLogic or IBM WebSphere Application Server as the Access Manager web container, you must choose the Configure Later option when installing Access Manager. See Chapter 2, Installing and Configuring Third-Party Web Containers for more information.
For information about the installer, refer to the Sun Java Enterprise System 2005Q4 Installation Guide for UNIX.
The Java Enterprise System installer installs the Access Manager 7 2005Q4 amconfig script and sample silent mode input file (amsamplesilent) in the AccessManager-base /SUNWam/bin directory on Solaris systems or the AccessManager-base/identity/bin directory on Linux systems.
AccessManager-base represents the Access Manager base installation directory. On Solaris systems, the default base installation directory is /opt, and on Linux systems, it is /opt/sun. However, you can specify another directory, if you prefer, when you run the installer.
The amconfig script is a top-level script that calls other scripts as needed to perform the requested operation. For more information, see the Access Manager amconfig Script.
The sample configuration script input file (amsamplesilent) is a template that you can use to create the input file that you must specify when you run the amconfig script in silent mode.
This sample configuration script input file is an ASCII text file that contains Access Manager configuration variables. Before you run the amconfig script, copy (and rename, if you wish) the amsamplesilent file, and then edit the variables in the file based on your system environment. The configuration variables are in the following format:
DEPLOY_LEVEL=1 NEW_INSTANCE=true SERVER_HOST=ishost.example.com
For a list of the variables you can set in a configuration script input file, see the Access Manager Sample Configuration Script Input FileAccess Manager Sample Configuration Script Input File.
The format of the sample configuration script input file used when you run the amconfig script in silent mode does not follow the same format or necessarily use the same variable names as a Java Enterprise System silent installation state file. This file contains sensitive data, such as the administrator password. Make sure to protect or delete this file as appropriate.
After you install first instance of Access Manager using the Sun Java Enterprise System installer, you can run the amconfig script to perform the following operations, depending on the values of the variables in the silent mode input file:
Deploy and configure the first instance of Access manager or deploy and configure for additional instances of Access Manager on the same host system. For example, after you configure an additional instance of a web container, you can then deploy and configure a new Access Manager instance for that web container instance.
Reconfigure both the first instance and any additional instances of Access Manager.
Uninstall instances and components of Access Manager that you deployed using the amconfig script.