Oracle B32100-01 - Manual (Page 143)

Installing a Distributed OracleAS Cold Failover Cluster (Identity Management) Configuration
Installing in High Availability Environments: OracleAS Cold Failover Cluster 8-19
8.6 Installing a Distributed OracleAS Cold Failover Cluster (Identity
Management) Configuration
This configuration is suitable:
■
if you want to run Oracle Internet Directory and Oracle Directory Integration
Platform on the same tier as your database, and Oracle Delegated Administration
Services and OracleAS Single Sign-On on a different tier
■
if you want to install the OracleAS Metadata Repository in an existing cold
failover cluster database
Figure 8–4 shows a distributed OracleAS Cold Failover Cluster (Identity Management)
configuration.
It consists of:
■
two nodes running Oracle Delegated Administration Services and OracleAS Single
Sign-On. These nodes are accessed through a load balancer.
■
two nodes running in an active-passive configuration. These nodes will run the
existing cold failover cluster database, Oracle Internet Directory, and Oracle
Directory Integration Platform.
■
storage devices local to each node
■
two shared disks. One shared disk contains the database Oracle home. On the
other shared disk, you will install Oracle Internet Directory and Oracle Directory
Integration Platform.
■
firewalls to separate the tiers
Tier Running the Oracle Internet Directory, Oracle Directory Integration Platform,
and Database
In this tier, during normal operation, the active node mounts the shared disks to access
the Oracle Identity Management and database; runs the Oracle Internet Directory,
Oracle Directory Integration Platform, and database processes; and handles all
requests.
If the active node goes down for any reason, the clusterware fails over the processes to
the secondary node (node 2), which becomes the new active node, mounts the shared
disks, runs the processes, and handles all requests.
To access the active node, clients, including middle-tier components and applications,
use the virtual hostname. The virtual hostname is associated with the active node
(which is the primary node during normal operation, the secondary node upon
failover). Clients do not need to know which node (primary or secondary) is servicing
requests.
You need to use the virtual hostname in URLs to access the active node. For example,
if vhost.mydomain.com is the virtual hostname, the URLs for the Oracle HTTP
Server and the Application Server Control for this tier 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