Directory Structure Terminology and Environment Variables

2-10 Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management

2.3 WebLogic Domain Considerations

A domain is the basic administration unit for WebLogic Server instances. A domain consists of one or more WebLogic Server instances and their associated resources that you manage with a single Administration Server. You can define multiple domains based on different system administrators responsibilities, application boundaries, or geographical locations of servers. Conversely, you can use a single domain to centralize all WebLogic Server administration activities. In the context of Identity Management, it is recommended that you deploy the Identity Management components, plus SOA, in a separate WebLogic Server domain from the one where SOA, WebCenter and other customer applications might be deployed. In a typical enterprise deployment, the administration of identity management components such as LDAP directory, single sign-on solutions, and provisioning solutions is done by a different set of administrators from those who administer the middleware infrastructure and applications. It is technically possible to deploy everything in a single domain in a development or test environment. However, in a production environment, the recommendation to use separate domains creates a logical administrative boundary between the identity management stack and the rest of the middleware and application deployment.

2.4 Shared Storage and Recommended Directory Structure

This section details the directories and directory structure that Oracle recommends for an EDG topology. Other directory layouts are possible and supported, but the model adopted in this guide is chosen 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. This section contains the following topics: ■ Section 2.4.1, Directory Structure Terminology and Environment Variables ■ Section 2.4.2, Recommended Locations for the Different Directories

2.4.1 Directory Structure Terminology and Environment Variables

This section describes directory structure terminology and environment variables. Load balancer to Oracle HTTP Server NA 7777 HTTP NA NA Session replication within a WebLogic Server cluster NA NA NA NA By default, this communication uses the same port as the servers listen address. Node Manager NA 5556 TCPIP NA NA Note: Additional ports might need to be opened across the firewalls to enable applications in external domains, such as SOA or WebCenter domains, to authenticate against this Identity Management domain. Table 2–2 Cont. Ports Used in the Oracle Identity Management Enterprise Deployment topologies Type Firewall Port and Port Range Protocol Application Inbound Outbound Timeout Prerequisites for Enterprise Deployments 2-11 ■ ORACLE_BASE : This environment variable and related directory path refers to the base directory under which Oracle products are installed. For example: u01apporacle ■ MW_HOME : This environment variable and related directory path refers to the location where Oracle Fusion Middleware resides. A MW_HOME has a WL_HOME, an ORACLE_COMMON_HOME and one or more ORACLE_HOMEs. An example of a typical MW_HOME is ORACLE_BASEproductfmw ■ WL_HOME : This environment variable and related directory path contains installed files necessary to host a WebLogic Server, for example MW_HOMEwlserver_ 10.3. ■ ORACLE_HOME : This environment variable points to the location where an Oracle Fusion Middleware product, such as Oracle HTTP Server, Oracle SOA Suite, or Oracle Internet Directory is installed and the binaries of that product are being used in a current procedure. For example: MW_HOMEiam ■ ORACLE_COMMON_HOME : This environment variable and related directory path refer to the location where the Oracle Fusion Middleware Common Java Required Files JRF Libraries and Oracle Fusion Middleware Enterprise Manager Libraries are installed. An example is: MW_HOMEoracle_common ■ Domain directory: This path refers to the file system location where the Oracle WebLogic domain information configuration artifacts is stored. Different WebLogic Servers can use different domain directories even when in the same node as described Section 2.4.2, Recommended Locations for the Different Directories.