You must check the system requirements, decide which mode of Oracle Unified Directory to set up, set the environment variables, and specify the installation directories before installing Oracle Unified Directory.
1.1 Checking the System Requirements for Oracle Unified Directory
Before you install Oracle Unified Directory or any related products, check the certification matrix and system requirements to ensure that your environment meets the minimum requirements for the products you are installing.
The following documents are available on the Oracle Technology Network (OTN):
The certification matrix contains information about supported installation types, platforms, operating systems, databases, JDKs, and third-party products.
The process of patching an Oracle Fusion Middleware Identity and Access Management 11g (126.96.36.199.0) deployment starts with the Selection of Patching Method in Patching Guide for Oracle Identity and Access Management.
This topic includes the following sections:
1.1.1 Viewing the Oracle Unified Directory Certification Matrix
Oracle Fusion Middleware provides the system requirements and supported platforms for its components to view the certification matrix.
To view the certification matrix:
- Access the Oracle Fusion Middleware Supported System Configurations page.
- Scroll down to System Requirements and Supported Platforms for Oracle Identity and Access Management 12c (188.8.131.52.0).
- Click the
xlslink to view the certification matrix.
1.1.2 Pre-Installation System Notes
Consider these requirements before installing Oracle Unified Directory.
On Windows systems you must have administrator privileges to install the Oracle Unified Directory software.
Before running the installer, set the
DISPLAYenvironment variable on your system.
On UNIX and Linux systems, installation as the root user is not supported.
The Oracle Unified Directory software treats global, full local, and sparse zones as an independent physical system. Installing Oracle Unified Directory in any type of Solaris zone is therefore like installing on an independent system. Oracle Unified Directory does not share services or file locations with other zones.
1.1.3 Oracle Identity and Access Management Health Checker
The Health Checker is a tool that you can run to test various configurations in an Oracle Identity and Access Management environment. You can run the Health Checker at the post-configuration stage of an Oracle Unified Directory deployment.
The Health Checker retrieves data from your environment and compares this data with the Oracle recommended values for the various configuration settings. The Health Checker then generates a report that provides detailed information about each of the items that it checked.
For more information on how to run the Health Checker, see Understanding the Oracle Identity and Access Environment Health Check Utility in Verifying Your Oracle Identity and Access Management Environment.
This guide also provides manual checklists for deploying Oracle identity and Access Management components in production, including a checklist for Oracle Unified Directory.
1.2 Selecting an Oracle Unified Directory Server Role
You can use Oracle Unified Directory in several roles based on your requirements. You can set up Oracle Unified Directory as a directory server, proxy server, or replication gateway.
Oracle Unified Directory can function in the following three modes or roles:
As a general rule, the use of the generic term server can apply to the directory server, proxy server, or replication gateway.
1.2.1 About Oracle Unified Directory as a Directory Server
When you set up Oracle Unified Directory as a directory server, the server acts as an LDAP directory server that contains directory data.
1.2.2 About Oracle Unified Directory as a Proxy Server
When you set up Oracle Unified Directory as an LDAP proxy server, the server acts as an interface between the client and a remote LDAP server containing the data. The proxy server manages the client requests through load balancing, data distribution, or both.
The proxy does not contain any data. The proxy can also manipulate the data sent by the client or received from the remote LDAP servers (for example, DN renaming, RDN changing, transformation, or Enterprise User Security).
When you use the Oracle Unified Directory proxy, your data is stored in one or more remote LDAP servers or data centers, which can be any LDAPv3-compliant directory server such as Oracle Unified Directory directory server or Oracle Directory Server Enterprise Edition.
1.2.3 About Oracle Unified Directory as a Replication Gateway
When you set up Oracle Unified Directory as a replication gateway, the server acts as a gateway that enables replication between Oracle Directory Server Enterprise Edition and Oracle Unified Directory.
1.3 Understanding the Oracle Unified Directory Installation Directories
During the software installation, you are asked to specify several installation directories. It is helpful to have an understanding of those directories and what they contain when installation is complete.
These directories are created:
1.3.1 Oracle Middleware Home Location
Oracle Middleware home is the directory under which Oracle Unified Directory and Oracle Fusion Middleware Infrastructure are installed. Oracle Fusion Middleware Infrastructure must be installed if you plan to manage Oracle Unified Directory using Oracle Unified Directory Services Manager.
If you are planning to install Oracle Unified Directory and Fusion Middleware Infrastructure, you must install these two components using the same Middleware home directory.
1.3.2 Oracle Home Directory
An Oracle home contains installed files necessary to host a specific product. The Installer installs the files required to host the component, such as binaries and libraries, in the Oracle home directory.
It contains the Oracle Unified Directory setup files to set up individual instances. Also contains the default schema files for all server instances associated with that
An Oracle home resides within the directory structure of the Middleware home. Each Oracle home can be associated with multiple Oracle instances or Oracle WebLogic Server domains.
OUD_ORACLE_HOME directory is
1.3.3 Oracle Common Directory
The installer creates this directory under the location you enter in the Oracle Middleware Home Location field. This directory contains the Application Development Framework.
The default directory is
1.3.4 Oracle WebLogic Domain Directory
A WebLogic domain includes a special WebLogic Server instance called the Administration Server, which is the central point from which you configure and manage all resources in the domain.
Usually, you configure a domain to include additional WebLogic Server instances called Managed Servers. You deploy Java components, such as Web applications, EJBs, and Web services, and other resources to the Managed Servers and use the Administration Server for configuration and management purposes only.
The directory structure of a domain is separate from the directory structure of the WebLogic Server home. It can reside anywhere; it need not be within the Middleware home directory. A domain is a peer of an Oracle instance.
By default, the Oracle Fusion Middleware Configuration Wizard creates a domain as subdirectory in a directory named
user_projects under your Middleware Home directory (
1.3.5 Oracle Unified Directory Installation Directory Structure
Review this topic for the directory structure of an Oracle Unified Directory installation on a single host using all of the default values.
In this example,
install-directory can be any directory on your system. This directory is empty before you install Oracle Unified Directory.
If you are planning to manage Oracle Unified Directory with Oracle Unified Directory Services Manager, you must also install Oracle WebLogic Server and Oracle ADF. You must specify the same Middleware home directory to install all three products.