Software Requirements

Access Manager has specific minimum software requirements, including:

• Operating System Requirements

• Web Container Requirements

• Directory Server Requirements

• Java Development Kit (JDK) Software Requirements

• Access Manager Session Failover Requirements

For the latest information about the software requirements, including supported releases, any required patches, and known limitations, see the Sun Java System Access Manager 7 2005Q4 Release Notes.

Operating System Requirements

Access Manager 7 2005Q4 is supported on these platforms:

• Solaris^TM Operating System (OS), SPARC® based systems, versions 8, 9, and 10

• Solaris^TM OS on x86 platforms, versions 9 and 10

• Red Hat^TM Linux, Advanced Server and Enterprise Server

For information about downloading OS patches and patch clusters, see SunSolve Online at http://sunsolve.sun.com/.

To list the patches currently installed on a Solaris system, use the showrev -p command.

Web Container Requirements

Access Manager 7 2005Q4 supports the following web containers for either a full installation or an SDK-only installation:

• Sun Java System Web Server

• Sun Java System Application Server

• BEA WebLogic

• IBM WebSphere Application Server

For the supported versions of these web containers, see the Sun Java System Access Manager 7 2005Q4 Release Notes.

When a policy agent is installed on an Access Manager web container, it uses approximately 10 Mbytes of disk space. This additional space must be considered when configuring the web container. For more information, see the Sun Java System Access Manager Policy Agent 2.2 User’s Guide.

Directory Server Requirements

Access Manager 7 2005Q4 has the following requirements for an LDAP directory server:

• The Access Manager information tree, which contains the following information, is stored in Sun Java System Directory Server:

  • How users authenticate

  • Which resources users can access

  • What information is available to applications after users are given access to resources

• The Access Manager identity repository is used to store user data such as users and groups. Access Manager 7 2005Q4 can use Sun Java System Directory Server or an LDAP version 3 (LDAP v3) compliant directory server as the identity repository.

For more information about the Access Manager information tree and identity repository, see the Sun Java System Access Manager 7 2005Q4 Technical Overview.

Java Development Kit (JDK) Software Requirements

For the specific version of the JDK software required by Access Manager 7 2005Q4, see the Sun Java System Access Manager 7 2005Q4 Release Notes.

Access Manager Session Failover Requirements

If you are planning to implement Access Manager session failover, these components are required:

• Web container to run Access Manager: Sun Java System Web Server, Sun Java System Application Server, IBM WebSphere Application Server, or BEA WebLogic.

• Sun Java System Directory Server. All Access Manager instances must access the same Directory Server.

• Sun Java System Message Queue. The Message Queue broker cluster manages the session messages between Access Manager instances and the session store database.

• Berkeley DB by Sleepycat Software, Inc. (http://www.sleepycat.com/) is the default session store database. Use the version that is distributed with the Sun Java Enterprise System 2005Q4 release.

Access Manager session failover is supported on the following platforms:

• Solaris^TM OS, SPARC® based systems, versions 8, 9, and 10

• Solaris^TM OS on x86 platforms, versions 9 and 10

• Red Hat^TM Linux, Advanced Server and Enterprise Server

For the latest information about the supported versions of these platforms and components, see the Sun Java System Access Manager 7 2005Q4 Release Notes.

For more information, see Implementing Access Manager Session Failover.