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 OracleAS Cold Failover Cluster (Identity Management) topology on UNIX:

Two nodes in a hardware cluster, cluster node 1 and cluster node 2, run Oracle Identity Management and OracleAS Metadata Repository database. On cluster node 1, the components are active, but on cluster node 2, the components are on standby. These cluster nodes also run a vendor clusterware.

The cluster nodes are connected to a shared storage, but only one node, the active node, can mount the shared storage at any one time. The shared storage contains the Oracle homes for the OracleAS Metadata Repository database and for Oracle Identity Management. These are two separate Oracle homes.

Clients such as middle tiers access the OracleAS Metadata Repository and Oracle Identity Management components using a virtual hostname and IP.

If cluster node 1 fails, a failover event occurs and cluster node 2 becomes the active node. It mounts the shared storage and runs the OracleAS Metadata Repository database processes and the Oracle Identity Management processes. The virtual hostname and IP also switch from cluster node 1 to cluster node 2.