4 Performing Common Installation Tasks

This chapter describes tasks that are common to most Oracle Identity Management installations and configurations. It includes the following topics:

4.1 Starting an Installation

This topic explains the steps that are common to starting most Oracle Identity Management installations and configurations. It begins with starting the Installer and ends after you complete the steps on the Prerequisites Check screen.

Note:

Starting the Installer as the root user is not supported.

Perform the following steps to start an Oracle Identity Management installation:

  1. Start the Installer by executing one of the following commands:

    UNIX: ./runInstaller

    Windows: D:\ setup.exe

    After the Installer starts, the Welcome screen appears.

  2. Click Next on the Welcome screen. The Select Installation Type screen appears.

  3. Select Install and Configure and click Next. The Prerequisites Check screen appears.

  4. Monitor the prerequisites checking.

    • If there is an issue, an error or warning message will appear. Investigate the issue and resolve it. After resolving the issue, click Retry to restart the prerequisite checks.

      Note:

      You can proceed with the installation without resolving the issue by clicking Continue. However, failing to resolve the issue during the prerequisites checking may cause additional issues later in the installation.
    • If all prerequisite checks pass inspection, click Next.

    The Select Domain screen appears. Continue by referring to the appropriate procedure in this chapter for the installation you want to perform.

4.2 Identifying Installation Directories

This topic describes directories you must identify in most Oracle Identity Management installations and configurations—it does not describe one particular Installer screen. During installation, you will have to identify other component-specific directories not described in this topic.

The common directories described in this section include the following:

4.2.1 Oracle Middleware Home Location

Identify the location of your Oracle Middleware Home directory. The Installer creates an Oracle Home directory for the component you are installing under the Oracle Middleware Home that you identify in this field. The Oracle Middleware Home directory is commonly referred to as MW_HOME.

4.2.2 Oracle Home Directory

Enter a name for the component's Oracle Home directory. The Installer uses the name you enter in this field to create the Oracle Home directory under the location you enter in the Oracle Middleware Home Location field.

The Installer installs the files required to host the component, such as binaries and libraries, in the Oracle Home directory. The Oracle Home directory is commonly referred to as ORACLE_HOME.

4.2.3 WebLogic Server Directory

Enter the path to your Oracle WebLogic Server Home directory. This directory contains the files required to host the Oracle WebLogic Server. It is commonly referred to as WL_HOME.

4.2.4 Oracle Instance Location

Enter the path to the location where you want to create the Oracle Instance directory. The Installer creates the Oracle Instance directory using the location you enter in this field and using the name you enter in the Oracle Instance Name field.

The Installer installs the component's configuration files and runtime processes in the Oracle Instance directory. Runtime components will write only to this directory. You can identify any location on your system for the Oracle Instance directory—it does not have to reside inside the Oracle Middleware Home directory.

4.2.5 Oracle Instance Name

Enter a name for the Oracle Instance directory. The Installer uses the name you enter in this field to create the Oracle Instance directory at the location you specify in the Oracle Instance Location field. This directory is commonly referred to as ORACLE_INSTANCE.

Instance names are important because Oracle Fusion Middleware uses them to uniquely identify instances. If you install multiple Oracle Fusion Middleware instances on the same computer, for example, an Oracle Identity Management instance and an Oracle WebLogic Server instance, you must give them different names.

The name you enter for the Oracle Instance directory must:

  • Contain only alphanumeric and underscore (_) characters

  • Begin with an alphabetic character (a-z or A-Z)

  • Consist of 4-30 characters

  • Not contain the hostname or IP address of the computer

Note:

You cannot change the Oracle Instance name after installation.

4.3 Determining Port Numbers

If you want to install an Oracle Identity Management 11g Release 1 (11.1.1) component against an existing Oracle Identity Management 11g Release 1 (11.1.1) component, you may need to identify the ports for the existing component. For example, if you want to install Oracle Directory Integration Platform 11g Release 1 (11.1.1) against an existing Oracle Internet Directory 11g Release 1 (11.1.1) component, you must identify its port when you install Oracle Directory Integration Platform.

You can get information about ports using the following:

  • Fusion Middleware Control.

    Click Ports on the Fusion Middleware Control home page. This takes you to a page that lists all ports in use and the suggested port ranges for different components.

  • $ORACLE_INSTANCE/config/OPMN/opmn/ports.prop

    Note:

    If you change a component's port number after installation, the ports.prop file is not updated.
  • The $ORACLE_INSTANCE/bin/opmnctl status -l command to see port numbers of components managed by OPMN.

4.4 Completing an Installation

This topic explains the steps that are common to completing most Oracle Identity Management installations and configurations. It begins with the steps on the Installation Summary screen and ends after the Installation Complete screen.

When the Installation Summary screen appears, perform the following steps to complete the installation:

  1. Verify the installation and configuration information on the Installation Summary screen.

    • Click Save to save the installation response file, which contains your responses to the Installer prompts and fields. You can use this response file to perform silent installations. Refer to Appendix B, "Performing Silent Installations" for more information.

      Note:

      The installation response file is not saved by default—you must click Save to retain it.
    • Click Install. The Installation Progress screen appears.

  2. Monitor the progress of your installation. The location of the installation log file is listed for reference. After the installation progress reaches 100%, click OK. The Configuration Progress screen appears.

    Note:

    On Unix systems, after the installation progress reaches 100%, a confirmation dialog box appears with information about the oracleRoot.sh script. Execute the script in different terminal as described in "Executing the oracleRoot.sh Script on UNIX Platforms" and continue to the Configuration Progress screen.
  3. Monitor the progress of the configuration. The location of the configuration log file is listed for reference. After the configuration progress reaches 100%, the Installation Complete screen appears.

  4. Click Save to save the installation summary file. This file contains information about the configuration, such as locations of install directories and URLs for management components, that will help you get started with administration.

    Note:

    The installation summary file is not saved by default—you must click Save to retain it.

    Click Finish to close and exit the Installer.

4.5 Locating Installation Log Files

The Installer writes log files to the ORACLE_INVENTORY_LOCATION/logs directory on UNIX systems and to the ORACLE_INVENTORY_LOCATION\logs directory on Windows systems.

On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file.

On Microsoft Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

  • installDATE-TIME_STAMP.log

  • installDATE-TIME_STAMP.out

  • installActionsDATE-TIME_STAMP.log

  • installProfileDATE-TIME_STAMP.log

  • oraInstallDATE-TIME_STAMP.err

  • oraInstallDATE-TIME_STAMP.log