Running the Java Enterprise System (Java ES) Installer

Install the first Access Manager instance on a host server by running the Java ES installer. Considerations for running the installer include:

• When you run the installer, you can also install other Java ES components such as Directory Server, Message Queue, and either Web Server or Application Server as the Access Manager web container.

• After installation, the amconfig script and the amsamplesilent configuration file are available in the following directory, depending on your platform:

  • Solaris systems: AccessManager-base /SUNWam/bin

  • Linux systems: AccessManager-base/identity/bin

  Where: 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.

  On Windows systems, the amconfig.bat and AMConfigurator.properties files are available in the default installation directory: C:\Program files\Sun\JavaES5.

• When you run the installer, specify either the Configure Now or Configure Later option.

  • Configure Now: You configure Access Manager and the various Java ES components when you run the installer by choosing options (or default values). Not all Java ES components support this option.

  • Configure Later: When you run the Java ES installer, you specify only minimal configuration values. Then, you later configure the specific components by running a script or using an administration console. Access Manager provides the amconfig script and amsamplesilent file for postinstallation configuration.

• If you want to use an existing Directory Server that already contains user data, check ”Yes” for “Is Directory Server provisioned with user data?”.

• To use BEA WebLogic Server or IBM WebSphere Application Server as the web container, you must choose the Configure Later option when you install Access Manager, as follows:

  1. Install BEA WebLogic Server or IBM WebSphere Application Server by following the respective BEA or IBM product documentation.

  2. Install Access Manager by running the installer with the Configure Later option.

  3. Configure Access Manager for the web container by setting variables in the amsamplesilent configuration file (or a copy of the file) and then running the amconfig script.

For information about running the installer, see the Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

Running the Java ES Installer on UNIX and Linux Systems

Considerations for running the Java ES installer on Solaris, HP-UX, and Linux systems to install an Access Manager instance include:

• When you run the installer, you can also install other Java ES components such as Directory Server, Message Queue, and either Web Server or Application Server as the Access Manager web container.

• After installation, the amconfig script and the amsamplesilent configuration file are available in the following directory, depending on your platform:

  • Solaris systems: AccessManager-base /SUNWam/bin

  • Linux systems: AccessManager-base/identity/bin

  Where: 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.

• When you run the installer, specify either the Configure Now or Configure Later option.

  • Configure Now: You configure Access Manager and the various Java ES components when you run the installer by choosing options (or default values). Not all Java ES components support this option.

  • Configure Later: When you run the Java ES installer, you specify only minimal configuration values. Then, you later configure the specific components by running a script or using an administration console. Access Manager provides the amconfig script and amsamplesilent file for postinstallation configuration.

• If you want to use an existing Directory Server that already contains user data, check ”Yes” for “Is Directory Server provisioned with user data?”.

• To use BEA WebLogic Server or IBM WebSphere Application Server as the web container, you must choose the Configure Later option when you install Access Manager, as follows:

  1. Install BEA WebLogic Server or IBM WebSphere Application Server by following the respective BEA or IBM product documentation.

  2. Install Access Manager by running the installer with the Configure Later option.

  3. Configure Access Manager for the web container by setting variables in the amsamplesilent configuration file (or a copy of the file) and then running the amconfig script.

For information about running the installer, see the Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

Running the Java ES Installer on Windows Systems

Considerations for running the Java ES installer on Windows systems to install an Access Manager instance include:

• When you run the installer, you can also install other Java ES components such as Directory Server, Message Queue, and either Web Server or Application Server as the Access Manager web container.

• After installation, the amconfig.bat and AMConfigurator.properties files are available in the following default installation directory: C:\Program files\sun\JavaES.

• When you run the installer, specify either the “Configure Automatically during install” or “Configure Manually after install” option.

  • Configure Automatically during install: You configure Access Manager and the various Java ES components when you run the installer by choosing options (or default values). Not all Java ES components support this option.

  • Configure Manually after install: When you run the Java ES installer, you specify only minimal configuration values. Then, you later configure the specific components by running a batch file or using an administration console. Access Manager provides the amconfig.bat and AMConfigurator.properties files for postinstallation configuration.

• If you want to use an existing Directory Server that already contains user data, check ”Yes” for “Is Directory Server provisioned with user data?”.

• To use BEA WebLogic Server or IBM WebSphere Application Server as the web container, you must choose the “Configure Manually after install” option when you install Access Manager, as follows:

  1. Install BEA WebLogic Server or IBM WebSphere Application Server by following the respective BEA or IBM product documentation.

  2. Install Access Manager by running the installer with the “Configure Manually after install” option.

  3. Configure Access Manager for the web container by setting variables in the AMConfigurator.properties configuration file (or a copy of the file) and then running amconfig.bat.

For information about running the installer, see the Sun Java Enterprise System Installation Guide for Windows.