B Performing Silent Installations

This appendix describes how to install Oracle Identity Management in silent mode. This appendix contains the following topics:

B.1 What is a Silent Installation?

A silent installation eliminates the need to monitor the Oracle Identity Management installation because no graphical output is displayed and no input by the user is required.

To perform a silent Oracle Identity Management installation, you invoke the Installer with the -silent flag and provide a response file from the command line. The response file is a text file containing variables and parameter values which provide answers to the Installer prompts.

B.2 Before Performing a Silent Installation

This topic describes tasks that may be required before you perform a silent installation. This topic includes the following sections:

B.2.1 UNIX Systems: Creating the oraInst.loc File

The Installer uses the Oracle inventory directory to keep track of all Oracle products installed on the systems. The inventory directory is stored in a file named oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation.

Perform the following steps to create the oraInst.loc file if it does not exist:

  1. Log in as the root user.

  2. Using a text editor such as vi or emacs, create the oraInst.loc file in any directory. 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. Replace oui_install_group with the name of the group whose members have write permissions to this directory.

  3. Exit from the root user.

Note:

After you performing the silent installation on UNIX platforms, you must run the ORACLE_HOME/root.sh script as the root user. The root.sh script detects settings of environment variables and enables you to enter the full path of the local bin directory.

B.2.2 Windows Systems: Creating the Registry Key

If you have not installed Oracle Identity Management on your system, you must create the following Registry key and value:

HKEY_LOCAL_MACHINE / SOFTWARE / Oracle / inst_loc = [inventory_directory]

Replace inventory_directory with the full path to your Installer files. For example: C:\Program Files\Oracle\Inventory

B.3 Creating Response Files

Before performing a silent installation, you must provide information specific to your installation in a response file. Response files are text files that you can create or edit in a text editor. The Installer will fail if you attempt a silent installation using a response file that is not configured correctly.

Several default response files, which you can use as templates and customize for your environment, are included in the installation media. These default response files are located in the Disk1/stage/Response directory on UNIX, or in the Disk1\stage\Response directory on Windows.

Creating Response Files for Oracle Identity Management Software Installation

When you use the Oracle Identity Management Installation Wizard to install the software for the first time, you can save a summary of your installation in a response file.

To create a response file for Oracle Identity and Access Management software Installer for Oracle Identity Manager, Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlements Server, and Oracle Identity Navigator, complete the following steps:

  1. On the Installation Summary screen in the installation wizard, click Save in the Save Response File field.

  2. When prompted, save the file to a local directory.

Creating Response Files for Oracle Identity Manager Configuration

When you use the Oracle Identity Manager Configuration Wizard to configure Oracle Identity Manager Server, Design Console, or Remote Manager for the first time, you can save a summary of your configuration in a response file.

To create this response file, complete the following steps:

  1. On the Configuration Summary screen in the installation wizard, click Save in the Save Response File field.

  2. When prompted, save the file to a local directory.

B.3.1 OID, OVD, ODSM, ODIP, and OIF

The following is a list of the default response files included in the installation media for the Oracle Identity Management Suite containing Oracle Internet Directory (OID), Oracle Virtual Directory (OVD), Oracle Directory Services Manager (ODSM), Oracle Directory Integration Platform (ODIP), and Oracle Identity Federation (OIF):

  • im_install_only.rsp: Use this response file to install Oracle Identity Management components without configuring them.

  • im_install_config.rsp: Use this response file to install and configure Oracle Identity Management components.

  • im_config_only.rsp: Use this response file with the Oracle Identity Management 11g Release 1 (11.1.1) Configuration Wizard (config.sh script or config.bat) in ORACLE_HOME/bin/ to configure installed components.

B.3.2 OIM, OAM, OAAM, OES, and OIN

The following is a list of the default response files included in the installation media for the Oracle Identity Management Suite containing Oracle Identity Manager (OIM), Oracle Access Manager (OAM), Oracle Adaptive Access Manager (OAAM), Oracle Entitlements Server (OES), and Oracle Identity Navigator (OIN):

  • iamsuite_install_only.rsp: Use this response file to install Oracle Identity Management components without configuring them.

  • iamsuite_config_only.rsp: Use this response file with the Oracle Identity Manager 11g Release 1 (11.1.1) Configuration Wizard (config.sh script or config.bat) in ORACLE_HOME/bin/ to configure Oracle Identity Manager Server, Design Console, and Remote Manager.

  • deinstall_oh.rsp: Use this response file with the Oracle Identity Management 11g Release 1 (11.1.1) Deinstaller to deinstall installed components.

B.3.3 Securing Your Silent Installation

Your response files contain certain passwords required by the Installer. To minimize security issues regarding these passwords in the response file, follow these guidelines:

  • Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.

  • If possible, remove the response files from the system after the silent installation is completed.

B.4 Performing a Silent Installation

To perform a silent Oracle Identity Management installation, you invoke the Installer with the -silent flag and provide a response file from the command line.

On UNIX

The following is the syntax for running the Installer from the command line on UNIX systems:

runInstaller [-mode] [-options] [(COMMAND_LINE_VARIABLE=VARIABLE_VALUE)*]

For example:

./runInstaller -silent -response FILE

On Windows

The following is the syntax for running the Installer from the command line on Windows systems:

setup.exe [-mode] [-options] [(COMMAND_LINE_VARIABLE=VARIABLE_VALUE)*]

For example:

setup.exe -silent -response FILE

B.5 Installer Command Line Parameters

Table (UNKNOWN STEP NUMBER) lists and describes supported Installer command line parameters:

Table B-1 Installer Command Line Parameters

Parameter Description

Installation Modes - Only One Mode Can be Specified

-i | -install

Launches the Installer in GUI mode. This is the default mode and is used if no mode is specified on the command line.

-silent

Install in silent mode. The Installer must be passed either a response file or command line variable value pairs.

-d | -deinstall

Launches the Installer in GUI mode for deinstallation.

-p | -prerequisite

Launches the Installer in GUI mode but only checks the prerequisites. No software is installed.

-v | -validate

Launches the Installer in GUI mode and performs all prerequisite and validation checking, but does not install any software.

-sv | -silentvalidate

Performs all prerequisite and validation checking in silent mode. You must pass the Installer either a response file or a series of command line variable value pairs.

Installation Options

-help | --help | --usage

Displays the usage parameters for the runInstaller command.

-invPtrLoc file

Pointer to the inventory location file. Replace file with the full path and name of the oraInst.loc file.

-response file | -responseFile file

Pointer to the response file. Replace file with the full path and name of the response file.

-jreLoc location

Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where your JRE is installed.

-logLevel level

Specify the level of logging performed by the Installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:

  • severe

  • warning

  • info

  • config

  • fine

  • finer

  • finest

-debug

Obtain debug information from the Installer.

-force

Allow the silent installation to proceed in a non-empty directory.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage. This command causes the timeTakentimestamp.log file to be created.

-waitforcompletion

Windows only - the Installer will wait for completion instead of spawning the Java engine and exiting.

-noconsole

Messages will not be displayed to the console window.

-ignoreSysPrereqs

Ignore the results of the system prerequisite checks and continue with the installation.

-executeSysPrereqs

Execute the system prerequisite checks only, then exit.

-paramFile file

Specify the full path to the oraparam.ini file. This file is the initialization file for the Installer. The default location of this file is Disk1/install/platform.

-novalidation

Disables all validation checking performed by the Installer.

-nodefaultinput

For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated.

Command Line Variables

Installer Variables

Installer variables are specified using varName=value. For example:

ORACLE_HOME=/scratch/install/IDM_Home

Session Variables

Session variables are specified using session:varName=value