7 Preparing the File System for an Enterprise Deployment
This chapter describes how to prepare the file system for an Oracle Fusion Middleware enterprise deployment.
- Overview of Preparing the File System for an Enterprise Deployment
This section provides an overview of the process of preparing the file system for an enterprise deployment. - Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment
This section provides reference to the shared storage recommendations when installing and configuring an enterprise deployment. - Understanding the Recommended Directory Structure for an Enterprise Deployment
The diagrams in this section show the recommended directory structure for a typical Oracle Fusion Middleware enterprise deployment. - File System and Directory Variables Used in This Guide
This section lists and describes the file system and directory variables used throughout this guide. - About Creating and Mounting the Directories for an Enterprise Deployment
This section lists the best practices to be followed when creating or mounting the top-level directories in an enterprise deployment. - Summary of the Shared Storage Volumes in an Enterprise Deployment
This section provides a summary of the shared storage volumes required for an enterprise deployment.
7.1 Overview of Preparing the File System for an Enterprise Deployment
This section provides an overview of the process of preparing the file system for an enterprise deployment.
It is important to set up your storage in a way that makes the enterprise deployment easy to understand, configure, and manage. Oracle recommends setting up your storage according to information in this chapter. The terminology defined in this chapter is used in diagrams and procedures throughout the guide.
Use this chapter as a reference to help understand the directory variables used in the installation and configuration procedures.
Other directory layouts are possible and supported, but the model adopted in this guide was designed for maximum availability, providing both the best isolation of components and symmetry in the configuration and facilitating backup and disaster recovery. The rest of the document uses this directory structure and directory terminology.
7.2 Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment
This section provides reference to the shared storage recommendations when installing and configuring an enterprise deployment.
Before you implement the detailed recommendations in this chapter, be sure to review the recommendations and general information about using shared storage in the High Availability Guide.
The recommendations in this chapter are based on the concepts and guidelines described in the High Availability Guide.
Table 7-1 lists the key sections you should review and how those concepts apply to an enterprise deployment.
Table 7-1 Shared Storage Resources in the High Availability Guide
| Section in High Availability Guide | Importance to an Enterprise Deployment |
|---|---|
|
Describes guidelines for disk format and the requirements for hardware devices that are optimized for shared storage. |
|
|
Describes your options for storing the Oracle home on a shared storage device that is available to multiple hosts. For the purposes of the enterprise deployment, Oracle recommends using redundant Oracle homes on separate storage volumes. If a separate volume is not available, a separate partition on the shared disk should be used to provide redundant Oracle homes to application tier hosts. |
|
|
Describes the concept of creating separate domain homes for the Administration Server and the Managed Servers in the domain. For an enterprise deployment, the Administration Server domain home location is referenced by the ASERVER_HOME variable. |
|
|
Provides instructions for setting the location of the transaction logs and JMS stores for an enterprise deployment. |
Note:
Oracle Business Intelligence has an additional shared storage requirement for setting the location of specific Business Intelligence metadata. For more information, see Configuring the Singleton Data Directory (SDD).7.3 Understanding the Recommended Directory Structure for an Enterprise Deployment
The diagrams in this section show the recommended directory structure for a typical Oracle Fusion Middleware enterprise deployment.
The directories shown in the diagrams contain binary files that are installed on disk by the Oracle Fusion Middleware installers, domain-specific files generated via the domain configuration process, as well as domain configuration files that are propagated to the various host computers via the Oracle WebLogic Server pack and unpack commands:
-
Figure 7-1 shows the resulting directory structure on the shared storage device after you have installed and configured a typical Oracle Fusion Middleware enterprise deployment. The shared storage directories are accessible by the application tier host computers.
-
Figure 7-2 shows the resulting directory structure on the local storage device for a typical application tier host after you have installed and configured an Oracle Fusion Middleware enterprise deployment. The Managed Servers in particular are stored on the local storage device for the application tier host computers.
-
Figure 7-3 shows the resulting directory structure on the local storage device for a typical Web tier host after you have installed and configured an Oracle Fusion Middleware enterprise deployment. Note that the software binaries (in the Oracle home) are installed on the local storage device for each Web tier host.
Where applicable, the diagrams also include the standard variables used to reference the directory locations in the installation and configuration procedures in this guide.
Figure 7-1 Recommended Shared Storage Directory Structure for an Enterprise Deployment
* For more information, see About the Node Manager Configuration in a Typical Enterprise Deployment.
Figure 7-2 Recommended Local Storage Directory Structure for an Application Tier Host Computer in an Enterprise Deployment
* For more information, see About the Node Manager Configuration in a Typical Enterprise Deployment.
Figure 7-3 Recommended Local Storage Directory Structure for a Web Tier Host Computer in an Enterprise Deployment
7.4 File System and Directory Variables Used in This Guide
This section lists and describes the file system and directory variables used throughout this guide.
Table 7-2 lists the file system directories and the directory variables used to reference the directories on the Application tier. Table 7-3 lists the file system directories and variables used to reference the directories on the Web tier.
For additional information about mounting these directories when you are using shared storage, see About Creating and Mounting the Directories for an Enterprise Deployment.
Throughout this guide, the instructions for installing and configuring the topology refer to the directory locations using the variables shown here.
You can also define operating system variables for each of the directories listed in this section. If you define system variables for the particular UNIX shell you are using, you can then use the variables as they are used in this document, without having to map the variables to the actual values for your environment.
Note:
As you configure your storage devices to accommodate the recommended directory structure, note the actual directory paths in the Enterprise Deployment Workbook. You will use these addresses later when you enable the IP addresses on each host computer.
For more information, see Using the Enterprise Deployment Workbook .
Table 7-2 Sample Values for Key Directory Variables on the Application Tier
| Directory Variable | Description | Sample Value on the Application Tier |
|---|---|---|
|
ORACLE_BASE |
The base directory, under which Oracle products are installed. |
/u01/oracle |
|
ORACLE_HOME |
The read-only location for the product binaries. For the application tier host computers, it is stored on shared disk. The Oracle home is created when you install the Oracle Fusion Middleware Infrastructure software. You can then install additional Oracle Fusion Middleware products into the same Oracle home. |
/u01/oracle/products/fmw |
|
ORACLE_COMMON_HOME |
The directory within the Oracle Fusion Middleware Oracle home where common utilities, libraries, and other common Oracle Fusion Middleware products are stored. |
/u01/oracle/products/fmw/oracle_common |
|
WL_HOME |
The directory within the Oracle home where the Oracle WebLogic Server software binaries are stored. |
/u01/oracle/products/fmw/wlserver |
|
PROD_DIR |
Individual product directories for each Oracle Fusion Middleware product you install. |
/u01/oracle/products/fmw/prod_dir
The product can be soa, wcc, bi, or another value, depending on your enterprise deployment. |
|
EM_DIR |
The product directory used to store the Oracle Enterprise Manager Fusion Middleware Control software binaries. |
/u01/oracle/products/fmw/em |
|
JAVA_HOME |
The location where you install the supported Java Development Kit (JDK). |
/u01/oracle/products/jdk |
|
SHARED_CONFIG_DIR |
The shared parent directory for shared environment configuration files, including domain configuration, keystores, runtime artifacts, and application deployments |
/u01/oracle/config |
|
ASERVER_HOME |
The Administration Server domain home, which is installed on shared disk. |
/u01/oracle/config/domains/domain_name
In this example, replace domain_name with the name of the WebLogic Server domain. |
|
MSERVER_HOME |
The Managed Server domain home, which is created via the unpack command on the local disk of each application tier host. |
/u02/oracle/config/domains/domain_name
|
|
APPLICATION_HOME |
The Application home directory, which is installed on shared disk, so the directory is accessible by all the application tier host computers. |
/u01/oracle/config/applications
/domain_name
|
|
ORACLE_RUNTIME |
This directory contains the Oracle runtime artifacts, such as the JMS logs and TLogs. Typically, you mount this directory as a separate shared file system, which is accessible by all hosts in the domain. When you run the Configuration Wizard or perform post-configuration tasks, and you identify the location of JMS stores or tlogs persistent stores, then you can use this directory, qualified with the name of the domain, the name of the cluster, and the purpose of the directory. For example: ORACLE_RUNTIME/cluster_name/jms |
/u01/oracle/runtime/ |
|
NM_HOME |
The directory used by the Per Machine Node Manager start script and configuration files. Note: This directory is necessary only if you are using a Per Machine Node Manager configuration. For more information, see About the Node Manager Configuration in a Typical Enterprise Deployment. |
/u02/oracle/config/node_manager |
|
DEPLOY_PLAN_HOME |
The deployment plan directory, which is used as the default location for application deployment plans. Note: This directory is required only when you are deploying custom applications to the application tier. |
/u01/oracle/config/dp |
|
KEYSTORE_HOME |
The shared location for custom certificates and keystores. |
/u01/oracle/config/keystores |
Table 7-3 Sample Values for Key Directory Variables on the Web Tier
| Directory Variable | Description | Sample Value on the Web Tier |
|---|---|---|
|
OHS_ORACLE_HOME |
The read-only location for the Oracle HTTP Server product binaries. For the Web tier host computers, this directory is stored on local disk. The Oracle home is created when you install the Oracle HTTP Server software. |
/u02/oracle/products/fmw |
|
ORACLE_COMMON_HOME |
The directory within the Oracle HTTP Server Oracle home where common utilities, libraries, and other common Oracle Fusion Middleware products are stored. |
/u02/oracle/products/fmw
/oracle_common
|
|
WL_HOME |
The directory within the Oracle home where the Oracle WebLogic Server software binaries are stored. |
/u02/oracle/products/fmw/wlserver |
|
PROD_DIR |
Individual product directories for each Oracle Fusion Middleware product you install. |
/u02/oracle/products/fmw/ohs |
|
JAVA_HOME |
The location where you install the supported Java Development Kit (JDK). |
/u02/oracle/products/jdk |
|
OHS_DOMAIN_HOME |
The Domain home for the standalone Oracle HTTP Server domain, which is created when you install Oracle HTTP Server on the local disk of each Web tier host. |
/u02/oracle/config/domains/domain_name
|
|
OHS_CONFIG_DIR |
This is the location where you edit the Oracle HTTP Server configuration files (for example, Note this directory is also referred to as the OHS Staging Directory. Changes made here are later propagated to the OHS Runtime Directory. For more information, see “Staging and Run-time Configuration Directories” in the Administrator's Guide for Oracle HTTP Server. |
/u02/oracle/config/domains
/domain_name/config/fmwconfig
/components/OHS
/instance_name
|
7.5 About Creating and Mounting the Directories for an Enterprise Deployment
This section lists the best practices to be followed when creating or mounting the top-level directories in an enterprise deployment.
When creating or mounting the top-level directories, note the following best practices:
-
For the application tier, install the Oracle home (which contains the software binaries) on a second shared storage volume or second partition that is mounted to BIHOST2. Be sure the directory path to the binaries on BIHOST2 is identical to the directory path on BIHOST1.
For example:
/u01/oracle/products/fmw/
For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
-
This enterprise deployment guide assumes that the Oracle Web tier software will be installed on a local disk.
The Web tier installation is typically performed on local storage to the WEBHOST nodes. When using shared storage, you can install the Oracle Web tier binaries (and create the Oracle HTTP Server instances) on shared disk. However, if you do so, then the shared disk must be separate from the shared disk used for the application tier, and you must consider the appropriate security restrictions for access to the storage device across tiers.
As with the application tier servers (BIHOST1 and BIHOST2), use the same directory path on both computers.
For example:
/u02/oracle/products/fmw/
7.6 Summary of the Shared Storage Volumes in an Enterprise Deployment
This section provides a summary of the shared storage volumes required for an enterprise deployment.
The following table summarizes the shared volumes and their purpose in a typical Oracle Fusion Middleware enterprise deployment.
For more information, see Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
| Volume in Shared Storage | Mounted to Host | Mount Directories | Description and Purpose |
|---|---|---|---|
|
NFS Volume 1 |
BIHOST1 |
|
Local storage for the product binaries to be used by BIHOST1; this is where the Oracle home directory and product directories are installed. |
|
NFS Volume 2 |
BIHOST2 |
|
Local storage for the product binaries to be used by BIHOST2; this is where the Oracle home directory and product directories are installed. |
|
NFS Volume 3 |
BIHOST1 BIHOST2 |
|
Administration Server domain configuration, mounted to all hosts; used initially by BIHOST1, but can be failed over to any host. |
|
NFS Volume 4 |
BIHOST1 BIHOST2 |
|
The runtime artifacts directory, mounted to all hosts, contains runtime artifacts such as JMS logs, blogs, and any cluster-dependent shared files needed. |
|
NFS Volume 5 |
BIHOST1 |
|
Local storage for the Managed Server domain directory to be used by BIHOST1, if the private Managed Server domain directory resides on shared storage. |
|
NFS Volume 6 |
BIHOST2 |
|
Local storage for the Managed Server domain directory to be used by BIHOST2, if the private Managed Server domain directory resides on shared storage. |
|
NFS Volume 7 |
WEBHOST1 |
|
Local storage for the Oracle HTTP Server software binaries (Oracle home) and domain configuration files used by WEBHOST1, if the private Managed Server domain directory resides on shared storage. |
|
NFS Volume 8 |
WEBHOST2 |
|
Local storage for the Oracle HTTP Server software binaries (Oracle home) and domain configuration files used by WEBHOST2, if the private Managed Server domain directory resides on shared storage. |