WOW - this is the best idea I ever saw to install AVIRA AntiVir completely silent and unattended! I don't like the AutoIt-scripts where you can see all the windows appearing and disappearing again (BTW, is it possible to hide these installation-windows with AutoIt, maybe with moving it out of the screen?).
This appendix describes how to install Oracle Identity Management in silent mode. This appendix contains the following topics:
H.1 What is a Silent Installation?
A silent installation eliminates the need to monitor the Oracle Identity and Access Management installation because no graphical output is displayed and no input by the user is required.
To perform a silent Oracle Identity and Access 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.H.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:
H.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:- Log in as the root user.
- 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: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.
- 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.
H.2.2 Windows Systems: Creating the Registry Key
If you have not installed Oracle Identity and Access Management on your system, you must create the following Registry key and value:
Replace inventory_directory with the full path to your Installer files. For example:
C:Program FilesOracleInventory
H.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 Disk1stageResponse directory on Windows.
Creating Response Files for Oracle Identity and Access Management Software Installation
When you use the Oracle Identity and Access 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 Management, Oracle Adaptive Access Manager, Oracle Entitlements Server, Oracle Access Management Mobile and Social, Oracle Privileged Account Manager, and Oracle Identity Navigator, complete the following steps:
- On the Installation Summary screen in the installation wizard, click Save in the Save Response File field.
- 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:
- On the Configuration Summary screen in the installation wizard, click Save in the Save Response File field.
- When prompted, save the file to a local directory.
H.3.1 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 and Access Management Suite containing Oracle Identity Manager, Oracle Access Management, Oracle Adaptive Access Manager, Oracle Entitlements Server, Oracle Privileged Account Manager, Oracle Access Management Mobile and Social, and Oracle Identity Navigator:
iamsuite_install_only.rsp
: Use this response file to install Oracle Identity and Access 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 orconfig.bat
) inORACLE_HOME
/bin/ to configure Oracle Identity Manager Server, Design Console, and Remote Manager.deinstall_oh.rsp
: Use this response file with the Oracle Identity and Access Management Deinstaller to deinstall installed components.
H.3.2 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.
H.4 Performing a Silent Installation
To perform a silent Oracle Identity and Access 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:
For example:
On Windows
The following is the syntax for running the Installer from the command line on Windows systems:
For example:
H.5 Installer Command Line Parameters
Table (UNKNOWN STEP NUMBER) lists and describes supported Installer command line parameters:
Table H-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:
|
-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: |
Session Variables | Session variables are specified using session:varName=value |
The following sections describe how to run the installation program in silent mode:
What Is Silent-Mode Installation?
Silent-mode installation allows you to define an installation configuration only once and then use the configuration to duplicate the installation on many machines. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create before beginning the installation. The installation program does not display any configuration options during the installation process. Silent-mode installation works on both Windows and UNIX systems.
The instructions in this section are based on the assumption that you have already acquired the installation program as described in Product Distribution.
Overview of Silent-Mode Installation Steps
The silent-mode installation process has two primary steps:
![Exe install switches Exe install switches](/uploads/1/2/5/6/125608629/953553018.png)
- Create a
silent.xml
file that defines the installation configuration that you would normally enter during an interactive installation process, such as graphical-mode or console-mode installation. For example, insilent.xml
, you can supply the values for the Middleware home directory, the product directory, and the components to be installed.For more information, see Creating a silent.xml File for Silent-Mode Installation. - Start the silent-mode installation as described in the section that is appropriate for your situation:
Important Considerations for Silent-Mode Installation
When using silent mode, keep the following considerations in mind:
- Silent-mode installation requires the same amount of temporary disk space and uses the same temporary storage directories as a standard installation. The installation program does not alert you if there is not enough space in the temporary directory.
- A silent-mode installation takes the same amount of time as a standard installation. At the beginning of a silent-mode installation, an initial installation program window or message is displayed briefly, indicating that the installation has started. No messages are displayed to indicate that the installation is in progress or has completed successfully.
- Incorrect entries in the
silent.xml
file can cause installation failures. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation. - The XML definition (
<?xml version='1.0' encoding='UTF-8'?>
) must be at the very beginning of thesilent.xml
file. Do not enter a space or line breaks before the XML definition. - You cannot reinstall any WebLogic product on top of a previously installed version of the same product—in the same Middleware home directory or in the same file location. To reinstall the same version of a product, you must first uninstall the previously installed instance of it or install the new instance in another location.You can, however, add products and product components to an existing installation. For example, you can install Core Application Server, Administration Console, and Configuration Wizard Upgrade Framework during one installation, and add WebLogic JDBC Drivers and Server Examples during a separate installation.
Creating a silent.xml File for Silent-Mode Installation
When you install your software in silent mode, the installation program uses an XML file (
silent.xml
) to determine which installation options should be implemented. Before you can run the installation program in silent mode, you must first create a silent.xml
file.To create a
silent.xml
file:- Copy the sample code provided in Sample silent.xml File for Silent Mode Installation, and paste the code in an XML file.
- Save the file, with the name
silent.xml
, in the same directory that contains the installation program.Note:The XML definition (<?xml version='1.0' encoding='UTF-8'?>)
must be at the very beginning of thesilent.xml
file. Do not enter a space or line breaks before the XML definition. - In the
silent.xml
file that you saved on your system, edit the values for the>Data-Value NameDescriptionThe full path for the Middleware home directory of your choice. For more information about the home directory, see Choosing a Middleware Home Directory.These parameters enable support for Oracle Configuration Manager (OCM). If your computer connects to the internet via a proxy server, use these>If you have a My Oracle Support account and want to receive security updates from Oracle, specify the email address and password for your My Oracle Support account.If you do not want to receive security updates from Oracle, do not specify these values.The full path for the directory where you want to install WebLogic Server (for example, for Windows:C:
MW_HOME
wlserver_10.3
whereMW_HOME
is the name of the Middleware home directory specified by theBEAHOME
>Specify the components and subcomponents you want to install on your system.To install WebLogic Server components, use the following values:To install Coherence components, use the following syntax:To install Enterprise Pack for Eclipse, use the following value (there are no sub-components for this product):For additional information about entering these values, see Guidelines for Component Selection. Note that you should not have any spaces between components, as shown in the example in Sample silent.xml File for Silent Mode Installation,(Windows platforms only)yes
to install the WebLogic Server Node Manager as a Windows service.- no to skip the installation of the WebLogic Server Node Manager as a Windows service. The default is
no
.
Note: You must have Administrator privileges to install Node Manager as a Windows service.The Node Manager listen port.If you do not specify a port number, the installer uses the default port 5556.If the port number is in use, the installer scans for the next available port and assigns it to Node Manager.Note: TheINSTALL_NODE_MANAGER_SERVICE
option must be set toyes
.When the installation process completes, Node Manager is started using the specified port.true
, oryes
, to create the shortcuts in the All Users folder. The default is true.false
, orno
, to create the shortcuts in the local users folder.
The person performing the installation must have administrator privileges to install the Start menu shortcuts in the All Users folder. For more information, see Administrator Privileges.This is an optional element with which you can specify the local JDKs to be installed. Enter the full path of the JDKs to be installed, separated by the pipe symbol ('|').This is an optional element you can use to specify the Oracle-supplied JDKs to be installed. Enter the full path of the JDKs to be installed, separated by the pipe symbol ('|').
Guidelines for Component Selection
Use the following guidelines when specifying values for the
COMPONENT_PATHS
Starting .bin Installation Programs in Silent Mode
When using a
.bin
installation file, follow these steps to start a silent-mode installation:- Log in to the target UNIX system.
- Create a
silent.xml
file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating asilent.xml
file, see Creating a silent.xml File for Silent-Mode Installation. - Go to the directory that contains the installation program.
- Launch the installation program by entering the following commands:
chmod a+x
file_name.bin
./
file_name.bin
-mode=silent -silent_xml=
path_to_silent.xml
In this command,file_name.bin
is the name of the installation file andpath_to_silent.xml
is the full path of thesilent.xml
file.Note:If you plan to install the Server Examples, you must include the following parameter in the installation command. Otherwise, the installation may take longer than expected.-Djava.security.egd=file:/dev/./urandom
An installer window is displayed, indicating that the files are being extracted. No other prompt or text is displayed.
Starting .jar installation programs in Silent Mode
When using a
.jar
installation file, follow these steps to start a silent mode installation.Notes:
If you are installing WebLogic Server on a 64-bit platform, see Installing WebLogic Server on 64-Bit Platforms Using 64-Bit JDK, for more information.When you run the Generic Upgrade installer, include the
-Xmx
size
[g|G|m|M|k|K]
option in the command to ensure that the heap size is adequate.If you are installing WebLogic Server on a UNIX or Linux operating system, you must include the following parameter in the installation command if you plan to install the Server Examples. Otherwise, the installation may take longer than expected.
-Djava.security.egd=file:/dev/./urandom
- Log in to the target system.
- Create a
silent.xml
file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For information about creating asilent.xml
file, see Creating a silent.xml File for Silent-Mode Installation. - Add the directory of the appropriate JDK to the
PATH
variable definition on the target system. For example, on UNIX or Linux systems, add thebin
directory to the beginning of thePATH
variable:PATH=$JAVA_HOME/bin:$PATH; export PATH
- Go to the directory that contains the installation file.
- Launch the installation by entering the following command:
java -jar
file_name
.jar -mode=silent -silent_xml=
path_to_silent.xml
In this command,file_name
.jar
is the name of the installation file andpath_to_silent.xml
is the full path to thesilent.xml
file.An Installer window is displayed, indicating that the files are being extracted.
Installing WebLogic Server on 64-Bit Platforms Using 64-Bit JDK
If you are installing WebLogic Server on a 64-bit platform using a
.jar
installation program:- Add the directory of the appropriate JDK to the
PATH
variable definition on the target system. For example, on UNIX, add thebin
directory of the appropriate 64-bit JDK to the beginning of thePATH
variable definition on the target system:JAVA_HOME=
path_to_64-bit_JDK
; export JAVA_HOME
PATH=$JAVA_HOME/bin:$PATH; export PATH
- (UNIX or Linux only) Include the
-d64
flag in the installation command when using a 32/64-bit hybrid JDK (such as for the HP-PA, HPIA, and Solaris64 platforms). For example, if installing in graphical mode using the Package installer:java -d64 -jar
filename
.jar
-mode=silent -silent_xml=
path_to_silent.xml
- Execute the
java -version
command (orjava -d64 -version
command on UNIX or Linux platforms using a 32/64-bit hybrid JDK) to ensure that yourJAVA_HOME
refers to a 64-bit JDK. - If you are using the Sun 64-bit JDK, use the following command to install WebLogic Server:
java -Xmx1024m -jar
filename
.jar
-mode=silent -silent_xml=
path_to_silent.xml
Exit Codes for Silent Mode Installation
When run in silent mode, the installation program generates exit codes that indicate the success or failure of the installation.
Table 5-2 shows the exit codes.
Table 5-2 Exit Codes for Silent Mode Installation
Exit Code | Description |
---|---|
0 | Installation completed successfully |
-1 | Installation failed due to a fatal error |
-2 | Installation failed due to an internal XML parsing error |
If you launch the silent-mode installation process from a script, you can choose to have these exit codes displayed on the console.
Example 5-1 provides a sample command file that invokes the installation program in silent mode and echoes the exit codes to the console from which the script is executed.
Example 5-1 Sample Command File Displaying Silent-Mode Exit Codes
Sample silent.xml File for Silent Mode Installation
The following sample
silent.xml
file installs all default components of WebLogic Server, the optional Server Examples sub-component of WebLogic Server, and the Product Files component of Coherence.Note:
The Evaluation Database component is automatically installed if the Server Examples component is included in silent.xml
. Therefore, it does not have to be explicitly included in silent.xml
. If, however, you do not install the Server Examples, but you want to install the Evaluation Database, you must include WebLogic Server/Evaluation Database
![Comodo Silent Installation Switches Comodo Silent Installation Switches](/uploads/1/2/5/6/125608629/660815942.png)
silent.xml
.Running the Upgrade Installer in Silent Mode
The process for upgrading an installation in silent mode is similar to the process for a full installation in silent mode, except that the
silent.xml
file is much simpler. Please note the following issues when performing an upgrade in silent mode:- If you created a
silent.xml
file when you initially installed WebLogic Server, you should store it in a safe location or make a backup copy of it so that you do not accidentally overwrite it with thesilent.xml
file you are creating for your upgrade installation. Alternatively, you can name your upgrade file using a different file name, for examplesilent_upgrade.xml
. - Incorrect entries in
silent.xml
can cause installation failures. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation. See Generating a Verbose Installation Log. - When using an Upgrade installer to upgrade an existing WebLogic Server installation on Linux or UNIX operating systems, you must run the Upgrade installer using the same user ID as was used to perform the initial WebLogic Server installation.
- If you are upgrading an existing WebLogic Server 10.3.0, 10.3.1, 10.3.2, or 10.3.3 installation that includes Workshop for WebLogic, you must uninstall the Workshop components before upgrading your software. You must use either GUI mode or console mode to remove the Workshop components. See Uninstalling the Software, for more information.If you do not remove Workshop prior to running the Upgrade installer, you can remove it after the upgrade only by reverting to the previous installation and running the WebLogic uninstall program to remove the WebLogic components. WebLogic Server 10.3.5 does not support removal of Workshop components.
To run the Upgrade installer in silent mode:
- Create a
silent.xml
file (orsilent_upgrade.xml
file) to specify the Middleware home directory that contains the WebLogic Server installation you want to upgrade. See the sample in Sample silent.xml File for Upgrade Installation. - Save the XML file in the directory in which the Upgrade installer is stored.
- Start the Upgrade installer as described in one of the following sections:Make sure that the
-silent_xml
option points to the XML file you created for the upgrade installation. - After the installation completes, if you are using the JRockit SDK, Oracle recommends that you upgrade your domains to use the latest production version. See Configuring Domains to Use the Latest Version of JRockit.
Sample silent.xml File for Upgrade Installation
When using an Upgrade installer, the
silent.xml
file needs to define only the BEAHOME
data value name. This is the Middleware home directory that contains the WebLogic Server installation you want to upgrade. See the following example, where C:OracleMiddleware
is the Middleware home directory where WebLogic Server is installed. Update this value to the appropriate directory for your installation.