This is an architectural diagram showing how Oracle Access Manager components communicate with Oracle Application Server middle-tier components.

On the Oracle Access Manager side, there are the following:

• A special browser client for management: Communicates with the Oracle Access Manager Web server.

• Oracle Access Manager Web server (Oracle HTTP Server, for example): Has WebGate, Policy Manager, and WebPass installed. WebGate communicates with Access Server. Policy Manager communicates with the LDAP server (such as Oracle Internet Directory). WebPass communicates with Identity Server.

• Access Server: Communicates with WebGate, the LDAP server, each OC4J instance in the middle-tier, and Oracle HTTP Server in the middle tier.

• Identity Server: Communicates with WebPass and the LDAP server.

On the Oracle Application Server middle tier, there are the following:

• Oracle HTTP Server: Has WebGate and mod_oc4j installed. WebGate communicates with Access Server; mod_oc4j communicates with each OC4J instance.

• OC4J instances: Each instance has the Access SDK, which communicates with the Access Server. Each OC4J instance communicates with mod_oc4j in Oracle HTTP Server.

• Clients: A user's browser client, using either the Oracle Access Manager SSO cookie or HTTP header variables for authentication, communicates with Oracle HTTP Server. A user's Web service client, using either username token authentication, X.509 token authentication, or SAML token authentication, communicates with an OC4J instance. A user's EJB client, using EJB authentication, communicates with an OC4J instance.

(End of description.)