Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle WebCenter Portal
11g Release 1 (11.1.1.7.0)

Part Number E12001-12
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

C Silent Installation and Deinstallation

This appendix describes how to install and deinstall Oracle WebCenter Portal from the command line in silent mode. This appendix contains the following topics:

C.1 Understanding Silent Installation and Deinstallation

You can use the Oracle Universal Installer's silent installation mode to bypass the graphical user interface and supply the necessary information in a response file. This method is most useful when installing the same product multiple times on multiple hosts. By using a response file, you can automate the installation of a product for which you know the installation parameters.

For information about silent installation and deinstallation, refer to "Silent Installation and Deinstallation" in Oracle Fusion Middleware Installation Planning Guide.

C.2 Using the Oracle WebCenter Portal Response File Templates

Before doing a silent installation, you must provide information specific to your installation in a response file. A response file is a specification file containing information you normally fetch through the Oracle Universal Installer user interface during an interactive installation session. Each answer is stored as a value for a variable identified in the response file. For example, values for Oracle home or installation type can be set automatically within the response file. Response files are text files that you can create or edit in any text editor.

The installer will fail if you attempt an installation using a response file that is not configured correctly. Oracle recommends creating your response file by first running the install GUI, then clicking Save on the Installation Summary screen. 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.

Response file templates for Oracle WebCenter Portal are provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory where you unpacked the archive file (Section 2.2.1, "Obtaining the Software"):

C.2.1 Using the Oracle WebCenter Portal Silent Installation Response Files

Table C-1 lists the installation response file templates provided for Oracle WebCenter Portal:

Table C-1 Installation Response File Templates for Oracle WebCenter Portal

Template Description

sampleResponse_wls.rsp

Use this response file template to install Oracle SOA Suite using Oracle WebLogic Server as your application server. The equivalent using the GUI would be to run the installer and select WebLogic Server on the Application Server screen.

For more information, see Section C.2.1.1, "Using the sampleResponse_wls.rsp response File Template".

sampleResponse_was.rsp

Use this response file template to install Oracle SOA Suite using IBM WebSphere as your application server. The equivalent using the GUI would be to run the installer and select WebSphere on the Application Server screen.

For more information, see Section C.2.1.2, "Using the sampleResponse_was.rsp response File Template".


C.2.1.1 Using the sampleResponse_wls.rsp response File Template

Table C-2 describes the parameters found in the sampleResponse_wls.rsp response file template. The parameters are listed in the order in which they appear in the response file; note that they do not necessarily follow the order of the installation screens as seen in graphical mode.

Table C-2 Parameters in the sampleResponse_wls.rsp File

Corresponding Install Screen Parameter Description

Install Software Updates

SPECIFY_DOWNLOAD_LOCATION

SOFTWARE_UPDATES_DOWNLOAD_LOCATION

Set SPECIFY_DOWNLOAD_LOCATION=true if you want to specify the location where software updates can be downloaded.

Then, specify the directory on your local system that contains the updates using the SOFTWARE_UPDATES_DOWNLOAD_LOCATION parameter.

SKIP_SOFTWARE_UPDATES

Set SKIP_SOFTWARE_UPDATES=true if you do not want the installer to check for software updates.

Specify Installation Location

ORACLE_HOME

Specify the full path to your Oracle home directory.

MIDDLEWARE_HOME

Specify the full path to your Middleware home directory.

Application Server

APPSERVER_TYPE

Set APPSERVER_TYPE=WLS since you are using Oracle WebLogic Server as the application server.


C.2.1.2 Using the sampleResponse_was.rsp response File Template

Table C-3 describes the parameters found in the sampleResponse_was.rsp response file template. The parameters are listed in the order in which they appear in the response file; note that they do not necessarily follow the order of the installation screens as seen in graphical mode.

Table C-3 Parameters in the sampleResponse_was.rsp File

Corresponding Install Screen Parameter Description

Install Software Updates

SPECIFY_DOWNLOAD_LOCATION

SOFTWARE_UPDATES_DOWNLOAD_LOCATION

Set SPECIFY_DOWNLOAD_LOCATION=true if you want to specify the location where software updates can be downloaded.

Then, specify the directory on your local system that contains the updates using the SOFTWARE_UPDATES_DOWNLOAD_LOCATION parameter.

SKIP_SOFTWARE_UPDATES

Set SKIP_SOFTWARE_UPDATES=true if you do not want the installer to check for software updates.

Specify Installation Location

ORACLE_HOME

Specify the full path to your Oracle home directory.

MIDDLEWARE_HOME

Specify the full path to your Middleware home directory.

Application Server

APPSERVER_TYPE

Set APPSERVER_TYPE=WAS since you are using the IBM WebSphere application server.

APPSERVER_LOCATION

Specify the location of your IBM WebSphere application server.


C.2.2 Using the Oracle WebCenter Portal Silent Deinstallation Response File

The only response file template provided for deinstallation is called deinstall_oh.rsp. This file contains only a single parameter: DEINSTALL_IN_ASINSTANCE_MODE=false. This causes the deinstaller to not look for any Oracle instances to remove; instead, the deinstaller will remove the Oracle home from where it is started.