The figure shows the steps for transforming to an OracleAS Cold Failover Cluster (Identity Management) topology. There are five steps:
Install the Oracle Database on a hardware cluster to create a cold failover cluster database. The figure shows two nodes in a hardware cluster, with vendor clusterware running on each node, and both nodes are connected to a shared storage. The second node connects to the shared storage only on failover. The Oracle home for the OracleAS Metadata Repository database resides on the shared storage. You transfer the contents of the source OracleAS Metadata Repository to the cold failover cluster database.
Change the source Oracle Identity Management instance to point to the cold failover cluster database. The figure shows a line from the source Oracle Identity Management instance to the OracleAS Metadata Repository running on the cold failover cluster database.
Install Oracle Identity Management on the shared storage. The figure shows the Oracle home for the Oracle Identity Management instance on the shared storage of the hardware cluster. Cluster node 1 is the active node and it runs the Oracle Identity Management components (Oracle HTTP Server, OracleAS Single Sign-On, Oracle Delegated Administration Services, Oracle Internet Directory, Oracle Directory Integration and Provisioning) as well as the OracleAS Metadata Repository database. Cluster node 2 is the standby node; it runs the same components.
Configure the new Oracle Identity Management and middle tier to use the virtual hostname. The figure shows the hardware cluster associated with a virtual hostname and IP. In this step, you associate the new Oracle Identity Management instance and existing middle tiers to use the virtual hostname and IP.
Deregister the source Oracle Identity Management. In the OracleAS Cold Failover Cluster (Identity Management) topology, you use the Oracle Identity Management running on the hardware cluster. You do not need the source Oracle Identity Management.