Oracle B32100-01 - Manual (Page 119)

Installing in High Availability Environments: Overview 7-1
7
Installing in High Availability Environments:
Overview
This chapter provides an overview of the high availability configurations supported
by Oracle Application Server. Subsequent chapters provide the details. This chapter
also lists the common requirements.
Contents of this chapter:
■
Section 7.1, "Overview of High Availability Configurations"
■
Section 7.2, "Installation Order for High Availability Configurations"
■
Section 7.3, "Requirements for High Availability Configurations"
7.1 Overview of High Availability Configurations
This chapter provides only a brief overview of the high availability configurations in
Oracle Application Server. For a complete description of the configurations, see the
Oracle Application Server High Availability Guide.
Oracle Application Server supports the following types of high availability
configurations at installation time. Note that there are multiple variants of each type.
■
Section 7.1.1, "OracleAS Cold Failover Cluster"
■
Section 7.1.2, "OracleAS Clusters"
■
Section 7.1.3, "OracleAS Disaster Recovery"
■
Section 7.1.4, "Summary of Differences"
For a quick summary of the high availability configurations, see Section 7.1.4,
"Summary of Differences" .
7.1.1 OracleAS Cold Failover Cluster
Oracle Application Server provides an active-passive model for its components using
OracleAS Cold Failover Clusters. In an OracleAS Cold Failover Cluster topology, two
or more Oracle Application Server instances are configured to serve the same
application workload but only one instance is active at any particular time. These
instances run on two different nodes in a hardware cluster. These two nodes also have
access to a shared storage, on which you install the Oracle home for the Oracle
Application Server instance.
One of the nodes in the hardware cluster is the active node. It mounts the shared
storage and runs the Oracle Application Server instance. The other node is the passive,
or standby, node. It runs only when the active node fails. During the failover event, the