A Silent and Non-Interactive Installation

This appendix describes how to install Oracle Application Server in silent mode. This appendix contains the following topics:

Section A.1, "Silent Installation"
Section A.2, "Non-Interactive Installation"
Section A.3, "Pre-Installation"
Section A.4, "Create the Response File"
Section A.5, "Start the Installation"
Section A.6, "Post-Installation"
Section A.7, "Security Tips for Silent and Non-Interactive Installations"
Section A.8, "Deinstallation"

A.1 Silent Installation

Silent installation eliminates the need to monitor the Oracle Application Server installation because there is no graphical output and no input by the user.

You can perform a silent installation of Oracle Application Server by supplying a response file in the Oracle Universal Installer and specifying 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.

Use silent installation of Oracle Application Server when there are similar installations on more than one computer. In addition, use silent installation when performing the Oracle Application Server installation from a remote location using the command line.

A.2 Non-Interactive Installation

Non-interactive installations also use a response file to automate the Oracle Application Server installation. In non-interactive installations, there is graphical output and a user may enter input.

Non-interactive installation of Oracle Application Server is also accomplished by supplying the Oracle Universal Installer with a response file but without specifying the -silent flag on the command line. If you have not provided responses to all of the installer prompts, then you need to enter information during the installation.

Use non-interactive installation of Oracle Application Server when there are specific screens you want to observe during installation.

A.3 Pre-Installation

If the oraInst.loc file does not exist in the /var/opt/oracle directory for HP-UX or in the /etc directory for Linux, you must create it before starting the silent and non-interactive installation of Oracle Application Server. 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 /var/opt/oracle directory for HP-UX and in the /etc directory for Linux. Enter the following line in the file:
```
inventory_loc=oui_inventory_directory
```
Replace oui_inventory_directory with the full path to the directory where you want the installer to create the inventory directory. Make sure that the oinstall operating system group has write permissions to this directory. For example:
```
inventory_loc=/opt/oracle/oraInventory
```
Make sure that the oinstall operating system group has write permissions to this directory. For more information about the inventory directory and the group that owns it, see Section 2.5.1, "Create a Group for the Inventory Directory".
Create an empty /etc/oratab file.
```
# touch /etc/oratab
```
Exit from the root user.
```
# exit
```

A.4 Create the Response File

Before doing a silent or non-interactive 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.

This section contains the following topics:

Creating Response Files from Templates
Creating Response Files by Using the Record Mode in the Installer
Example Response File

A.4.1 Creating Response Files from Templates

Templates for response files are available in the stage/Response directory on Disk 1 of the Oracle Application Server CD-ROM. The Response file template available for the J2EE and Web Cache installation types is as follows:

oracle.iappserver.iapptop.Core.rsp

Refer to the template file for descriptions of the parameters in the file.

Note:

For Boolean parameters, specify either true or false.

A.4.2 Creating Response Files by Using the Record Mode in the Installer

You can run the installer in record mode to save your inputs to a file that you can use later as a response file. This feature is useful if you need to perform the same installation on different computers.

To run the installer in record mode:

Start up the installer with the -record and -destinationFile parameters.
```
prompt> /path/to/runInstaller -record -destinationFile newResponseFile
```
Replace newResponseFile with the full path to the response file that you want the installer to create. Example: /opt/oracle/myResponse.rsp.
Enter your values in the installer screens. The installer will write these values to the file specified in the -destinationFile parameter.

When you get to the Summary screen, the installer automatically writes all your values to the specified file. At this point, you can complete the installation on this computer, or you can exit without performing the installation.

Secure information such as passwords, is not written to the file, so you must modify the response file before you can use it.

Modify the following parameters:

ACCEPT_LICENSE_AGREEMENT=true
oracle.iappserver.instance:szl_InstanceInformation={"instancename", "instancepassword", "instancepassword"}
PreReqConfigSelections=""
nValidationRepositoryHost=0
nValidationRepository=0
nValidationStartProcPortals=0
nValidationStartProcBusiness=0
nValidationClusterSupport=0
nValidationStartProcCore=0
nValidationClusterRepository=0
oracle.iappserver.instance:nValidationInstanceInfo=0
silent=true

oracle.iappserver.iapptop:startupProcesses=""
oracle.iappserver.iapptop:SHOW_IAS_COMPONENT_CONFIG_PAGE=false
oracle.iappserver.iapptop:n_ValidationPreReqConfigSelections=0
oracle.iappserver.iapptop:nValidationPortListSelect=0
oracle.iappserver.iapptop:nValidationOID2=0
oracle.iappserver.iapptop:nValidationInstanceInfo=0
oracle.iappserver.iapptop:nValidationOID=0

Refer to the generated response file for descriptions of the parameters in the file.

A.4.3 Example Response File

The following section describes a sample response file for the Oracle Application Server J2EE and Web Cache installation type.

Note:

Ensure that you read the description of each parameter=value in the provided sample file, and edit its value accordingly for your environment.

A.4.3.1 Example Response File for Standalone J2EE and Web Cache

The following is an example of a response file for a silent installation of standalone instance of J2EE and Web Cache as described in Section 4.2, "Installing Oracle Application Server".

Note:

If you do not copy the CD-ROMs to the hard drive, then the installer will prompt you to switch CD-ROMs during installation. To complete the installation without any prompting, you must copy the contents of the CD-ROMs to the hard drive and specify the LOCATION_FOR_DISKn parameters.

RESPONSEFILE_VERSION=2.2.1.0.0
UNIX_GROUP_NAME=<Value Unspecified>
FROM_LOCATION="../stage/products.xml"
FROM_LOCATION_CD_LABEL=<Value Unspecified>
NEXT_SESSION_RESPONSE=<Value Unspecified>
ORACLE_HOME=<Value Required>
ORACLE_HOME_NAME="OHOME1"
TOPLEVEL_COMPONENT={"oracle.iappserver.iapptop","10.1.2.0.0"}
DEINSTALL_LIST={"oracle.iappserver.iapptop","10.1.2.0.0"}
SHOW_SPLASH_SCREEN=true
SHOW_WELCOME_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_SUMMARY_PAGE=true
SHOW_INSTALL_PROGRESS_PAGE=true
SHOW_REQUIRED_CONFIG_TOOL_PAGE=true
SHOW_CONFIG_TOOL_PAGE=true
SHOW_XML_PREREQ_PAGE=true
SHOW_RELEASE_NOTES=true
SHOW_END_OF_INSTALL_MSGS=true
SHOW_ROOTSH_CONFIRMATION=true
SHOW_END_SESSION_PAGE=true
SHOW_EXIT_CONFIRMATION=true
NEXT_SESSION=true
NEXT_SESSION_ON_FAIL=true
SHOW_DEINSTALL_CONFIRMATION=true
SHOW_DEINSTALL_PROGRESS=true
ACCEPT_LICENSE_AGREEMENT=true
RESTART_SYSTEM=<Value Unspecified>
CLUSTER_NODES=<Value Unspecified>
OUI_HOSTNAME=<Value Unspecified>
REMOVE_HOMES=<Value Unspecified>
COMPONENT_LANGUAGES={"en"}
oracle.sysman.agent:DEPENDENCY_LIST={ "oracle.assistants.emcf:10.1.0.2.0" }
oracle.logloader:DEPENDENCY_LIST={ "oracle.opmn:10.1.2.0.0" }
oracle.iappserver.iapptop:OPTIONAL_CONFIG_TOOLS=<Value Unspecified>
oracle.networking.netca:OPTIONAL_CONFIG_TOOLS=<Value Unspecified>
szl_RepositoryUserInput=<Value Unspecified>
szl_PortListSelect=<Value Unspecified>
oracle.iappserver.iapptop:szl_InstanceInformation=<Value Unspecified>
oracle.iappserver.instance:szl_InstanceInformation=<Value Unspecified>
szl_ClusterRepository=<Value Unspecified>
szlSpecifyRepositoryID=<Value Unspecified>
szlSpecifyRepositoryCluster=<Value Unspecified>
szlSpecifyOIDLogin=<Value Unspecified>
szOIDwithSSLStatus=<Value Unspecified>
startupProcesses=<Value Unspecified>
n_farmRepository=<Value Unspecified>
mailServerName=<Value Unspecified>
b_securityAccess=<Value Unspecified>
b_reportsStartup=<Value Unspecified>
b_formsStartup=<Value Unspecified>
b_configureWireless=<Value Unspecified>
b_configurePortal=<Value Unspecified>
b_configurePersonalization=<Value Unspecified>
b_configureJazn=<Value Unspecified>
b_configureDisco=<Value Unspecified>
b_configureCalypso=<Value Unspecified>
b_clusterSupport=<Value Unspecified>
b_FileBasedClustering=<Value Unspecified>
b_FarmRepository=<Value Unspecified>
SHOW_IAS_COMPONENT_CONFIG_PAGE=<Value Unspecified>
PreReqConfigSelections=<Value Unspecified>
OIDport=<Value Unspecified>
OIDhost=<Value Unspecified>
nValidationRepositoryHost=<Value Unspecified>
nValidationRepository=<Value Unspecified>
n_ValidationPreReqConfigSelections=<Value Unspecified>
nValidationStartProcPortals=<Value Unspecified>
nValidationStartProcBusiness=<Value Unspecified>
nValidationClusterSupport=<Value Unspecified>
nValidationStartProcCore=<Value Unspecified>
nValidationPortListSelect=<Value Unspecified>
nValidationClusterRepository=<Value Unspecified>
nValidationOID2=<Value Unspecified>
oracle.iappserver.iapptop:nValidationInstanceInfo=<Value Unspecified>
oracle.iappserver.instance:nValidationInstanceInfo=<Value Unspecified>
nValidationOID=<Value Unspecified>
s_groupid=<Value Unspecified>
s_group=<Value Unspecified>

A.5 Start the Installation

To make the installer use the response file, specify the location of the response file that you want to use as a parameter when starting the installer.

To perform a non-interactive installation:

prompt> setenv DISPLAY hostname:0.0
prompt> runInstaller -responseFile absolute_path_and_filename

To perform a silent installation, use the -silent parameter:

prompt> runInstaller -silent -responseFile absolute_path_and_filename

A.6 Post-Installation

The success or failure of the non-interactive and silent installations is logged in the installActions<time_stamp>.log file. Additionally, the silent installation creates the silentInstall<time_stamp>.log file. The log files are created in the oraInventory directory.

The silentInstall<time_stamp>.log file contains the following line if the installation was successful:

The installation of OracleAS <Installation Type> was successful.

The installActions<time_stamp>.log file contains specific information for each Oracle Application Server installation type.

A.7 Security Tips for Silent and Non-Interactive Installations

One of the pieces of information in the response file is the installation password. The password information is in clear text.

To minimize security issues regarding the password in the response file, adhere to the following 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 or non-interactive installation.
If possible, remove the response files from the system after the silent or non-interactive installation is completed.

A.8 Deinstallation

You can perform a silent deinstallation of Oracle Application Server by supplying a silent deinstallation parameter to the response file that you used for installation.

Add the following parameter to your installation response file:

REMOVE_HOMES={"<ORACLE_HOME to be removed>"}

For example:

REMOVE_HOME="/local_location/oracle_home"

Note:

You still need to follow the deinstallation steps described in Appendix D, "Deinstallation and Reinstallation". One of the key steps is to run the deconfig tool before running the silent deinstallation command. The silent deinstallation command only replaces the step where you run the installer interactively to deinstall the instance.

To perform a silent deinstallation, use the -deinstall parameter as follows:

prompt> runInstaller -silent -deinstall -responseFile absolute_path_and_filename