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:
Install BEA WebLogic Server or IBM WebSphere Application Server by following the respective BEA or IBM product documentation.
Install Access Manager by running the installer with the “Configure Manually after install” option.
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.