4.1 Common Installation Tasks for OID, OVD, ODSM, ODIP, and OIF (11.1.1.4.0)

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

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: DRIVE:\setup.exe

   After the Installer starts, the Welcome screen appears.

2. Continue the installation or patching process by clicking Next on the Welcome screen.

   For more information about patching an Oracle Identity Management 11.1.1.2.0 installation to 11.1.1.4.0, see Patching the Oracle Identity Management 11.1.1.2.0 to 11.1.1.4.0.

4.1.2 Creating the Inventory Directory (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 4-1 to configure the inventory directory information:

4.1.3 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:

• Oracle Middleware Home Location

• Oracle Home Directory

• WebLogic Server Directory

• Oracle Instance Location

• Oracle Instance Name

4.1.4 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:

• WebLogic Server Administration Console.

  Log in to the Administration Console. Click on Servers under Environment to see what ports are in use for the Administration Server and Managed Servers.

• $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.1.5 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 C, "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%, 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. By default the installation summary file, which can help you get started with administration, is saved to the OUI_INVENTORY/logs/ directory. The filename is of the form: installSummaryDATE.txt. This file contains information about the configuration, such as locations of install directories and URLs for management components.

   If desired, you can click the Save button on the Installation Complete screen and choose a different name and location for the file.

   Click Finish to close and exit the Installer.

4.1.6 Optional: Configuring the Minimum Amount for Oracle WebLogic Server's Maximum Heap Size

After installing Oracle Identity Management 11g Release 1 (11.1.1), if you want to configure the minimum (lowest) level of maximum heap size (-Xmx) required for Oracle WebLogic Server to host Oracle Identity Management components, perform the steps in this section.

The minimum (lowest) levels for maximum heap size are:

• Oracle WebLogic Administration Server: 512 MB

• Oracle WebLogic Managed Server: 256 MB

Perform the following steps to configure the heap size for Oracle WebLogic Administration Servers and Oracle WebLogic Managed Servers:

1. Open the setDomainEnv script (.sh or .bat) in the MW_HOME/user_projects/domains/DOMAIN_NAME/bin/ directory.

2. Locate the last occurrence of the EXTRA_JAVA_PROPERTIES entry.

3. In the last occurrence of the EXTRA_JAVA_PROPERTIES entry, locate the last occurrence of heap size parameters: -Xmx, -Xms, and so on.

   Note:

   These are the heap size parameters for the Oracle WebLogic Administration Server.

4. Set the heap size parameters (-Xms and -Xmx) for the Oracle WebLogic Administration Server as desired, for example: -Xms256m and -Xmx512m

5. To set the heap size parameters for the Oracle WebLogic Managed Server, enter the text in Example 4-1 immediately below the last occurrence of the EXTRA_JAVA_PROPERTIES entry and:

   • Set the heap size parameters (-Xms and -Xmx) as desired, for example: -Xms256m -Xmx256m

   • Replace wls_ods1 with the name of the Oracle WebLogic Managed Server hosting Oracle Directory Services Manager.

   • Replace wls_oif1 with the name the Oracle WebLogic Managed Server hosting Oracle Identity Federation.

   Example 4-1 Heap Size Parameters for Oracle WebLogic Managed Server

   if [ "${SERVER_NAME}" = "wls_ods1" -o  "${SERVER_NAME}" = "wls_oif1" ] ; then
           EXTRA_JAVA_PROPERTIES=" ${EXTRA_JAVA_PROPERTIES} -Xms256m -Xmx256m "
           export EXTRA_JAVA_PROPERTIES
   fi
   

6. Save and close the setDomainEnv script.

7. Restart the Oracle WebLogic Administration Server and the Oracle WebLogic Managed Server by referring to Appendix B, "Starting or Stopping the Oracle Stack."

4.1.7 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

• opatchDATE-TIME_STAMP.log