This chapter describes how to install and deinstall your Oracle Fusion Middleware environment from the command line in silent mode.
This chapter contains the following content:
Section 4.5, "Creating the Middleware Home Directory in Silent Mode"
Section 4.6, "Installing Your Oracle Fusion Middleware Product in Silent Mode"
Section 4.8, "Configuring Your Oracle Fusion Middleware Product in Silent Mode"
Section 4.9, "Deinstalling Your Oracle Fusion Middleware Product in Silent Mode"
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 variable and parameter 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 typically called a response file. For more information, see Section 4.2, "Understanding Response Files".
Note:
For UNIX users, if this is a first time installation of any Oracle product, you must create theoraInst.loc file before starting. Please refer to Section 4.3.1, "UNIX Users: Creating the oraInst.loc File" 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.
Note:
For Windows users, if this is a first time installation of any Oracle product, you must create the registry keys before starting. Registry key creation is described in Section 4.3.2, "Windows Users: Creating the Registry Key"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, as described in your product installation guide.
On the Installation Summary screen, click Save to save your installation 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 on other systems, or modify it as needed.
Pre-existing sample response files are provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory in the location where you unzipped your downloaded archive files for installation.
Refer to your product installation guide for more detailed descriptions of the sample installation and deinstallation response files that are provided for each product.
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 covers the pre-installation tasks that may be required before you are able to perform a silent installation.
The following topics are covered:
oraInst.loc FileThe 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.
Log in as the root user.
prompt> su
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.
Exit from the root user.
# exit
If you have not installed Oracle SOA Suite 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
If your Oracle Fusion Middleware product requires database schemas, you must first create the schemas in your database before installing and configuring your product.
For instructions on how to create the schemas in silent mode, refer to "Running Repository Creation Utility (RCU) from the Command Line" in Oracle Fusion Middleware Repository Creation Utility User's Guide.
Installation of all Oracle Fusion Middleware products requires the presence of an Oracle Middleware home directory, which can be created by installing Oracle WebLogic Server.
To install the latest Oracle WebLogic Server in silent mode, see "Product Distribution" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server to obtain the latest software, and "Running the Installation Program in Silent Mode" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server for silent installation instructions.
To install your Oracle Fusion Middleware product in silent mode, use the -silent mode from the command line. The full syntax for running the installer from the command line on UNIX operating systems is shown below:
runInstaller [-mode] [-options] [(<CommandLinevariable=Value>)*]
On Windows operating systems:
setup.exe [-mode] [-options] [(<CommandLinevariable=Value>)*]
Table 4-1 lists the valid command line parameters for silent installation.
Table 4-1 Installer Command Line Parameters
| Parameter | Description |
|---|---|
|
Installation Modes - Only One Mode Can be Specified |
|
|
|
Launches the installer in GUI mode. This is the default mode and is used if no mode is specified on the command line. |
|
|
Install in silent mode. The installer must be passed either a response file or command line variable value pairs. |
|
|
Launches the installer in GUI mode for deinstallation. NOTE: this option is only available when you start the deinstaller from the |
|
|
Launches the installer in GUI mode but only checks the prerequisites. No software is installed. |
|
|
Launches the installer in GUI mode and performs all prerequisite and validation checking, but does not install any software. |
|
|
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 |
|
|
|
Displays the usage parameters for the NOTE: the |
|
|
Pointer to the 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 4.2, "Understanding Response Files" for information about creating the response files. |
|
|
Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the |
|
|
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. |
|
|
Log debugging information pertaining to disk usage. |
|
|
Log debugging information pertaining to memory usage. |
|
|
Log debugging information pertaining to time usage. This command causes the |
|
|
Windows only - the installer will wait for completion instead of spawning the Java engine and exiting. NOTE: this option only works if the command is invoked from a script; for example, if a |
|
|
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. |
|
|
Specify the full path to the |
|
|
Disables all validation checking performed by the installer. |
|
|
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 ORACLE_HOME=/home/Oracle/Middleware/as_1 On a Windows operating system: ORACLE_HOME=C:\products\Oracle\Middleware\as_1 |
|
Session Variables |
Session variables are specified using |
|
Component Variables |
Component variables are specified using |
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/devSOA.rsp -invPtrLoc /home/jdoe/oraInst.loc
On Windows operating systems:
setup.exe -silent -response C:\home\Oracle\response\devSOA.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/devSOA.rsp
On Windows operating systems:
setup.exe -silent -response c:\home\Oracle\response\devSOA.rsp
Below is a sample output from a silent Oracle SOA Suite installation using the sampleResponse_wls.rsp template:
$ ./runInstaller -jreLoc /home/Oracle/Middleware/jdk160_version/ -silent -response /home/Oracle/response/sampleResponse_wls.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 69669 MB Passed
Checking swap space: must be greater than 512 MB. Actual 1395 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-03_10-49-20PM. Please wait ...[jdoe@examplehost Disk1]$ Log: /home/Oracle/oraInventory/logs/install2009-04-03_10-49-20PM.log
Copyright © 1999, 2012, 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 SOA Suite 11g completed successfully.
The Oracle Web Tier installer does not provide a mechanism for creating an Oracle WebLogic Server domain.
If you are performing a silent installation of Oracle Web Tier without a WebLogic Server domain already configured on your system, and you want to associate your components with a WebLogic Server domain, or you have a need to be able to create a WebLogic Domain in silent mode, you can use the procedure described in this section to create and enable a WebLogic Server domain using WebLogic Server Scripting Tool (WLST) scripts:
Task 1: Install the Latest Oracle WebLogic Server in Silent Mode
Task 4: Start the Administration Server in the WebLogic Server Domain
See Section 4.5, "Creating the Middleware Home Directory in Silent Mode".
Create a WLST script containing the following WLST commands to create the WebLogic Server domain:
#!/usr/bin/python
import os, sys
readTemplate('WebLogic_Server_Home/common/templates/domains/wls.jar')
cd('/Security/base_domain/User/admin_name')
cmo.setPassword('examplepassword')
cd('/Server/AdminServer')
cmo.setName('admin_server_name')
cmo.setListenPort(admin_server_port)
cmo.setListenAddress('admin_server_address')
writeDomain('DOMAIN_HOME')
closeTemplate()
exit()
For example, you could create a file called create_domain_7001.py that contained the following:
#!/usr/bin/python
import os, sys
readTemplate('/oracle/Middleware/wlserver_10.3/common/templates/domains/wls.jar')
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('ExamplePassword1')
cd('/Server/AdminServer')
cmo.setName('AdminServer')
cmo.setListenPort(7001)
cmo.setListenAddress('examplehost.exampledomain.com')
writeDomain('/oracle/Domains/ExampleSilentWTDomain')
closeTemplate()
exit()
To run the script:
Set the environment
cd WebLogic_Server_Home/common/bin
./commEnv.sh
Run the script using WLST. For example:
wlst path_to_script/create_domain_7001.py
Create a second script containing the following WLST commands to enable the WebLogic Server domain with JRF and EM:
#!/usr/bin/python
import os, sys
readDomain('DOMAIN_HOME')
addTemplate('MW_HOME/oracle_common/common/templates/applications/jrf_template_11.1.1.jar')
addTemplate('MW_HOME/oracle_common/common/templates/applications/oracle.em_11_1_1_0_0_template.jar')
updateDomain()
closeDomain()
exit()
For example, you could create a file called enable_domain_7001.py that contained the following:
#!/usr/bin/python
import os, sys
readDomain('/oracle/Domains/ExampleSilentWTDomain')
addTemplate('/oracle/Middleware/oracle_common/common/templates/applications/jrf_template_11.1.1.jar')
addTemplate('/oracle/Middleware/oracle_common/common/templates/applications/oracle.em_11_1_1_0_0_template.jar')
updateDomain()
closeDomain()
exit()
After the script is created, run it using WLST. For example:
wlst path_to_script/enable_domain_7001.py
To see which domain templates are required for your Fusion Middleware product or component, refer to "Fusion Middleware Product Templates" in Oracle Fusion Middleware Domain Template Reference.
After the domain is created, start the Administration Server. Run the startWebLogic.sh (on UNIX operating systems) or startWebLogic.cmd (on Windows operating systems) script in the directory where you created your new domain.
For example, on UNIX operating systems:
cd /oracle/Domains/ExampleSilentWTDomain ./startWebLogic.sh
On Windows operating systems:
cd C:\Oracle\Domains\ExampleSilentWTDomain startWebLogic.cmd
Login to Fusion Middleware Control using the following URL:
http://administration_server_host:administration_server_port/em
Login to the Administration Server Console using the following URL:
http://administration_server_host:administration_server_port/console
The way in which you can configure your Oracle Fusion Middleware product from the command line varies depending on the type of product.
If your product contains system components (for example, Oracle Web Tier, Oracle Portal, Forms, Reports and Discoverer, or Oracle Identity Management), you can use the same commands as described in Section 4.6, "Installing Your Oracle Fusion Middleware Product in Silent Mode".
These products use the same engine for both installation and configuration, so the contents of the response file determine whether you are only installing the software, only configuring existing software, or installing and configuring at the same time.
As mentioned in Section 4.2, "Understanding Response Files", the recommended way to create these response files is to run the graphical installer once and save the configuration to a response file. Each product also comes with sample response files that you can use. Refer to the product installation guides for more information.
Below are some example silent configuration commands, assuming you have previously performed a software-only installation (did not run the configuration tool).
On UNIX operating systems:
./config.sh -silent -response response_file
For example:
./config.sh -silent -response /home/Oracle/response/devSOA.rsp
On Windows operating systems:
config.bat -silent -response response_file
For example:
config.bat -silent -response C:\home\Oracle\response\devSOA.rsp
If your product contains Java components (for example, Oracle SOA Suite, Oracle WebCenter Content, Oracle WebCenter Portal), the installer and the Configuration Wizard are essentially different products and therefore you cannot configure your products silently using the same silent installation commands.
Instead, silent configuration for Java components must be done using WebLogic Scripting Tool (WLST) commands.
For more information, refer to:
To deinstall the Oracle Fusion Middleware product software on your system (both system and java components), use the -d or -deinstall parameter from the command line. You must start the deinstaller from the ORACLE_HOME/oui/bin (on UNIX operating systems) or ORACLE_HOME\oui\bin (on Windows operating systems) directory; this is the only directory where the -d or -deinstall parameters are accepted.
On UNIX operating systems:
./runInstaller -silent -deinstall -response file
On Windows operating systems:
setup.exe -silent -deinstall -response file
Table 4-2 lists the valid command line parameters for silent deinstallation.
Table 4-2 Deinstaller Command Line Parameters
| Parameter | Description |
|---|---|
|
Installation Modes - Only One Mode Can be Specified |
|
|
|
Launches the installer in GUI mode for deinstallation. |
|
Installation Options |
|
|
|
Displays the usage parameters for the |
|
|
Pointer to the 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. |
|
|
Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the |
|
|
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. |
|
|
Log debugging information pertaining to disk usage. |
|
|
Log debugging information pertaining to memory usage. |
|
|
Log debugging information pertaining to time usage. This command causes the |
|
|
Windows only - the installer will wait for completion instead of spawning the Java engine and exiting. |
|
|
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. |
|
|
Specify the full path to the |
|
|
Disables all validation checking performed by the installer. |
|
|
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 ORACLE_HOME=/home/Oracle/Middleware/as_1 On a Windows operating system: ORACLE_HOME=C:\products\Oracle\Middleware\as_1 |
|
Session Variables |
Session variables are specified using |
|
Component Variables |
Component variables are specified using |
Below is a sample output from a silent deinstall using the deinstall_oh.rsp template:
$ ./runInstaller -silent -deinstall -jreLoc /home/Oracle/Middleware/jdk160_version/ -response /home/Oracle/Response/deinstall_oh.rsp
Starting Oracle Universal Installer...
Checking swap space: must be greater than 500 MB. Actual 4047 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-03-26_10-01-21AM. Please wait ...[]$ Log: /home/oraInventory/logs/deinstall2010-03-26_10-01-21AM.log
Reading response file..
Starting silent deinstallation...
Starting Oracle Home deinstallation...
Completed deinstallation of Oracle Home.