The figure shows the steps for transforming to an OracleAS Cold Failover Cluster (Identity Management) topology. The figure shows two nodes in a hardware cluster, with Microsoft Cluster Server and Oracle Fail Safe running on each node, and both nodes are connected to a shared storage. The second node connects to the shared storage only on failover.

There are nine steps:

  1. Install Oracle Fail Safe on the local storage of each cluster node, and create a failover group in Oracle Fail Safe.

  2. Install the Oracle home for the cold failover cluster database on the local storage of each cluster node, but place the data files on the shared storage. In this step, you also transfer the contents of the source OracleAS Metadata Repository to the cold failover cluster database.

  3. Set up the new database for high availability. In this step, a line connects the new OracleAS Metadata Repository with Oracle Fail Safe.

  4. 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 new OracleAS Metadata Repository running on the cold failover cluster database.

  5. 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 when cluster node 1 fails.

  6. Configure the new Oracle Identity Management to use the virtual hostname. The figure shows the hardware cluster associated with a virtual hostname and IP. In this step, you associate the virtual hostname and IP with the new Oracle Identity Management instance so that clients can use the virtual hostname and IP to access the Oracle Identity Management instance.

  7. Make the Oracle Identity Management highly available. In this step, a line connects the Oracle Internet Directory instance with Oracle Fail Safe.

  8. Configure the middle tier to use the new Oracle Identity Management instance. The figure shows a line connecting a middle tier with the virtual hostname and IP. The middle tier will access the Oracle Identity Management instance using the virtual hostname and IP.

  9. 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.