2 Installing the Oracle Unified Directory Software

Oracle Unified Directory primarily supports two domain configurations. You can install Oracle Unified Directory either as a collocated configuration that is managed through a WebLogic server or as a standalone configuration.

Topics:

2.1 Before You Install Oracle Unified Directory

You can manage Oracle Unified Directory either from the command line or by using the Oracle Unified Directory Services Manager (OUDSM) graphical user interface.

Oracle Unified Directory Services Manager (OUDSM) requires Oracle WebLogic Server and Oracle ADF, so if you plan to use OUDSM, you must install Oracle Unified Directory in a Collocated Oracle Unified Directory Server (Managed through WebLogic server) mode. When you configure Oracle Unified Directory in a WebLogic Server domain, the Oracle Unified Directory instances can be managed like any other elements of the WebLogic Server domain. To configure Oracle Unified Directory in a WebLogic Server domain, you must install the Oracle Unified Directory software in an existing Oracle Fusion Middleware Infrastructure Oracle home.

You can also install Oracle Unified Directory in a Standalone Oracle Unified Directory Server (Managed independently of WebLogic server) mode. A standalone Oracle Unified Directory is not managed by or registered to a WebLogic Server domain. A standalone Oracle Unified Directory 12c (12.2.1.4.0) topology is installed and configured without the Oracle Fusion Middleware Infrastructure. You install the Oracle Unified Directory software in its own Oracle home and you configure the Oracle Unified Directory instance in its own standalone domain. You can use OUDSM installed in a different location or host to manage Oracle Unified Directory that is installed in a standalone mode.

Note:

The product templates for OUD and OUDSM are not interrelated; they are independent of each other. Hence, you can configure OUD and OUDSM independently in separate domains. So, it is possible to have OUD in collocated mode without OUDSM and also you can configure OUDSM alone in a domain without OUD.

You can upgrade Oracle Unified Directory from Oracle Unified Directory Release 12c (12.2.1.3.0) to 12c (12.2.1.4.0). See Updating the Oracle Unified Directory Software.

The installation process requires that you identify certain directories into which the software is installed. For a complete understanding of the installation directory structure, see Understanding the Oracle Unified Directory Installation Directories.

2.2 Installing the Java Development Kit

The installation of Oracle Unified Directory 12c (12.2.1.4.0) requires Java Development Kit (JDK) 1.8.

The archive binary file (.tar.gz) can be installed by anyone (not only root users), in any location that you can write to. However, only the root user can install the JDK into the system location.

For the system requirements and instructions to install JDK, see JDK Installation for Linux Platforms and JDK Installation for Microsoft Windows.

2.3 Setting the JAVA_HOME Environment Variable

After installing the Java Development Kit (JDK), you must set the JAVA_HOME environment variable to point to the Java installation directory.

The setup scripts will not work if the JAVA_HOME environment variable is not set or does not point to a supported Java installation (JDK 8).

For example, on UNIX or Linux systems, run a command similar to the following, depending on your shell:

JAVA_HOME=/usr/lang/JAVA/jdk1.8.0_191
export JAVA_HOME

To set the JAVA_HOME environment variable on Windows systems:

  1. Go to Control Panel > System and Security > System > Advanced System Settings.
  2. Click the Environment Variables button.
  3. In the section System Variables, find the JAVA_HOME environment variable and select it. Click Edit. If the JAVA_HOME environment variable does not exist, click New.
  4. Do one of the following:
    • In the Edit System Variable window, enter path to a supported JDK installation as a Variable value:.

    • In the New System Variable window, enter JAVA_HOME as a Variable name: and enter the path to a supported JDK installation as a Variable value:.

  5. Click OK to apply the changes.

2.4 Setting the PATH Environment Variable

After installing the Java Development Kit, you must set the PATH environment variable to point to the Java installation directory.

For example, on UNIX or Linux systems, run a command similar to the following, depending on your shell:

JAVA_HOME=/usr/lang/JAVA/jdk1.8.0_191
export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH
export PATH

For more information on how to set the PATH environment variable on Windows systems, see How do I set or change the PATH system variable?.

2.5 Obtaining Product Distributions

Oracle provides multiple locations for downloading Oracle Unified Directory and the software it requires.

Note:

  • If you are planning to manage Oracle Unified Directory using Oracle Unified Directory Services Manager, you must first install the Oracle Fusion Middleware Infrastructure.

  • When you install Oracle Unified Directory and Oracle Fusion Middleware Infrastructure, you must specify the same Oracle Home directory. The examples in this chapter use path-to-oracle-home/ORACLE_HOME to represent the Oracle Home directory.

2.5.1 Downloading the Oracle Fusion Middleware Infrastructure Distribution

If you are planning to configure and manage Oracle Unified Directory with OUDSM, you must also install Oracle WebLogic Server and Oracle Application Development Framework. The Oracle Fusion Middleware Infrastructure includes several products and feature sets including Oracle WebLogic Server and Oracle ADF.

To download the Oracle Fusion Middleware Infrastructure distribution:

  1. Download the Oracle Fusion Middleware Infrastructure distribution from the Oracle ADF download page. In the Oracle ADF Downloads section, select 12.2.1.4 from the Application Development Runtime field. Click Download File.
  2. When your browser asks to download the .zip file, save this file onto your system.
  3. Extract the .zip file contents onto your system. The extracted file fmw_12.2.1.4.0_infrastructure_generic.jar runs the product installer and installs the software onto your system.

2.5.2 Downloading the Oracle Unified Directory Distribution from OSDC

Go to the Oracle Software Delivery Cloud (OSDC), to download the Oracle Unified Directory software.

To download Oracle Unified Directory from OSDC:

  1. Download the production distribution for Oracle Unified Directory from the Oracle Software Delivery Cloud.
  2. If prompted, login with a username and password.
  3. Enter Oracle Unified Directory in the type-ahead input field and click Search.
  4. Select Oracle Unified Directory 12.2.1.4.0 from the list of available platforms.
    After you have made your selection, the software title will immediately be placed into your Selected Software cart where you can assign a platform for each individual Release.
  5. Click your Selected Software cart.
  6. Select the Platform for installing Oracle Unified Directory 12.2.1.4.0 and click Continue.
  7. Complete the Terms & Restrictions and Export License Agreement as instructed on the site and click Continue.
  8. Click on the file name to download. Each file has a unique part number.
  9. Browse to the directory where you want to save the file. Click Save to start the file download. A compressed ZIP file is downloaded.
  10. Extract the contents of the ZIP file to a directory of your choice.

2.5.3 Downloading the Oracle Unified Directory Distribution from OTN

Go to the Oracle Technology Network (OTN), to download the Oracle Unified Directory software.

To download Oracle Unified Directory from OTN:

  1. Download the production distribution for Oracle Unified Directory from the Oracle Identity Management download page.
  2. Click the download page here link under the heading Oracle Identity Management 12c.
  3. Accept the OTN License Agreement.
  4. Click the .zip file name to download the file individually and save to the directory where you want to save the file.

    Each .zip file has a unique part number.

  5. Extract the contents of the .zip file onto your system.

2.6 Installing and Configuring OUD/OUDSM Domains

You can either install and configure both OUD and OUDSM in a single domain or OUD and OUDSM independently in separate domains.

Topics:

2.6.1 Installing the OUD/OUDSM Software

You can install OUD and OUDSM independently in separate domains or both in a single domain. This section describes how to install OUD and OUDSM.

2.6.1.1 Installing Oracle Fusion Middleware Infrastructure

The installation of Oracle Fusion Middleware Infrastructure is a prerequisite if you are planning to configure and manage Oracle Unified Directory with Oracle Unified Directory Services Manager. Since OUDSM requires Oracle WebLogic Server and Oracle ADF, the installation of Oracle Fusion Middleware Infrastructure takes care of the installation of WebLogic Server, ADF, and other infrastructure components.

If you are planning to configure and manage Oracle Unified Directory with Oracle Unified Directory Services Manager, you must install Oracle Unified Directory in a Collocated Oracle Unified Directory Server (Managed through WebLogic server) mode.

To install Oracle Fusion Middleware Infrastructure:

  1. Set up the JAVA_HOME and PATH environment variables pointing to the JDK8 install location.
  2. Install Oracle Fusion Middleware Infrastructure.

    See Installing the Infrastructure Software in Installing and Configuring the Oracle Fusion Middleware Infrastructure.

2.6.1.2 Installing Oracle Unified Directory

You can install Oracle Unified Directory in two ways depending on how you want to manage it. If you plan to manage OUD through WebLogic server or OUDSM, you must install OUD in collocated mode or a single domain. However, if you plan to manage OUD independently of WebLogic server, you must choose the standalone mode or separate domains.

To install Oracle Unified Directory:

  1. Set up the JAVA_HOME and PATH environment variables pointing to the JDK8 install location.
  2. Launch the installation program by invoking the java executable from the JDK directory on your system.

    On UNIX operating systems:

    $ $JAVA_HOME/bin/java -jar fmw_12.2.1.4.0_oud.jar

    On Windows operating systems:

    C:\Program Files\Java\jdk1.8.0_191\bin\java -jar fmw_12.2.1.4.0_oud.jar

    Note:

    You must run the command prompt with Windows Administrator privileges. Open the command prompt and specify Run as administrator. When you open this window, the title bar reads Administrator: Command Prompt.

    The Installation Inventory Setup screen opens.

  3. Use the Installation Inventory Setup screen to specify the location of the Oracle central inventory directory. Click OK.
    The Oracle Unified Directory 12c Installer Welcome screen opens.
  4. Review the information on the Welcome screen that introduces you to the product installer. Click Next.
  5. Use the Auto Updates screen to search for the latest software updates, including important security updates, through your My Oracle Support account.
    • Keep the default setting Skip Auto Updates if you do not want your system to check for software updates.
    • Select patches from directory: Select this option if you already downloaded the latest software updates and you want the installer to search a local directory for updates applicable to the products you are about to install. When you select this option, the installer displays an extra field that you can use to identify the local directory where your updates are located.
    • Search My Oracle Support for Updates: If you have a My Oracle Support account, then select this option to have the installer automatically search My Oracle Support for software updates that apply to the software products you are about to install.

    Click Next.

  6. Use the Installation Location screen to specify your Oracle home directory location and to view the products installed in that directory. Click Next.
  7. Use the Installation Type screen to determine the type of installation you want to perform and consequently, which products and features are installed.
    • If you plan to manage OUD through Oracle WebLogic Server or OUDSM, select Collocated Oracle Unified Directory Server (Managed through WebLogic server).

    • If you plan to manage OUD independently of Oracle WebLogic Server, select Standalone Oracle Unified Directory Server (Managed independently of WebLogic server).

    Click Next.

  8. Verify that your system meets minimum requirements on the Prerequisite Checks screen. Click Next.
  9. The Installation Summary screen contains a list of the feature sets you selected for installation, along with the approximate amount of disk space to be used by the feature sets once installation is complete. Click Install.
  10. The Installation Progress screen shows the progress of the installation. When the progress bar reaches 100%, the installation is complete. Click Next.
  11. This screen appears at the conclusion of the installation and provides a summary of the products and features that were installed. Click Finish to dismiss the installer.

2.6.2 Configuring OUD and OUDSM in Separate Domains

After the product installation is complete, you can start the process of domain creation. You can configure OUD and OUDSM in separate domains.

Note:

This is the Oracle preferred approach to set up domains for OUD and OUDSM. If you follow this approach, you can create a domain for OUDSM without depending on Oracle database.

2.6.2.1 Configuring a Domain for OUD Using the Configuration Wizard

You can configure a domain for OUD either by creating a new domain or by extending an existing domain using the Fusion Middleware Configuration Wizard.

To either create a new domain or update an existing domain for OUD:

  1. Start the Configuration Wizard from the ORACLE_HOME/oracle_common/common/bin directory.

    On UNIX operating systems:

    ./config.sh

    On Windows operating systems:

    config.cmd

    The Configuration Type screen is displayed.

  2. On the Configuration Type screen, perform the following steps:
    1. You can either create a new domain or extend an existing domain.

      • Select Create a new domain to create a new domain.

      • Select Update an existing domain to extend an existing domain.

    2. Enter the full path for the domain or use the Browse button to navigate to the directory in which your domains are located.

    3. Click Next.

  3. On the Templates screen, make sure Create Domain Using Product Templates is selected, and then select the Oracle Unified Directory - 12.2.1.3.0 [oud] template. Click Next.
    1. Ensure your selection is correct based on the configuration selected in Step 2.

      • If you select Create a new domain, ensure Create Domain Using Product Templates is selected.

      • If you select Update an existing domain, ensure that Update Domain Using Product Templates is selected.

    2. Select the Oracle Unified Directory - 12.2.1.3.0 [oud] template.

    3. Click Next.

    Note:

    The version of Oracle Unified Directory template is unchanged, hence the template version remains the same as in 12c.

  4. On the JDK Selection screen, accept Oracle Hotspot as a default selection and click Next.
  5. On the System Components screen, ignore this screen and click Next.

    Note:

    This screen provides an option to add a component. However, this functionality to add a component or an instance is not available in this release. This option will be supported in future releases.

  6. Use the Node Manager screen to enter the node manager username and password.
    Click Next.
  7. Review each item on the Configuration Summary screen and verify that the information is correct.
    To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation or domain extension does not start until you click Create or Update.
  8. The Configuration Success screen shows information about the domain you just configured.
    Click Finish to dismiss the Configuration Wizard.
2.6.2.2 Creating a Domain for OUDSM Using the WebLogic Scripting Tool

You can create a domain for OUDSM without depending on the Oracle Database or the Repository Creation Utility (RCU) using the WLST command.

Note:

This is the Oracle preferred approach to set up a domain for OUDSM. It is recommended not to extend this domain with any other products or components. In this approach, you do not have to run config.sh.

To set up the OUDSM domain using the WLST:

  1. Launch the WLST:

    On UNIX and Linux systems:

    $ ORACLE_HOME/oracle_common/common/bin/wlst.sh

    On Windows systems:

    C:\> ORACLE_HOME\oracle_common\common\bin\wlst.cmd

    ORACLE_HOME is the Oracle home directory you specified at installation.

  2. Execute the createOUDSMDomain command to create a compact domain for Oracle Unified Directory Services Manager.

    The createOUDSMDomain command includes the following parameters:

    • domainLocation is the absolute location of the domain with domain name.

    • weblogicPort is the WebLogic port.

    • weblogicSSLPort is the WebLogic SSL port. This parameter is optional and not enabled if not passed.

    • weblogicUserName is the WebLogic user name. This parameter is optional and if not passed default value is weblogic.

    • weblogicUserPassword is the WebLogic admin user password.

    createOUDSMDomain(domainLocation=<location>,weblogicPort=<value>,
    weblogicSSLPort=<value>,weblogicUserName=<name>,weblogicUserPassword=<password>

    Example:

    createOUDSMDomain(domainLocation="/u01/oracle/config/domains/oudsm",weblogicPort=7001,weblogicSSLPort=7002,weblogicUserPassword='password')

2.6.3 Configuring OUD and OUDSM in a Single Domain

You can configure OUD and OUDSM in a single WebLogic domain if you have selected Collocated Oracle Unified Directory Server (Managed through WebLogic server) as the installation type.

You can also configure the WebLogic domain for OUDSM using the Fusion Middleware Configuration Wizard. Since the configuration wizard only supports Oracle Platform Security Services (OPSS) DB store, therefore, OUDSM relies on a DB-based OPSS security store for storing the administrator configurations securely.

Before running config.sh to set up OUDSM, you must first install and configure a certified database. To use a database repository for the OPSS security store, you must use the Repository Creation Utility (RCU) to create the required schema and to seed some initial data.

2.6.3.1 Creating Database Schemas for the Infrastructure Domain Using the Repository Creation Utility

After Oracle Fusion Middleware Infrastructure is installed, start Repository Creation Utility (RCU) from the ORACLE_HOME/oracle_common/bin directory. The Repository Creation Utility enables you to create database schemas that are required for Oracle Fusion Middleware products.

Note:

This database schema creation procedure is required only if you are planning to install the Oracle Unified Directory Services Manager (OUDSM) by selecting the OUDSM template.

To create schemas using the Repository Creation Utility:

  1. Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.

    See About Database Requirements for an Oracle Fusion Middleware Installation in Planning an Installation of Oracle Fusion Middleware.

  2. Start the Repository Creation Utility (RCU) from the ORACLE_HOME/oracle_common/bin directory.

    On UNIX operating systems:

    ./rcu

    On Windows operating systems:

    rcu.bat
  3. Click Next on the Welcome to Repository Creation Utility screen.
  4. On the Create Repository screen, select System Load and Product Load as the schema creation method and click Next.
  5. On the Database Connection Details screen, enter database connection details for RCU to connect to your database.
    1. Click Next when you are finished entering the connection credentials for your database.
      A dialog box appears indicating the progress of the installer establishing the connection with the specified database.
    2. Click OK to dismiss this dialog box.
  6. On the Select Components screen, enter a custom prefix you want to use for your schemas, and then select the Oracle Platform Security Services schema.

    Note:

    If you select Oracle Platform Security Services, all dependent components will be automatically selected.

    1. Click Next when you are finished specifying your prefix and schema names and when you are finished selecting components.
      A dialog box appears, indicating the progress of component prerequisite checking before the schemas are created.
    2. Click OK to dismiss this dialog box.
  7. On the Schema Passwords screen, specify how you want to set the schema passwords on your database, then enter and confirm your passwords. Click Next.
  8. Use the Map Tablespaces screen to configure the desired tablespace mapping for the schemas you want to create.
    1. Click Next when you are finished with your tablespace information.
      A dialog box appears, asking you to confirm the creation of tablespaces for any new schemas.
    2. Click OK to continue. A dialog box appears, indicating the progress of the tablespace creation.
    3. When the tablespaces are created, click OK to dismiss this window.
  9. On the Summary screen, verify your information, and then click Create to begin schema creation.
  10. Review the information on the Completion Summary screen, and then click Close to dismiss this screen.
    The Completion Summary screen contains information about the log files that were created from this RCU operation. You can click the name of a particular log file to view the contents of that file.
2.6.3.2 Configuring OUD/OUDSM Domain Using the Configuration Wizard

You can configure a domain for OUD/OUDSM either by creating a new domain or by extending an existing domain using the Fusion Middleware Configuration Wizard.

Note:

If you are updating an existing domain to add OUD (for example, adding OUD to a DIP Domain), then the Configuration Wizard screens documented at steps 4 and 5 are not actually displayed and it skips straight to the Database Configuration Type page (step 6).

To create a new domain or extend an existing domain for OUD/OUDSM:

  1. Start the Configuration Wizard from the ORACLE_HOME/oracle_common/common/bin directory.

    On UNIX operating systems:

    ./config.sh

    On Windows operating systems:

    config.cmd

    The Configuration Type screen is displayed.

  2. On the Configuration Type screen, perform the following steps:
    1. You can either create a new domain or extend an existing domain.

      • Select Create a new domain to create a new domain.

      • Select Update an existing domain to extend an existing domain.

    2. Enter the full path for the domain or use the Browse button to navigate to the directory in which your domains are located.

    3. Click Next.

  3. On the Templates screen, make sure Create Domain Using Product Templates is selected, and then select the following templates:
    1. Ensure your selection is correct based on the configuration selected in Step 2.

      • If you select Create a new domain, ensure that Create Domain Using Product Templates is selected.

      • If you select Update an existing domain, ensure that Update Domain Using Product Templates is selected.

    2. Select the following templates:

      • Oracle Unified Directory - 12.2.1.3.0 [oud]

      • Oracle Unified Directory Services Manager - 12.2.1.3.0 [oud]

        When you select OUDSM, Oracle JRF - 12.2.1.3.0 [oracle_common] is automatically selected.

    3. Click Next.

    Note:

    There is no change in the versions of Oracle Unified Directory, Oracle Unified Directory Services Manager, and Oracle JRF templates, hence the template versions remains the same as in 12c.
  4. Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.
    The password must be at least eight characters and must contain at least one number or special character. Confirm the password and click Next.
    Make a note of these details as you will need them to start or restart the WebLogic domain in the following procedure.
  5. Use the Domain Mode and JDK screen to specify the domain mode and Java Development Kit (JDK).
    1. Select Production in the Domain Mode field.

      Note:

      If you select Production mode as the domain, the node manager has a random username and password assigned to it. Use the WebLogic Server Administration Console to reset the password.

    2. Accept Oracle Hotspot as a default JDK location.
    3. Click Next.
  6. On the Database Configuration type screen, select RCU Data. This option instructs the Configuration Wizard to connect to the database’s Service Table (STB) schema to automatically retrieve schema information for schemas needed to configure the domain.
    After selecting RCU Data:
    1. Enter the name of the server hosting the database in the Host Name field.
    2. Enter the database DBMS name, or service name if you selected a service type driver in the DBMS/Service field.
    3. Enter the port number on which the database listens.
    4. Enter the username and password for connecting to the database's Service Table schema.
    5. Click Get RCU Configuration to retrieve the schema information.
    6. After successfully retrieving the schema information, click Next to continue.
  7. Verify that the values populated on the JDBC Component Schema screen are correct for all schemas, and click Next.
  8. Use the JDBC Component Schema Test screen to test data source connections that you just configured.
    A green check mark in the Status column indicates a successful test. If you encounter issues, see the error message in the Connection Result Log section of the screen, fix the problem, then test the connection again.
  9. Use the Advanced Configuration screen to complete the domain configuration.
    To complete domain configuration, select any of these options:
    • Administration Server: Required to properly configure the Administration Server’s listen address.
    • Node Manager: Required to configure Node Manager.
    • Topology: Required to configure the Managed Servers and cluster, and for configuring the system and targeting Managed Servers to the system.
    • Domain Frontend Host Capture: Required to configure Domain Frontend Host.
    • Deployments and Services: Required to target to servers or clusters.
    Click Next.
  10. Review each item on the Configuration Summary screen and verify that the information is correct.
    To make any changes, go back to a screen by clicking the Back button or selecting the screen in the navigation pane. Domain creation or domain extension does not start until you click Create or Update.
  11. The Configuration Success screen shows information about the domain you just configured.
    Click Finish to dismiss the Configuration Wizard.

2.7 Starting the Administration Server

After the WebLogic domain configuration is complete, you can start the Administration Server to manage the domain. OUDSM also uses this WebLogic Admin Server, so once the Admin Server is up and running, OUDSM is also effectively running as well.

To start the Administration Server:

  1. Run the script to start the Administration Server from the following location:

    On UNIX operating systems:

    $ domain-home/bin/startWebLogic.sh
    

    On Windows operating systems:

    domain_home\startWebLogic.cmd

    Note:

    • The domain-home for starting the Administration Server depends on how you configure a domain for OUD and OUDSM.

    • If you added OUDSM to the existing DIP Domain by choosing Update an existing domain as the Configuration Type, you must restart the existing Admin Server and Managed Server so that the OUDSM application is deployed and accessible.

  2. Verify that the Administration Server is up and running by accessing the Oracle Unified Directory Services Manager through a browser. Access OUDSM through a browser, using the following URL:
    http://hostname:7001/oudsm
    

    where hostname is the name of the server on which WebLogic Server is installed. 7001 is the default administrative port for the WebLogic Administration Server.

    Note:

    Ensure that the Administration Server is up and running before you access OUDSM. When the server successfully completes its startup process, it displays the following message:

    <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

2.8 Starting the Node Manager

You can use the command line interface to start the node manager.

  1. Navigate to the following directory:
    $ cd $DOMAIN_HOME/bin
  2. Run the script to start the node manager:
    ./startNodeManager.sh

2.9 Performing an Oracle Unified Directory Silent Installation

Silent installation eliminates the need to monitor your product installation because no graphical output is displayed and no input by the user is required.

To perform an Oracle Unified Directory silent installation:

  1. Create a response file (install.rsp) in the directory of your choice using a text editor such as vi or emacs. Response file provides information specific to the installation of Oracle Unified Directory.
    [ENGINE]
     
    #DO NOT CHANGE THIS.
    Response File Version=1.0.0.0.0
     
    [GENERIC]
     
    #The oracle home location. This can be an existing Oracle Home or a new Oracle Home
    ORACLE_HOME=/u01/oracle/products/oud
     
    #Set this variable value to the Installation Type selected. Possible values: Standalone Oracle Unified Directory Server (Managed independently of WebLogic server), Collocated Oracle Unified Directory Server (Managed through WebLogic server).
    INSTALL_TYPE=Standalone Oracle Unified Directory Server (Managed independently of WebLogic server)
     
    #Provide the My Oracle Support Username. If you want to ignore Oracle Configuration Manager configuration provide empty string for user name.
    MYORACLESUPPORT_USERNAME=
     
    #Provide the My Oracle Support Password
    MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
    
    #Set this to true if you want to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
    DECLINE_SECURITY_UPDATES=true
     
    #Set this to true if My Oracle Support Password is specified
    SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
     
    #Provide the Proxy Host
    PROXY_HOST=
     
    #Provide the Proxy Port
    PROXY_PORT=
     
    #Provide the Proxy Username
    PROXY_USER=
     
    #Provide the Proxy Password
    PROXY_PWD=<SECURE VALUE>
    
    #Type String (URL format) Indicates the OCM Repeater URL which should be of the format [scheme[Http/Https]]://[repeater host]:[repeater port]
    COLLECTOR_SUPPORTHUB_URL=
    
  2. Create the oraInst.loc file in the directory of your choice using a text editor such as vi or emacs. The contents of the file consist of the following two lines:
    inventory_loc=oui_inventory_directory
    inst_group=oui_install_group

    Replace oui_inventory_directory with the full path to the directory where you want the installer to create the inventory directory. Then, replace oui_install_group with the name of the group whose members have write permissions to this directory.

    For example,

    inventory_loc=/home/exampleuser/oraInst.loc
    inst_group=dba

    The Oracle inventory directory keeps track of all Oracle products installed on the computer. The inventory directory is stored in a file called oraInst.loc.

  3. Run the following command to perform the silent installation:
    java –jar distribution_name.jar –silent –responseFile file –invPtrLoc file
    

    For example, to install the Oracle Unified Directory, run the following command:

    /u01/oracle/jdk/jdk1.8.0_191/bin/java –jar fmw_12.2.1.4.0_oud.jar –silent –responseFile /u01/oracle/response/install.rsp –invPtrLoc /u01/oracle/oraInst.loc
    

2.10 Configuring Oracle Unified Directory with Oracle Directory Integration Platform

Oracle Directory Integration Platform is a Java EE application that enables you to integrate your applications and directories, including third-party LDAP directories, with Oracle Unified Directory.

Oracle Directory Integration Platform includes services and interfaces that allow you to deploy synchronization solutions with other enterprise repositories. It can also be used to provide Oracle Unified Directory interoperability with third party metadirectory solutions.

For example, in an Oracle Fusion Middleware environment, where access to Oracle components relies on data stored in Oracle Unified Directory, you can still use Microsoft Active Directory as the central enterprise directory. Users of that directory can still access Oracle components because Oracle Directory Integration Platform can synchronize the data in Microsoft Active Directory with that in Oracle Unified Directory.

To configure Oracle Unified Directory, Oracle Unified Directory Services Manager, Oracle Directory Integration Platform, and Fusion Middleware Control in an Oracle WebLogic Server domain, see Configuring Oracle Unified Directory in Administrator's Guide for Oracle Directory Integration Platform.