Preparing the File System for an Enterprise Deployment

8 Preparing the File System for an Enterprise Deployment

Preparing the file system for an enterprise deployment involves understanding the requirements for local and shared storage, as well as the terminology that is used to reference important directories and file locations during the installation and configuration of the enterprise topology.

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
It is important to set up your storage in a way that makes the enterprise deployment easy to understand, configure, and manage.
Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment
Oracle recommends that you implement certain guidelines regarding shared storage when you install and configure an enterprise deployment.
About 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
Understanding the file system directories and the directory variables used to reference these directories is essential for installing and configuring the enterprise deployment topology.
About Creating and Mounting the Directories for an Enterprise Deployment
Oracle recommends that you implement certain best practices when you create or mount the top-level directories in an enterprise deployment.
Summary of the Shared Storage Volumes in an Enterprise Deployment
It is important to understand the shared volumes and their purpose in a typical Oracle Fusion Middleware enterprise deployment.

Parent topic: Preparing for an Enterprise Deployment

Overview 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.

This chapter provides an overview of the process of preparing the file system for an enterprise deployment. Oracle recommends setting up your storage according to information in this chapter. The terminology defined in this chapter is used in the diagrams and procedures throughout the guide.

Use this chapter as a reference to understand the directory variables that are 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.

Parent topic: Preparing the File System for an Enterprise Deployment

Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment

Oracle recommends that you implement certain guidelines regarding shared storage when you install and configure 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 8-1 lists the key sections that you should review and how those concepts apply to an enterprise deployment.

Table 8-1 Shared Storage Resources in the High Availability Guide

Section in High Availability Guide	Importance to an Enterprise Deployment
Shared Storage Prerequisites	Describes guidelines for disk format and the requirements for hardware devices that are optimized for shared storage.
Using Shared Storage for Binary (Oracle Home) Directories	Describes your options for storing the Oracle home on a shared storage device that is available to multiple hosts. For an enterprise deployment, Oracle recommends that you use 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.
Using Shared Storage for Domain Configuration Files	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.
Shared Storage Requirements for JMS Stores and JTA Logs	Provides instructions for setting the location of the transaction logs and JMS stores for an enterprise deployment.
Introduction to Zero Downtime Patching	Describes the Zero Downtime feature and the procedure to configure and monitor workflows.

Note:

Zero Downtime Patching (ZDT Patching) provides an automated mechanism to orchestrate the rollout of patches while avoiding downtime or loss of sessions. ZDT reduces risks and downtime of mission-critical applications that require availability and predictability while applying patches.

By using the workflows that you define, you can patch or update any number of nodes in a domain with little or no manual intervention. Changes are rolled out to one node at a time. This preemptively allows for session data to be migrated to compatible servers in the cluster and allows service migration of singleton services, such as JTA and JMS.

When you patch the Oracle home, the current Oracle home must be installed locally on each node that is included in the workflow. Although it is not required, Oracle also recommends that the Oracle home be in the same location on each node.

Parent topic: Preparing the File System for an Enterprise Deployment

About 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 the disk by the Oracle Fusion Middleware installers, domain-specific files generated through the domain configuration process, as well as domain configuration files that are propagated to the various host computers through the Oracle WebLogic Server pack and unpack commands.

The diagrams are used to indicate:

Figure 8-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 8-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 8-4 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 8-1 Recommended Shared Storage Directory Structure for an Enterprise Deployment

Note:

In a deployment which uses more than one domain, it is recommended that different copies of the binaries are used for each domain. For Oracle Identity Management, it is recommended that the following ORACLE_HOMEs be created:
- DIR_ORACLE_HOME for Directory components (/oud)
- IAD_ORACLE_HOME for Access components (/oam)
- IGD_ORACLE_HOME for Identity Governance components (/oig)
Oracle Identity Management uses multiple Domains. The diagram above depicts ASERVER_HOME as a generic location. This guide will often prefix this value with a domain abbreviation for example:
- IAD_ASERVER_HOME for Oracle Access Manager
- IGD_ASERVER_HOME for Oracle identity Governance

*See About the Node Manager Configuration in a Typical Enterprise Deployment.

Figure 8-2 Recommended Local Storage Directory Structure for an Application Tier Host Computer in an Enterprise Deployment

See About the Node Manager Configuration in a Typical Enterprise Deployment.

Figure 8-3 Recommended Local Storage Directory Structure for a Directory Tier Host Computer in an Enterprise Deployment

Note:

oudDomain exists only if OUDSM is used.

Figure 8-4 Recommended Local Storage Directory Structure for a Web Tier Host Computer in an Enterprise Deployment

Parent topic: Preparing the File System for an Enterprise Deployment

File System and Directory Variables Used in This Guide

Understanding the file system directories and the directory variables used to reference these directories is essential for installing and configuring the enterprise deployment topology.

Table 8-2 lists the file system directories and the directory variables that are used to reference the directories on the application tier. Table 8-3 lists the file system directories and variables that are used to reference the directories on the web tier.

For additional information about mounting these directories when you use 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 that use 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 that 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.

See Using the Enterprise Deployment Workbook.

Table 8-2 Sample Values for Key Directory Variables on the Application Tier

Directory Variable	Description	Relative Path	Sample Value on the Application Tier
ORACLE_BASE	The base directory, under which Oracle products are installed.	N/A	`/u01/oracle` - OAM, OIG `/u02/oracle` - OUD, OUDSM, OID
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.	`ORACLE_BASE/products/<product>`	`/u01/oracle/products/oam` `/u01/oracle/products/oig` `/u02/oracle/products/oud` `/u02/oracle/products/oudsm` `/u02/oracle/products/oid`
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.	`ORACLE_HOME/oracle_common`	`/u01/oracle/products/oam/oracle_common` `/u01/oracle/products/oig/oracle_common` `/u02/oracle/products/oud/oracle_common` `/u02/oracle/products/oudsm/oracle_common` `/u02/oracle/products/oid/oracle_common`
WL_HOME	The directory within the Oracle home where the Oracle WebLogic Server software binaries are stored.	`ORACLE_HOME/wlserver`	`/u01/oracle/products/oam/wlserver` `/u01/oracle/products/oig/wlserver`
PROD_DIR	Individual product directories for each Oracle Fusion Middleware product that you install.	`ORACLE_HOME/prod_dir`	`/u01/oracle/products/oam` `/u01/oracle/products/oig` `/u02/oracle/products/oud` `/u02/oracle/products/oudsm` `/u02/oracle/products/oid`
EM_DIR	The product directory used to store the Oracle Enterprise Manager Fusion Middleware Control software binaries.	`ORACLE_HOME/em`	`/u01/oracle/products/oam/em` `/u01/oracle/products/oig/em`
JAVA_HOME	The location where you install the supported Java Development Kit (JDK).	`ORACLE_BASE/products/jdk`	`/u01/oracle/products/jdk` - OAM, OIG `/u02/oracle/products/jdk` - OUD, OUDSM, OID
SHARED_CONFIG_DIR	The shared parent directory for shared environment configuration files, including domain configuration, keystores, runtime artifacts, and application deployments	`ORACLE_BASE/config`	`/u01/oracle/config`
LOCAL_CONFIG_DIR	The local or nfs-mounted configuration directory unique to a given host containing the machine-specific domain directory for the managed servers (`MSERVER_HOME`). Directory variable: `LOCAL_CONFIG_DIR`	`/u02/oracle/config` - OAM, OIG	`/u02/oracle/config`
ASERVER_HOME	The Administration Server domain home, which is installed on a shared disk.	`SHARED_CONFIG_DIR/domains/domain_name`	`/u01/oracle/config/domains/oam` `/u01/oracle/config/domains/oig`
IAD_ASERVER_HOME	The Administration Server domain home for Oracle Access Management, which is installed on a shared disk.	`SHARED_CONFIG_DIR/domains/domain_name`	`/u01/oracle/config/domains/oam`
IGD_ASERVER_HOME	The Administration Server domain home for Oracle Identity Governance, which is installed on a shared disk.	`SHARED_CONFIG_DIR/domains/domain_name`	`/u01/oracle/config/domains/oig`
MSERVER_HOME	The Managed Server domain home, which is created by using the `unpack` command on the local disk of each application tier host.	`LOCAL_CONFIG_DIR/domains/domain_name`	`/u02/oracle/config/domains/oam` `/u02/oracle/config/domains/oig` In this example, replace `domain_name` with the name of the WebLogic Server domain.
IAD_MSERVER_HOME	The Managed Server domain home, for Oracle Access Management which is created by using the `unpack` command on the local disk of each application tier host.	`LOCAL_CONFIG_DIR/domains/domain_name`	`/u02/oracle/config/domains/oam`
IGD_MSERVER_HOME	The Managed Server domain home, for Oracle Identity Governance which is created by using the `unpack` command on the local disk of each application tier host.	`LOCAL_CONFIG_DIR/domains/domain_name`	`/u02/oracle/config/domains/oig`
APPLICATION_HOME	The Application home directory, which is installed on shared disk, so the directory is accessible by all the application tier host computers.	`SHARED_CONFIG_DIR/applications/domain_name`	`/u01/oracle/config/applications/oam` `/u01/oracle/config/applications/oig` In this example, replace `domain_name` with the name of the WebLogic Server domain.
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. See About the Node Manager Configuration in a Typical Enterprise Deployment.	`LOCAL_CONFIG_DIR/node_manager`	`/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.	`SHARED_CONFIG_DIR/dp`	`/u01/oracle/config/dp`
KEYSTORE_HOME	The shared location for custom certificates and keystores.	`SHARED_CONFIG_DIR/keystores`	`/u01/oracle/config/keystores`

Table 8-3 Sample Values for Key Directory Variables on the Web Tier

Directory Variable	Description	Sample Value on the Web Tier
WEB_ORACLE_HOME	The read-only location for the Oracle HTTP Server product binaries. For the web tier host computers, this directory is stored on the local disk. The Oracle home is created when you install the Oracle HTTP Server software .	`/u02/oracle/products/ohs`
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/ohs/oracle_common`
WL_HOME	The directory within the Oracle home where the Oracle WebLogic Server software binaries are stored.	`/u02/oracle/products/ohs/wlserver`
PROD_DIR	Individual product directories for each Oracle Fusion Middleware product that you install.	`/u02/oracle/products/ohs`
JAVA_HOME	The location where you install the supported Java Development Kit (JDK).	`/u02/oracle/products/jdk`
WEB_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/ohsDomain`
WEB_CONFIG_DIR	This is the location where you edit the Oracle HTTP Server configuration files (for example, `httpd.conf` and `moduleconf/*.conf`) on each web host. Note that this directory is also referred to as the OHS Staging Directory. Changes made here are later propagated to the OHS Runtime Directory. See Staging and Run-time Configuration Directories in the Administering Oracle HTTP Server.	`/u02/oracle/config/domains/ohsDomain/config/fmwconfig/components/OHS/instance/instance_name`
WEB_KEYSTORE_HOME	If you use Oracle HTTP Server as your web server, this is the location for custom certificates and keystores.	`/u02/oracle/config/keystores`

Parent topic: Preparing the File System for an Enterprise Deployment

About Creating and Mounting the Directories for an Enterprise Deployment

Oracle recommends that you implement certain best practices when you create or mount the top-level directories in an enterprise deployment.

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 OAMHOST2. Be sure the directory path to the binaries on OAMHOST2 is identical to the directory path on OAMHOST1.

For example:
```
/u01/oracle/products/oam/
```
See Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.
This enterprise deployment guide assumes that the Oracle Web tier software is installed on a local disk.

The Web tier installation is typically performed on local storage to the WEBHOST nodes. When you use shared storage, you can install the Oracle Web tier binaries (and create the Oracle HTTP Server instances) on a 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 (OAMHOST1 and OAMHOST2), use the same directory path on both computers.

For example:
```
/u02/oracle/products/ohs
```

Parent topic: Preparing the File System for an Enterprise Deployment

Summary of the Shared Storage Volumes in an Enterprise Deployment

It is important to understand the shared volumes and their purpose in a typical Oracle Fusion Middleware enterprise deployment.

The following table summarizes the shared volumes and their purpose in a typical Oracle Fusion Middleware enterprise deployment.

See, Shared Storage Recommendations When Installing and Configuring an Enterprise Deployment.

Table 8-4 Shared Storage Volumes in an Enterprise Deployment

Shared Volume Name	Exports	Mounted to Host	Mount Directories	Description and Purpose
oamBinaries1	`/exports/oamBinaries1`	OAMHOST1 OAMHOST3	`/u01/oracle/products/`	Shared storage for the OAM product binaries to be used. This is where the Oracle home directory and product directories are installed.
oamBinaries2	`/exports/oamBinaries2`	OAMHOST2 OAMHOST4	`/u01/oracle/products/`	Shared storage for the OAM product binaries to be used. This is where the Oracle home directory and product directories are installed.
oigBinaries1	`/exports/oigBinaries1`	OIGHOST1 OIGHOST3	`/u01/oracle/products/`	Shared storage for the OIG product binaries to be used. This is where the Oracle home directory and product directories are installed.
oigBinaries2	`/exports/oigBinaries2`	OIGHOST2 OIGHOST4	`/u01/oracle/products/`	Shared storage for the OIG product binaries to be used. This is where the Oracle home directory and product directories are installed.
oamSharedConfig	`/exports/oamSharedConfig`	OAMHOST1 OAMHOST2 (failover) OAMHOST3 (failover) OAMHOST4 (failover)	`/u01/oracle/config`	Administration Server domain configuration, mounted to all OAM hosts; used initially by OAMHOST1 but can be failed over to any host.
oigSharedConfig	`/exports/oigSharedConfig`	OIGHOST1 OIGHOST2 (failover) OIGHOST3 (failover) OIGHOST4 (failover)	`/u01/oracle/config`	Administration Server domain configuration, mounted to all OIG hosts; used initially by OIGHOST1, but can be failed over to any host.
installers	`/exports/installers`	ALL HOSTS	`/installers`	Convenient location used to stage Oracle Software Installers during installation. Can be unmounted following installation. This is optional.

Note:

Directory Binaries can either be created locally or shared. If shared, create a separate volume for the Directory binaries.

If Shared storage is being used for local storage, to make the backups easier or to have the files stored on more fault tolerant hardware, then you must create an NFS volume for each of the hosts in the topology. It should then be mounted to the host in the location ORACLE_BASE.

Parent topic: Preparing the File System for an Enterprise Deployment