Overview of the Installation Process

For a new installation, install the first instance of Access Manager and other Sun Java Enterprise System (Java ES) components by running the Java ES installer. Information about the installer includes:

• Getting the Java ES Installer

• Installation Modes

• Installer Configuration Options

If you are deploying an Access Manager WAR file, see Chapter 12, Deploying Access Manager as a Single WAR File.

Getting the Java ES Installer

The Java ES installer is available in a media kit containing CDs or a DVD, as web download, on a pre-installed system, or from a file server on your network.

For more information, see the Getting the Java ES Software in Sun Java Enterprise System 5 Installation Guide for UNIX or the Sun Java Enterprise System 5 Installation Guide for Microsoft Windows.

Installation Modes

You can run the Java ES installer in the following modes:

• Graphical mode: An interactive wizard guides you through a series of choices on installation pages on a graphical workstation.

• Text-based mode: An interactive command-line installer prompts you for responses in a terminal window.

• Silent mode: The installer reads input from a state file, which is a text file containing name-value pairs of configuration information. You create a state file by running the installer with the -no and -saveState options. Then, you edit the state file for the specific host server where you plan to install the various Java ES components. Using a state file is useful for installing multiple instances on different host servers.

Installer Configuration Options

When you run the Java ES installer, you can select either of these configuration options for Access Manager as well as other Java ES components:

• Configure Now: You configure Access Manager and the various Java ES components when you run the installer by choosing options (or using 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 template file for postinstallation configuration.

  If you plan to use BEA WebLogic Server or IBM WebSphere Application Server as the Access Manager web container, you must choose the Configure Later option when you install Access Manager.

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