Requirements and Where to Find More Information

Sun Java System Application Server 9.1 (or Application Server 9.0) must be installed and running on the server where you plan to deploy Access Manager 7.1 or the Access Manager 7.1 SDK. 

You should be familiar with using the Application Server 9.1 Administration Console or command-line interface (CLI) to perform administrative tasks such as:  

• Verifying, starting, and stopping an Application Server 9.1 instance

• Deploying a web application from a WAR file

If the Java Security Manager is enabled, you must add the Access Manager 7.1 permissions to the Application Server 9.1 server.policy file. See Adding Access Manager Permissions to the Application Server 9.1 server.policy File.

Application Server 9.1 documentation collection: 

http://docs.sun.com/coll/1343.4

The Access Manager 7.1 SDK requires access to an Access Manager 7.1 full server installation that is configured and running. This Access Manager 7.1 server installation can be on a remote server or on another instance on the same server where you plan to deploy the Access Manager 7.1 SDK. 

To install Access Manager 7.1 server, use either of these methods, depending on the requirements of your deployment: 

• If your deployment requires Legacy Mode (including the Legacy Mode Console) or the ampassword application (which is used for the password reset of users), you must use the Sun Java Enterprise System (Java ES) 5 Update 1 installer.

• If your deployment requires Realm Mode but not the ampassword application, you can deploy Access Manager 7.1 from a WAR file.

Running the Java ES 5 Update 1 Installer:

Installing Access Manager 7.1 Using the Java ES 5 Update 1 Installer

Deploying a WAR File:

Deploying an Access Manager 7.1 WAR File With Application Server 9.1

Sun Java System Directory Server must be installed and running, usually on a remote server. 

Directory Server Enterprise Edition 6.0 documentation collection: 

http://docs.sun.com/coll/1224.1