Terminology for Directories and Directory Environment Variables

12-6 Oracle Fusion Middleware High Availability Guide ■ The oraInventory location is the same on both nodes and has similar accessibility of the instance or domain owner. The location of the oraInst.loc file, as well as the beahomelist file should be the same. ■ Since a given instance uses the same listen ports irrespective of the machine on which it is currently active, it is required to ensure that the ports used by the Cold Failover Cluster instance are free on both the nodes.

12.2.1.1 Terminology for Directories and Directory Environment Variables

The following list describes the directories and variables used in this chapter: ■ ORACLE_BASE: This environment variable and related directory path refers to the base directory under which Oracle products are installed. ■ MW_HOME: This environment variable and related directory path refers to the location where Fusion Middleware FMW resides. ■ WL_HOME: This environment variable and related directory path contains installed files necessary to host a WebLogic Server. ■ ORACLE_HOME: This environment variable and related directory path refers to the location where a specific Oracle FMW Suite for example, SOA, WebCenter, or Identity Management is installed. ■ ORACLE_COMMON_HOME: The Oracle home that contains the binary and library files that are common to all the Oracle Fusion Middleware software suites. In particular, the Oracle Common home includes the files required for Oracle Enterprise Manager Fusion Middleware Control which is used to manage the Fusion Middleware and the Oracle Java Required Files JRF. ■ DOMAIN Directory: This directory path refers to the location where the Oracle WebLogic Domain information configuration artifacts is stored. ■ ORACLE_INSTANCE: An Oracle instance contains one or more system components, such as Oracle Web Cache, Oracle HTTP Server, or Oracle Internet Directory. An Oracle instance directory contains updatable files, such as configuration files, log files, and temporary files. ■ localdisk: localdisk stands for the root of the directory tree when the FMW install either MW_HOME or DOMAIN HOME is on a local disk. It is used to represent the MW_HOME on local disk. ■ shareddisk: shareddisk stands for root of the directory tree when the FMW install either MW_HOME or DOMAIN HOME is on a shared storage system that is mounted by any one node of a CFC configuration. It is used to represent the MW_HOME on shared disk. Note: Before beginning the transformation, back up of your entire domain. Oracle also recommends creating a local backup file before editing it. For details on backing up your domain, see the Oracle Fusion Middleware Administrator’s Guide. Oracle recommends backing up: ■ All domain directories ■ All Instance homes ■ Optionally, the database repository and the Middleware homes ■ For all the sections below, before changing any file, ensure that a local backup copy is made before editing the file. Active-Passive Topologies for Oracle Fusion Middleware High Availability 12-7 The example values used and recommended for consistency for these directories are: ■ ORACLE_BASE: u01apporacle ■ MW_HOME Apptier: ORACLE_BASEproductfmw ■ ORACLE_COMMON_HOME: MW_HOMEoracle_common ■ WL_HOME: MW_HOMEwlserver_10.3 The following table includes examples of Oracle home, domain home, and domain directory values used for some of the Oracle Fusion Middleware components: Location for Applications Directory: ORACLE_BASEadmindomain_nameapps for example Location for Oracle Instance: ORACLE_BASEadmininstance_name for example All entities on disk that failover as a unit should preferably be on the same mount point. They can, however, be on separate shared storage, on separate mount points as well. Oracle recommends that the mount point for the shared storage is ORACLE_ BASE. In most cases, this ensures that all the persistent bits of a failover unit are on the same shared storage. When more than one Cold Failover Cluster exists on a node, and each fails over independent of the other, different mount points will exist for each such failover unit.

12.2.2 Transforming Oracle Fusion Middleware Infrastructure Components