Oracle B32100-01 - Manual (Page 138)

Installing an OracleAS Cold Failover Cluster (Identity Management) Configuration
8-14 Oracle Application Server Installation Guide
If you meet these requirements, you need to configure the CSS daemon on the other
node. The CSS daemon synchronizes ASM instances with the database instances that
use the ASM instances for database file storage.
To configure the CSS daemon:
1. Stop all the processes in the OracleAS Cold Failover Cluster (Infrastructure) home.
2. Stop the CSS daemon. You can do this by running the following command as root.
# /sbin/init.d/init.cssd
3. Fail over the IP and the disk to the other node.
4. On the other node, run the following command as root:
# $ORACLE_HOME/root.sh
ORACLE_HOME is where you installed the OracleAS Cold Failover Cluster
(Infrastructure).
Step 4 Install OracleAS Single Sign-On and Oracle Delegated Administration
Services
You install OracleAS Single Sign-On and Oracle Delegated Administration Services on
the local disks of each node. You perform these installations separately.
Pre-Installation Steps
This installation is actually an OracleAS Cluster (Identity Management) installation.
As such, you perform the OracleAS Cluster (Identity Management) setup steps in
Chapter 9, "Installing in High Availability Environments: OracleAS Cluster (Identity
Management)"
:
■
Section 9.2.1, "Use the Same Path for the Oracle Home Directory (recommended)"
■
Section 9.2.2, "Synchronize Clocks on All Nodes"
■
Section 9.2.3, "Configure Virtual Server Names and Ports for the Load Balancer"
Installation Steps
The steps are the same as those listed in Section 9.6.5, "Installing OracleAS Single
Sign-On and Oracle Delegated Administration Services on Each Node" .
8.5 Installing an OracleAS Cold Failover Cluster (Identity Management)
Configuration
Figure 8–3 shows an OracleAS Cold Failover Cluster (Identity Management)
configuration.
This configuration is suitable if you have the OracleAS Metadata Repository database
in a separate highly available environment and you want to use an active-passive
configuration for the Oracle Identity Management components. You install the Oracle
Identity Management components on a shared disk different from the share disk that
contains the OracleAS Metadata Repository database.
This configuration includes:
■
two clustered nodes
■
storage devices local to each node