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.

If this is a first time installation of Oracle Application Server, then you must create the registry keys before starting. For details about creating a registry key, refer to Section A.3, "Pre-Installation".

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.

If this is a first time installation of Oracle Application Server, then you must create the registry keys before starting. For details about creating a registry key, refer to Section A.3, "Pre-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 you have not installed Oracle Application Server on your computer, then you need to create the following Registry key and value:

HKEY_LOCAL_MACHINE/SOFTWARE/Oracle/inst_loc = Inventory_Directory

The Inventory_Directory is the full path to your installer files. For example:

C:\Program Files\Oracle\Inventory

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:

1. Start the installer with the -record and -destinationFile parameters.

   E:\> setup.exe -record -destinationFile newResponseFile
   
   

   Replace newResponseFile with the full path to the response file that you want the installer to create. For example, C:\myWebCacheResponse.rsp.

2. Enter the 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.

For all installations, 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

For Middle Tier installations, modify the following parameters:

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=" "
FROM_LOCATION="E:\Disk1\stage\products.xml"
FROM_LOCATION_CD_LABEL="Oracle Application Server 10G"
LOCATION_FOR_DISK2="C:\path\to\disk2\files"
LOCATION_FOR_DISK3="C:\path\to\disk3\files"
ORACLE_HOME="C:\oracle\ora_j2ee"
ORACLE_HOME_NAME="oracle_j2eehome_name"
TOPLEVEL_COMPONENT={"oracle.iappserver.iapptop","10.1.2.0.0"}
SHOW_SPLASH_SCREEN=false
SHOW_WELCOME_PAGE=false
SHOW_CUSTOM_TREE_PAGE=false
SHOW_COMPONENT_LOCATIONS_PAGE=false
SHOW_SUMMARY_PAGE=false
SHOW_INSTALL_PROGRESS_PAGE=false
SHOW_REQUIRED_CONFIG_TOOL_PAGE=false
SHOW_CONFIG_TOOL_PAGE=false
SHOW_RELEASE_NOTES=true
SHOW_ROOTSH_CONFIRMATION=false
SHOW_END_SESSION_PAGE=false
SHOW_EXIT_CONFIRMATION=false
NEXT_SESSION=false
NEXT_SESSION_ON_FAIL=false
DEINSTALL_LIST={"oracle.iappserver.iapptop","10.1.2.0.0"}
SHOW_DEINSTALL_CONFIRMATION=false
SHOW_DEINSTALL_PROGRESS=true
CLUSTER_NODES={}
ACCEPT_LICENSE_AGREEMENT=true
SELECTED_LANGUAGES={"en"}
INSTALL_TYPE="J2EE and Web Cache"
oracle.iappserver.iapptop:OPTIONAL_CONFIG_TOOLS="{}"
oracle.iappserver.infrastructure:OPTIONAL_CONFIG_TOOLS="{}"
oracle.iappserver.devcorner:OPTIONAL_CONFIG_TOOLS="{}"
oracle.sysman.server:OPTIONAL_CONFIG_TOOLS="{}"
oracle.rdbms.sqlplus.isqlplus:OPTIONAL_CONFIG_TOOLS="{}"
oracle.options.ops.csscommon:OPTIONAL_CONFIG_TOOLS="{}"
oracle.networking.netca:OPTIONAL_CONFIG_TOOLS="{}"
oracle.options.ops.vipca:OPTIONAL_CONFIG_TOOLS="{}"
oracle.iappserver.iapptop:szl_PortListSelect={"YES","C:\oracle\mystaticports.ini"}
oracle.iappserver.instance:szl_InstanceInformation={"j2ee_10_1_2", "password1", "password1"}
oracle.iappserver.iapptop:szOIDwithSSLStatus="N"
oracle.iappserver.iapptop:startupProcesses=""
n_farmRepository=0
mailServerName=""
b_securityAccess=false
b_reportsStartup=false
b_formsStartup=false
b_configureWireless=false
b_configurePortal=false
b_configurePersonalization=false
b_configureJazn=true
b_configureDisco=false
b_configureCalypso=true
b_clusterSupport=false
b_FileBasedClustering=false
b_FarmRepository=false
oracle.iappserver.iapptop:SHOW_IAS_COMPONENT_CONFIG_PAGE=false
PreReqConfigSelections=""
oracle.iappserver.iapptop:OIDport="389"
oracle.iappserver.iapptop:OIDhost=""
nValidationRepositoryHost=0
oracle.iappserver.iapptop:n_ValidationPreReqConfigSelections=0
nValidationStartProcPortals=0
nValidationStartProcBusiness=0
nValidationStartProcCore=0
oracle.iappserver.iapptop:nValidationPortListSelect=1
oracle.iappserver.iapptop:nValidationOID2=0
oracle.iappserver.iappdialog:nValidationOID2=0
oracle.iappserver.instance:nValidationInstanceInfo=0
oracle.java.jdbc.thin12:PROD_HOME="C:\oracle\ora_j2ee\oracle_java_jdbc_thin12"
oracle.options.ano.ssl.owm:PROD_HOME="C:\oracle\ora_j2ee\oracle_options_ano_ssl_owm"
oracle.networking.netclt:PROD_HOME="C:\oracle\ora_j2ee\oracle.networking.netclt"
oracle.java.javavm.javatools:PROD_HOME="C:\oracle\ora_j2ee\oracle.java.javavm.javatools"
oracle.xml.xsql:PROD_HOME="C:\oracle\ora_j2ee\oracle_xml_xsql"
oracle.options.ano.ssl:PROD_HOME="C:\oracle\ora_j2ee\oracle_options_ano_ssl"
oracle.networking.netmgr:PROD_HOME="C:\oracle\ora_j2ee\oracle.networking.netmgr"
oracle.networking.netca:PROD_HOME="C:\oracle\ora_j2ee\oracle_networking_netca"
oracle.assistants.acf:PROD_HOME="C:\oracle\ora_j2ee\oracle.assistants.acf"
oracle.assistants.emcf:PROD_HOME="C:\oracle\ora_j2ee\oracle.assistants.emcf"
oracle.install.instcommon:PROD_HOME="C:\oracle\ora_j2ee\oracle_install_instcommon"
oracle.rdbms.sqlplus:PROD_HOME="C:\oracle\ora_j2ee\oracle.rdbms.sqlplus"
oracle.rsf.net_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_net_rsf"
oracle.rdbms.aqapi:PROD_HOME="C:\oracle\ora_j2ee\oracle_rdbms_aqapi"
oracle.rdbms.xml.xsu:PROD_HOME="C:\oracle\ora_j2ee\oracle_rdbms_xml_xsu"
oracle.java.jdbc.thin14:PROD_HOME="C:\oracle\ora_j2ee\oracle_java_jdbc_thin14"
oracle.java.jdbc.oci_common:PROD_HOME="C:\oracle\ora_j2ee\oracle_java_jdbc_oci_common"
oracle.rsf.ssl_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_ssl_rsf"
oracle.rsf.nlsrtl_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_nlsrtl_rsf"
oracle.rsf.nlsrtl_rsf.lbuilder:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_nlsrtl_rsf"
oracle.rsf.ssl_rsf.sslrsf_ic:PROD_HOME="C:\oracle\ora_j2ee\oracle.rsf.ssl_rsf.sslrsf_ic"
oracle.xml.classgen.java:PROD_HOME="C:\oracle\ora_j2ee\oracle_xml_classgen_java"
oracle.options.ops.opscf:PROD_HOME="C:\oracle\ora_j2ee\oracle.options.ops.opscf"
oracle.java.jdbc.jdbc_common:PROD_HOME="C:\oracle\ora_j2ee\oracle_java_jdbc_jdbc_common"
oracle.rsf.plsql_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_plsql_rsf"
oracle.rsf.precomp_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_precomp_rsf"
oracle.rsf.slax_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_slax_rsf"
oracle.rsf.agent_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_agent_rsf_agent_rsf_cmp"
oracle.rsf.clntsh_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_clntsh_rsf_clntsh_rsf_cmp"
oracle.rsf.rdbms_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_rdbms_rsf"
oracle.rsf.has_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_has_rsf"
oracle.java.jdbc.thin14.thin14_ic:PROD_HOME="C:\oracle\ora_j2ee\oracle_java_jdbc_thin14"
oracle.rsf.rdbms_rsf.rdbms_rsf_ic:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_rdbms_rsf_rdbms_rsf_ic"
oracle.rsf.xdk_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_rdbms_rsf"
oracle.rsf.dbjava_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_dbjava_rsf"
oracle.rsf.ops_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_net_rsf"
oracle.xml.parser.java:PROD_HOME="C:\oracle\ora_j2ee\oracle.xml.parser.java"
oracle.java.jdbc.oci_common.ocicommon_ic:PROD_HOME="C:\oracle\ora_j2ee\oracle.java.jdbc.oci_common.ocicommon_ic"
oracle.rsf.oracore_rsf:PROD_HOME="C:\oracle\ora_j2ee\oracle_rsf_oracore_rsf"
silent=true

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, use the following command:

E:\> setup.exe -responseFile absolute_path_and_filename

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

E:\> setup.exe -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.log file. In addition, the silent installation creates the silentInstall.log file. The log files are created in the C:\Program Files\Oracle\Inventory\oui_inventory\Logs directory.

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

The installation of OracleAS <Installation Type> was successful.

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

See Also: Appendix E, "Configuration Assistants"

Note: Application Server Control Configuration Assistant and DCM Repository Backup Assistant success messages appear for first time installation of Oracle Application Server.

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="C:\oracle\ora_j2ee"

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:

E:\> setup.exe -silent -deinstall -responseFile absolute_path_and_filename