Access Manager Components

An Access Manager deployment includes the following products and components:

• Web Container

• Directory Server

• Message Queue and Berkeley DB for Session Failover

Web Container

Access Manager must run in one of the following web containers:

• Sun Java System Web Server

• Sun Java System Application Server

• BEA WebLogic Server

• IBM WebSphere Application Server

For the specific versions of each web container that are supported, see the Sun Java System Access Manager 7.1 Release Notes.

Directory Server

Access Manager requires an LDAP directory server for these entities:

• Access Manager Information Tree

• Identity Repository

Access Manager Information Tree

Access Manager 7.1 requires Sun Java System Directory Server to store the Access Manager information tree. Access Manager creates and maintains the Access Manager information tree, which includes the following information pertinent to system access:

• How users authenticate

• Which resources users can access

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

Identity Repository

Access Manager requires an identity repository to store user data such as users and groups. Previous versions of Access Manager required Sun Java System Directory Server as the identity repository. However, in addition to Sun Java System Directory Server, Access Manager 7.1 also supports an LDAP version 3 (LDAP v3) compliant directory server.

Message Queue and Berkeley DB for Session Failover

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

• 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 (http://www.oracle.com/database/berkeley-db.html) is the default session store database.