This chapter describes how to use the Oracle Universal Installer in silent mode from the command line.
This chapter includes the following sections:
Section 2.3, "Running the Oracle Universal Installer in Silent Mode"
Section 2.4, "Running the Oracle Universal Installer for Silent Deinstallation"
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. In most cases, you will need to 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, see Section 2.2.
Note:
For UNIX users, if this is a first time installation of any Oracle product, you must create the oraInst.loc file before starting. Refer to Section 2.3.2 for more information.
Following installation of your product, 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.
Before doing a silent installation, you must provide information specific to your installation in a response file (for example, the installation directory). 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.
Oracle recommends creating a response file in the following manner:
Run your product's graphical installer or deinstaller, as described in your product installation guide.
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 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 or deinstallation on other systems, or modify it as needed.
To see some sample response files that can be used for silent installation, see Appendix C.
The parameters that can be included in the response files are described in Section 2.2.3.
This section describes the various parameters that can be included in a valid response file for the Oracle Universal Installer.
See Appendix C for some sample response files.
Table 2-1 Response File Parameters
| Corresponding Screen | Parameter | Description |
|---|---|---|
|
|
Location of the Oracle home directory. |
|
|
|
Provide your My Oracle Support user name and password if you want to receive the latest product information and security updates. |
|
|
|
Set this parameter to |
|
|
|
If you specify values for |
|
|
|
Provide the proxy server information if you use a proxy server in your environment. |
|
|
|
The URL of the Oracle Configuration Manager Repeater. The format is: http://repeater_host:repeater_port or https://repeater_host:repeater_port |
|
|
|
Specify the type of install you want to perform. This value will differ depending on your product distribution. For example, for the Fusion Middleware Infrastructure distribution, the following install types are valid:
|
|
|
|
Specify the distribution you want to remove from the Oracle home. This parameter is required if more than one distribution exists in the Oracle home from which the deinstaller program is started. Enter the product name as it appears on the Distribution to Deinstall screen. |
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.
This section describes how to run the Oracle Universal Installer in silent mode and how to set up your Oracle central inventory for the first time.
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>)*]
Table 2-2 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 |
|---|---|
|
Installation Operations - Only One Operation Can be Specified |
|
|
|
Launches the installer. This is the default operation. |
|
Installation Modes |
|
|
|
Performs the designated operation (such as |
|
Installation Options |
|
|
|
Displays the usage options for the installer. |
|
|
UNIX only - pointer to the central inventory location file. Replace file with the full path and name of the |
|
|
Pointer to the response file. Replace file with the full path and name of the response file. See Section 2.2 for information about creating the response files. |
|
|
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:
|
|
|
Obtain debug information from the installer. |
|
|
Allow the silent installation to proceed in a non-empty directory. This option is valid for 11g only. |
|
|
Log debugging information pertaining to disk usage. |
|
|
Log debugging information pertaining to memory usage. |
|
|
Log debugging information pertaining to time usage. |
|
|
Messages will not be displayed to the console window. |
|
|
Ignore the results of the system prerequisite checks and continue with the installation. |
|
|
Execute the system prerequisite checks only, then exit. |
|
|
The The |
|
|
Location of the file that specifies feature set dependency changes. |
|
|
Windows only - the installer does not wait for the user to press Enter on the console after the operation (such as |
|
Command Line Variables |
|
|
Installer Variables |
Installer variables are specified using |
The first time you run the installer in silent mode on your UNIX operating system, you will 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 Section 1.2.1.2
Below is a sample output from a silent Oracle WebLogic Server and Coherence installation.
java -jar fmw_12.1.3.0.0_wls.jar -silent -responseFile /home/exampleuser/response/wls.rsp Extracting files................... Starting Oracle Universal Installer 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/OraInstall2014-04-02_10-32-26AM Log: /home/exampleuser/oraInventory/logs/install2014-04-02_10-32-26AM.log Copyright (c) 1996, 2014, Oracle and/or its affiliates. All rights reserved. Reading response file.. Expected result: One of enterprise-4,enterprise-5,enterprise-6,redhat-6,redhat-4,redhat-5,SuSE-10,SuSE-11 Actual Result: enterprise-5 Check complete. The overall result of this check is: Passed CertifiedVersions Check: Success. Verifying data...... Copying Files... -----------20%----------40%----------60%----------80%-------100% The installation of WebLogic Server 12.1.3.0.0 completed successfully.
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>)*]
Table 2-3 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 |
|---|---|
|
Deinstallation Options |
|
|
|
Displays the usage options for the deinstaller. |
|
|
Launches the deinstaller in GUI mode. This is the default mode and is used if no mode is specified on the command line. |
|
|
Specify the name of the distribution you want to remove from the Oracle home. This is necessary in the event that your Oracle home contains multiple distributions (for example, Oracle Fusion Middleware Infrastructure and Oracle SOA Suite). |
|
|
Specify the version of a particular distribution you want to remove from the Oracle home. This is necessary in the event that your Oracle home contains multiple distributions (for example, Oracle Fusion Middleware Infrastructure and Oracle SOA Suite). |
|
|
Pointer to the response file. Replace file with the full path and name of the response file. See Section 2.2 for information about creating the response files. |
|
|
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:
|
|
|
Obtain debug information from the installer. |
|
|
Log debugging information pertaining to disk usage. |
|
|
Log debugging information pertaining to memory usage. |
|
|
Log debugging information pertaining to time usage. |
|
|
Messages will not be displayed to the console window. |
|
|
Ignore the results of the system prerequisite checks and continue with the installation. |
|
|
Execute the system prerequisite checks only, then exit. |
|
|
The The |
|
|
Location of the file that specifies feature set dependency changes. |
|
Command Line Variables |
|
|
Installer Variables |
Installer variables are specified using |
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 Table 2-3 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.1.3.0.0 -distributionName "Oracle Data Integrator"
For silent deinstall, you have to specify -distributionName and -distributionVersion from command line in case multiple distributions are installed.
Below is sample output from a silent Oracle WebLogic Server and Coherence deinstallation.
ORACLE_HOME/oui/bin/deinstall.sh -silent -responseFile /home/exampleuser/wls_deinstall.rsp
Starting Oracle Universal Installer
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/OraInstall2014-04-02_10-32-26AM
Log: /home/exampleuser/oraInventory/logs/install2014-04-02_10-32-26AM.log
Copyright (c) 1999, 2014, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Starting silent deinstallation...
-----------20%----------40%----------60%----------80%-------100%
The uninstall of WebLogic Server 12.1.3.0.0 completed successfully.