2 Using the Oracle Universal Installer in Silent Mode

To install or deinstall Oracle Fusion Middleware, you can use the Oracle Universal Installer in silent mode from the command line.

For information on how to run the Oracle Universal Installer from the command line, see the following topics:

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

Silent installation of your Oracle Fusion Middleware product is accomplished by using the -silent flag on the command line when you start the installer. Most cases, you can supply the location and name of a file containing certain input values (for example, installation location). These are the values that would be asked for during a typical installation using the graphical user interface.

For Oracle Fusion Middleware products, this file is called a response file. For more information, seeAbout Response Files.

Silent installation does not include configuration. That is, you cannot configure your product silently using the same silent installation commands and response file. Configuration is a separate process, unlike in Oracle Fusion Middleware 11g. Refer to the installation guide for your product for complete information about configuring your product.

Note:

For UNIX users, if it is a first-time installation of any Oracle product, you must create the oraInst.loc file before starting. Refer to UNIX Users: Creating the Central Inventory for more information.

Following installation of your product, you can 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.

About Response Files

Before doing a silent installation, you must provide information specific to your installation in a response file (for example, the installation directory). The installer fails 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.

Creating a Response File

Oracle recommends using your product graphical installer or deinstaller to create a response file that you can use to silently install or deinstall your product.

  1. Run your product graphical installer or deinstaller, as described in your product installation guide.
  2. For product installation, on the Installation Summary screen, click Save Response File to save your installation parameters to a response file.

    For product deinstallation, on the Deinstallation Summary screen, click Save Response File to save your deinstallation parameters to a response file.

    You are 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 or deinstallation on other systems, or modify it as needed.

Sample Response Files

The provided sample response files show you the parameters that can be included in a response file for a silent installation or deinstallation.

To see some sample response files that can be used for silent installation, see Sample Response Files for Silent Installation and Deinstallation.

The parameters that can be included in the response files are described in Oracle Universal Installer Response File Parameters.

Oracle Universal Installer Response File Parameters

These parameters can be included in a valid response file for the Oracle Universal Installer.

Table 2-1 Oracle Universal Installer Response File Parameters

Corresponding Screen Parameter Description

Auto Updates

DECLINE_AUTO_UPDATES

Set this parameter to true if you want to skip software updates. The installer will not check for updates that might be applicable to the current product installation.

MOS_USERNAME

MOS_PASSWORD

Provide your My Oracle Support user name and password if you want the installer to automatically search My Oracle Support for software updates that apply to the software products you are about to install.

AUTO_UPDATES_LOCATION

Enter the path for the local directory where your updates are located.

Use this parameter 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.

SOFTWARE_UPDATES_PROXY_SERVER

SOFTWARE_UPDATES_PROXY_PORT

SOFTWARE_UPDATES_PROXY_USER

SOFTWARE_UPDATES_PROXY_PASSWORD

Provide the proxy server information if a proxy server is required for connections to the Internet and for accessing My Oracle Support.

Installation Location

ORACLE_HOME

Location of the Oracle home directory.

Security Updates

MYORACLESUPPORT_USERNAME

MYORACLESUPPORT_PASSWORD

Provide your My Oracle Support user name and password if you want to receive the latest product information and security updates.

DECLINE_SECURITY_UPDATES

Set this parameter to true if you want to decline receiving security updates. By default, this parameter is set to false.

SECURITY_UPDATES_VIA_MYORACLESUPPORT

If you specify values for MYORACLESUPPORT_USERNAME and MYORACLESUPPORT_PASSWORD, this parameter must be set to true.

PROXY_HOST

PROXY_PORT

PROXY_USER

PROXY_PWD

Provide the proxy server information if you use a proxy server in your environment.

COLLECTOR_SUPPORTHUB_URL

The URL of the Oracle Configuration Manager Repeater. The format is:

http://repeater_host:repeater_port

or

https://repeater_host:repeater_port

Installation Type

INSTALL_TYPE

Specify the type of install you want to perform. This value differs depending on your product distribution.

For example, for the Fusion Middleware Infrastructure distribution, the following install types are valid:

  • Fusion Middleware Infrastructure

  • Fusion Middleware Infrastructure With Examples

About the Security of Response Files During Silent Installation

Your response files contain certain passwords required by the installer. Follow these guidelines to minimize security issues regarding these passwords in the response file.

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

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

Running the Oracle Universal Installer in Silent Mode

Follow these instructions to run the Oracle Universal Installer in silent mode and to set up your Oracle central inventory for the first time.

Summary of the Silent Installation Syntax and Commands

To run the product installer from the command line, make sure that you understand the syntax and various command line options you can use for your installation.

The full syntax for running the product installer from the command line is shown below:

java -jar distribution_name.jar [-options] [(<CommandLinevariable=Value>)*]

To run the product installer in silent mode, use -silent mode and specify a response file:

java -jar distribution_name.jar -silent -responseFile file [-options] [(<CommandLinevariable=Value>)*]

The following table lists the valid command line options for silent installation and graphical installation.

Table 2-2 Installer Command Line Options for Silent Installation and Graphical Installation

Option Description

-install

Launches the installer. This is the default operation.

Only one operation can be specified.

-silent

Performs the designated operation (such as -install or -deinstall) in silent mode. If -silent is not specified, a graphical user interface is used.

-help

Displays the usage options for the installer.

-invPtrLoc file

UNIX only - pointer to the central inventory location file. Replace file with the full path and name of the oraInst.loc file.

-responseFile file

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

See About Response Files for information about creating the response files.

-logLevel level

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

  • Severe

  • Warning

  • Info

  • Config

  • Fine

  • Finer

  • Finest

-debug

Obtain debug information from the installer.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage.

-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

The oraparam.ini file is an initialization file for the installer, and is contained inside the distribution .jar file and extracted when the installer is started.

The -paramFile option overrides the default initialization file of the installer.

-compatibilityFile file

Location of the file that specifies feature set dependency changes.

-nowait

Windows only - the installer does not wait for the user to press Enter on the console after the operation (such as -install) is complete.

Installer Variables

Installer variables are specified using varName=value.

UNIX Users: Creating the Central Inventory

The first time you run the installer in silent mode on your UNIX operating system, you need to create a central inventory directory.

As a result, you see a prompt similar to the following example:

You are starting your first installation on this host or you do not have sufficient 
permission to access current inventory. As part of this install, you need to specify a 
directory for installer files. This is called the "inventory directory". Within the inventory 
directory, the installer automatically sets up subdirectories for each product to contain 
inventory data and will consume typically 150 Kilobytes per product. It is recommended 
that this file (oraInst.loc) be created in /etc directory. You need root privileges to do so. You
can exit the installer and run the script located in /tmp/createCentralInventory1371119669507.sh 
to set up the central inventory location.

Follow the instructions described in the prompt to run the /tmp/createCentralInventory.sh script as root to create the oraInst.loc file and your central inventory directory. This must be done before you can continue with your product installation. For more information, see Setting the Oracle Central Inventory Location Using Silent Installation on UNIX Operating Systems.

Sample Output from a Silent Installation

This example shows sample output from a silent Oracle WebLogic Server and Coherence installation.

java -jar fmw_12.2.1.2.0_wls_generic.jar -silent -responseFile /home/exampleuser/response/wls.rsp
Launcher log file is /tmp/OraInstall2016-06-30_07-32-16AM/launcher2016-06-30_07-32-16AM.log
Extracting the installer................... Done
Checking if CPU speed is above 300 MHz.   Actual 2526.998 MHz    Passed
Checking swap space: must be greater than 512 MB.   Actual 10288440 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
Checking temp space: must be greater than 300 MB.   Actual 44752 MB    Passed
 
 
Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2016-06-30_07-32-16AM
Log: /tmp/OraInstall2016-06-30_07-32-16AM/install2016-06-30_07-32-16AM.log
Copyright (c) 1996, 2016, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Skipping Software Updates
Starting check : CertifiedVersions
Expected result: One of oracle-6,oracle-7,redhat-7,redhat-6,SuSE-11,SuSE-12
Actual Result: oracle-6.6
Check complete. The overall result of this check is: Passed
CertifiedVersions Check: Success.

Starting check : CheckJDKVersion
Expected result: 1.8.0_101
Actual Result: 1.8.0_101
Check complete. The overall result of this check is: Passed
CheckJDKVersion Check: Success.

Validations are enabled for this session.
Verifying data
Copying Files
Percent Complete : 10
Percent Complete : 20
Percent Complete : 30
Percent Complete : 40
Percent Complete : 50
Percent Complete : 60
Percent Complete : 70
Percent Complete : 80
Percent Complete : 90
Visit http://www.oracle.com/support/policies.html for Oracle Technical Support policies.
Percent Complete : 100
 
The installation of Oracle Fusion Middleware 12c WebLogic Server and Coherence 12.2.1.2.0 completed successfully.
Logs successfully copied to /home/exampleuser/oraInventory/logs.

Running the Oracle Universal Installer for Silent Deinstallation

Follow these instructions to run the Oracle Universal Installer to deinstall your Oracle Fusion Middleware products in silent mode.

Summary of the Silent Deinstallation Syntax and Commands

To run the product deinstaller from the command line, make sure that you understand the syntax and various command line options you can use for deinstallation.

To deinstall your Oracle Fusion Middleware product in silent mode, use the -silent option from the command line.

The full syntax for running the deinstaller from the command line is shown below:

ORACLE_HOME/oui/bin/deinstall.sh -silent [-options] [(<CommandLinevariable=Value>)*]

The following table lists the valid command line options for silent deinstallation and graphical deinstallation.

Table 2-3 Deinstaller Command Line Options for Silent Deinstallation and Graphical Deinstallation

Options Description

-help

Displays the usage options for the deinstaller.

-deinstall

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

-distributionName name

Specify the name of the distribution you want to remove from the Oracle home. This is necessary if your Oracle home contains multiple distributions (for example, Oracle Fusion Middleware Infrastructure and Oracle SOA Suite).

-distributionVersion version

Specify the version of a particular distribution you want to remove from the Oracle home. This is necessary if your Oracle home contains multiple distributions (for example, Oracle Fusion Middleware Infrastructure and Oracle SOA Suite).

-responseFile file

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

See About Response Files for information about creating the response files.

-logLevel level

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

  • Severe

  • Warning

  • Info

  • Config

  • Fine

  • Finer

  • Finest

-debug

Obtain debug information from the installer.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage.

-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

The oraparam.ini file is an initialization file for the deinstaller.

The -paramFile option overrides the default initialization file of the deinstaller.

-nowait

Windows only - the installer does not wait for the user to press Enter on the console after the operation (such as -install) is complete.

Installer Variables

Installer variables are specified using varName=value.

Sample Silent Deinstall Commands

These commands show how you can deinstall your product in silent mode.

Below is an example silent deinstall command:

ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp

You can include the -logLevel option to create a verbose installation log. See Summary of the Silent Deinstallation Syntax and Commands, for more details about this option.

Below is an example silent deinstall command specifying a response file and FINE as the logging level.

ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp -logLevel FINE

Below is an example silent deinstall command with multiple products in a single Oracle home:

ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/deinstall.rsp -distributionVersion 12.2.1.3.0 -distributionName "Oracle Data Integrator"

For silent deinstall, you have to specify -distributionName and -distributionVersion from command line in case multiple distributions are installed.

Sample Silent Deinstall Output

This example shows sample output from a silent Oracle WebLogic Server and Coherence deinstallation.

ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp
Launcher log file is /tmp/OraInstall2016-06-30_07-50-01AM/launcher2016-06-30_07-50-01AM.log.
Checking if CPU speed is above 300 MHz.   Actual 2526.998 MHz    Passed
Checking swap space: must be greater than 512 MB.   Actual 10288440 MB    Passed
Checking if this platform requires a 64-bit JVM.   Actual 64    Passed (64-bit not required)
Checking temp space: must be greater than 300 MB.   Actual 44752 MB    Passed
 
Log: /tmp/OraInstall2016-06-30_07-50-01AM/deinstall2016-06-30_07-50-01AM.log
Setting ORACLE_HOME to /home/Oracle/products/Oracle_Home
Copyright (c) 1996, 2016, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Starting silent deinstallation...
Percent Complete : 10
Percent Complete : 20
Percent Complete : 30
Percent Complete : 40
Percent Complete : 50
Percent Complete : 60
Percent Complete : 70
Percent Complete : 80
Percent Complete : 90
100%
 
The uninstall of WebLogic Server 12.2.1.2.0 completed successfully.
Logs successfully copied to /home/exampleuser/oraInventory/logs.