Oracle B32100-01 - Manual (Page 139)

Installing an OracleAS Cold Failover Cluster (Identity Management) Configuration
Installing in High Availability Environments: OracleAS Cold Failover Cluster 8-15
■
two shared disks that can be accessed by both nodes. One shared disk contains the
Oracle home for the database (on which you will load the OracleAS Metadata
Repository), and on the other shared disk, you will install Oracle Identity
Management.
During normal operation, node 1, which is the primary node, is the active node. It
mounts both shared disks to access the Oracle Identity Management and database
files, runs the Oracle Identity Management and database processes, and handles all
requests.
If node 1 goes down for any reason, the clusterware fails over the Oracle Identity
Management and database processes to node 2. Node 2 becomes the active node,
mounts both shared disks, runs the processes, and handles all requests.
To access the active node in an OracleAS Cold Failover Cluster, clients, including
middle-tier components and applications, use the virtual hostname associated with the
OracleAS Cold Failover Cluster. The virtual hostname is associated with the active
node (node 1 during normal operation, node 2 if node 1 goes down). Clients do not
need to know which node (primary or secondary) is servicing requests.
You also use the virtual hostname in URLs that access the infrastructure. For example,
if vhost.mydomain.com is the name of the virtual host, the URLs for the Oracle
HTTP Server and the Application Server Control would look like the following:
URL for: Example URL
Oracle HTTP Server, Welcome page http://vhost.mydomain.com:7777
Oracle HTTP Server, secure mode https://vhost.mydomain.com:4443
Application Server Control http://vhost.mydomain.com:1156