Requirements for an Access Manager Single WAR File Deployment

Access Manager web container 

One of the following web containers must be running on the host server where you plan to deploy an Access Manager WAR file:  

• Sun Java System Web Server 7

• Sun Java System Application Server Enterprise Edition 8.2

• BEA WebLogic Server

• IBM WebSphere Application Server

For the versions of WebLogic Server and WebSphere Application Server that are supported as web containers for Access Manager 7.1, see the Sun Java System Access Manager 7.1 Release Notes.

Directory Server 

To store Access Manager configuration data, Directory Server Enterprise Edition 6 is required only for a production deployment. In a test or evaluation environment, you can use the File System option to store the Access Manager configuration data.

The Java ES installer might enforce the Directory Server dependency for Access Manager, but Directory Server is not required if you select the File System option when you configure Access Manager after you deploy the WAR file. For more information, see Configuring Access Manager 7.1 Using the Configurator.

Multiple server deployment: If you are deploying multiple Access Manager instances in a multiple server deployment:

• All Access Manager instances must access the same instance of Directory Server.

• The File System option to store the Access Manager configuration data is not supported.

The Java ES 5 release includes Sun Java System Directory Server Enterprise Edition 6. 

Password encryption key 

Multiple server deployment: If you are using the same WAR file to deploy multiple Access Manager instances in a multiple server deployment, you must use the same password encryption key value for each instance. Copy the encryption key value from the first instance and use this value when you configure each additional instance. You can determine this value from the am.encryption.pwd attribute in the AMConfig.properties file after you deploy the first instance.

Web container runtime user permissions 

If the runtime user of the Access Manager web container instance is a non-root user, this user must be able to write to its own home directory. For example, when installing Web Server 7, the default runtime user for the Web Server instance is webservd. On Solaris systems, the webservd user has the following entry in the /etc/passwd file:

webservd:x:80:80:WebServer Reserved UID:/:

The webservd user does not have permission to write to its default home directory (/). Therefore, you must change the permissions to allow the webservd user to write to its default home directory. Otherwise, the webservd user will encounter an error after you configure Access Manager using the Configurator (configurator.jsp).

LANG environment variable

To run the Configurator, the code set in the LANG environment variable must be set to ISO8859-1.

Access Manager mode 

An Access Manager instance deployed from an Access Manager 7.1 WAR file is always in Realm Mode (AM_REALM=enabled).

Sun Java Enterprise System (Java ES) installer 

To generate an Access Manager 7.1 WAR file, see Generating an Access Manager 7.1 WAR File Using the Java ES Installer.

For information about the installer, see Overview of the Installation Process.