This is an architectural diagram showing how COREid components communicate with Oracle Application Server middle-tier components.
On the COREid side, there are the following:
A special browser client for COREid management: Communicates with the COREid Web server (shown to be Oracle HTTP Server, for example).
COREid Web server (shown to be Oracle HTTP Server, for example): Has WebGate, Access Manager, and WebPass installed. WebGate communicates with Access Server. Access 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 COREid 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.)