The figure shows the configuration before and after the transformation. The left side of the figure shows the non-high availability topology. It consists of a middle tier, an Oracle Identity Management instance, and an OracleAS Metadata Repository running in a single-instance database.

The right side of the figure shows the distributed OracleAS Cluster (Identity Management) topology:

• Oracle HTTP Server, OracleAS Single Sign-On, and Oracle Delegated Administration Services running on two nodes. Both of these nodes are active, and are fronted by a load balancer. This load balancer is configured with an HTTP virtual server name of "sso.mydomain.com".

  This load balancer is also configured with another HTTP virtual server name of "mt.mydomain.com". Clients can use this virtual server name to access the middle tier.

• Oracle Internet Directory and Oracle Directory Integration and Provisioning running on two other nodes. One of these nodes is from the non-high availability topology. These nodes are fronted by a load balancer, and this load balancer is configured with an LDAP virtual server name of "oid.mydomain.com".

  The OracleAS Single Sign-On / Oracle Delegated Administration Services instances and the middle-tier instance use "oid.mydomain.com" to access Oracle Internet Directory.

• OracleAS Metadata Repository running in a Real Application Clusters database. The Real Application Clusters database runs on two clustered nodes and the nodes have access to a shared storage. The Oracle home for the database is located on each node in the Real Application Clusters, but the data files for the database are stored on the shared storage.

  All the Oracle Identity Management instances use the OracleAS Metadata Repository, which has been transformed into a Real Application Clusters database. There are two nodes in the Real Application Clusters. The Oracle home for the database is located on the local storage of each node, and the data files for the database are located on a shared storage.