D Silent Installation

This appendix describes how to install Application Developer from the command line in silent mode. This appendix contains the following topics:

D.1 What is a Silent Installation?

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

Silent installation of Application Developer is accomplished by supplying the installer with a response file and using the -silent flag on the command line. The response file is a text file containing variables and parameter values which provide answers to the installer prompts.

Note:

For UNIX users, if this is a first time installation of Application Developer, you must create the oraInst.loc file before starting. Please refer to Section D.3.1, "UNIX Users: Creating the oraInst.loc File" for more information.

Following installation of Application Developer, you need to run the 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.

Note:

For Windows users, if this is a first time installation of Application Developer, you must create the registry keys before starting. Registry key creation is described in Section D.3.2, "Windows Users: Creating the Registry Key"

D.2 Creating Response Files

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

A sample response file called sampleResponse.rsp is provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory on the installation CD-ROM. After using this response file to install Application Developer, you will still need to run the Configuration Wizard to configure the software.

The only parameters you need to specify in this file are ORACLE_HOME and MIDDLEWARE_HOME. See Section D.2.1, "Contents of the sampleResponse.rsp File" to view the contents of this file.

D.2.1 Contents of the sampleResponse.rsp File

This section shows the contents of the Disk1/stage/Response/sampleResponse.rsp response file on a UNIX system:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Provide the Oracle Home location. The location has to be the immediate child under the specified Middleware Home location. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. The total length has to be less than or equal to 128 characters. The location has to be an empty directory or a valid Application Developer Oracle Home.
ORACLE_HOME=/home/Oracle/Middleware/Oracle_APPDEV1
 
#Provide existing Middleware Home location.
MIDDLEWARE_HOME=/home/Oracle/Middleware
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

D.2.2 Creating Your Own Response Files

There are two ways to response create your own response file:

  • Use the sampleResponse.rsp file as a template and copy it to any location on your system. You can then alter the contents as needed and use it for your silent installation.

  • Run the installation GUI, then click Save on the Installation Summary Screen. You will be prompted for a name and location where you want to create this response file. After it is created, you can use it exactly as-is to replicate the installation on other systems, or modify it as needed.

D.2.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.

D.3 Pre-Installation Tasks

This section covers the pre-installation tasks that may be required before you are able to perform a silent installation.

The following topics are covered:

D.3.1 UNIX Users: Creating the oraInst.loc File

The Oracle inventory directory is used by the installer to keep track of all Oracle products installed on the computer. The inventory directory is stored in a file called oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation. This file is used by the installer.

  1. Log in as the root user.

    prompt> su
    
  2. Using a text editor such as vi or emacs, create the oraInst.loc file in the directory of your choice. 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.

  3. Exit from the root user.

    # exit
    

D.3.2 Windows Users: Creating the Registry Key

If you have not installed Application Developer on your computer, then you need to 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

D.4 Silent Installation Instructions

The syntax for running the installer from the command line on UNIX systems is shown below:

runInstaller [-mode] [-options] [(<CommandLinevariable=Value>)*]

On Windows systems:

setup.exe [-mode] [-options] [(<CommandLinevariable=Value>)*]

Table D-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 prerequsites. No software is installed.

-v

-validate

Launches the installer in GUI mode and performs all prequisite 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 prequisite checks and continue with the installation.

-executeSysPrereqs

Execute the system prequisite 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 (on UNIX operating systems) or Disk1\install\platform (on Windows operating systems).

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

An example for UNIX systems:

ORACLE_HOME=/home/Oracle/Middleware/Oracle_APPDEV1

An example for Windows systems:

ORACLE_HOME=C:\Products\Oracle\Middleware\Oracle_APPDEV1

Session Variables

Session variables are specified using session:varName=value.

Component Variables

Component variables are specified using session:compInternalName:[Version:]varName=value.


D.4.1 Sample Commands

If this is the first time you are installing on your system (meaning there is no pre-existing Oracle Inventory location), use the following command to perform a silent installation on UNIX systems:

./runInstaller -silent -response file -invPtrLoc file

On Windows systems:

setup.exe -silent -response file -invPtrLoc file

Below is a full example of this command for UNIX systems:

./runInstaller -silent -response /home/Oracle/response/appdev_inst.rsp -invPtrLoc /home/jdoe/oraInst.loc

On Windows operating systems:

setup.exe -silent -response C:\home\Oracle\response\appdev_inst.rsp -invPtrLoc c:\home\Oracle\oraInst.loc

If you have already installed an Oracle product on your system and do not need to specify an inventory location, then you can use a command similar to the following on UNIX systems:

./runInstaller -silent -response file

On Windows systems:

setup.exe -silent -response file

Below is a full example of this command on a UNIX system:

./runInstaller -silent -response /home/Oracle/response/appdev_inst.rsp

On Windows operating systems:

setup.exe -silent -response c:\home\Oracle\response\appdev_inst.rsp

D.4.2 Sample Output

Below is a sample output from a silent install using the sampleResponse.rsp template:

$ ./runInstaller -jreLoc /home/Oracle/Middleware/jdk160_14_R27.6.4-18/ -silent -response /home/Oracle/response/sampleResponse.rsp
Platform is Linux X86 32 bit
Starting Oracle Universal Installer...
 
Checking if CPU speed is above 300 MHz.    Actual 2999 MHz    Passed
Checking Temp space: must be greater than 150 MB.   Actual 69795 MB    Passed
Checking swap space: must be greater than 512 MB.   Actual 4029 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-22_12-35-31PM. Please wait ...[user@system Disk1]$ Log: /home/Oracle/oraInventory/logs/install2009-04-22_12-35-31PM.log
Copyright © 1999, 2009, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Expected result: One of enterprise-4,enterprise-5,redhat-4,redhat-5,SuSE-10
Actual Result: enterprise-4
Check complete. The overall result of this check is: Passed
CertifiedVersions Check: Success.
Checking for gcc-3.4.3-22.1; found gcc-3.4.6-10.0.1-i386.       Passed
Checking for gcc-c++-3.4.3-22.1; found gcc-c++-3.4.6-10.0.1-i386.       Passed
Checking for openmotif21-2.1.30-11.RHEL4.4 ; found openmotif21-2.1.30-11.0.1.RHEL4.6-i386.      Passed
Checking for setarch-1.6-1; found setarch-1.6-1-i386.   Passed
Checking for pdksh-5.2.14-30; found pdksh-5.2.14-30.6-i386.     Passed
Checking for sysstat-5.0.5-1; found sysstat-5.0.5-19.el4-i386.  Passed
Checking for gnome-libs-1:1.4.1.2.90-44.1; found gnome-libs-1:1.4.1.2.90-44.2-i386.     Passed
Checking for libstdc++-3.4.3-22.1 ; found libstdc++-3.4.6-10.0.1-i386.  Passed
Checking for libstdc++-devel-3.4.3-22.1; found libstdc++-devel-3.4.6-10.0.1-i386.       Passed
Checking for compat-libstdc++-296-2.96-132.7.2; found compat-libstdc++-296-2.96-132.7.2-i386.   Passed
Checking for compat-db-4.1.25-9; found compat-db-4.1.25-9-i386. Passed
Checking for control-center-2.8.0-12; found control-center-1:2.8.0-12.rhel4.5-i386.     Passed
Checking for glibc-common-2.3.4-2.9; found glibc-common-2.3.4-2.41-i386.        Passed
Checking for binutils-2.15.92.0.2-13; found binutils-2.15.92.0.2-25-i386.       Passed
Checking for make-1:3.80-5; found make-1:3.80-7.EL4-i386.       Passed
Checking for xscreensaver-4.18-5.rhel4.2; found xscreensaver-1:4.18-5.rhel4.14.0.1-i386.        Passed
Check complete. The overall result of this check is: Passed
Packages Check: Success.
Checking for VERSION=2.6.9; found VERSION=2.6.9-78.0.0.0.1.ELxenU.      Passed
Checking for hardnofiles=4096; found hardnofiles=4096.  Passed
Checking for softnofiles=4096; found softnofiles=4096.  Passed
Check complete. The overall result of this check is: Passed
Kernel Check: Success.
Expected result: ATLEAST=2.3.4-2.19 
Actual Result: 2.3.4-2.41
Check complete. The overall result of this check is: Passed
GLIBC Check: Success.
Expected result: 922MB
Actual Result: 4000MB
Check complete. The overall result of this check is: Passed
TotalMemory Check: Success.
Verifying data......
Copying Files...
-----------20%----------40%----------60%----------80%--------100%
 
The installation of Oracle Application Developer 11g completed successfully.

D.5 Silent De-Installation

You can also de-install the software on your system by using the -d or -deinstall parameter from the command line.

On UNIX systems:

./runInstaller -silent -deinstall -response file

On Windows systems:

setup.exe -silent -deinstall -response file