Skip Headers
Oracle® Fusion Middleware Installation Guide for Oracle Service Bus
11g Release 1 (11.1.1.6.0)

Part Number E15017-04
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

4 Silent Installation and Deinstallation

This appendix contains information you need to know to perform a silent installation or deinstallation of Oracle Service Bus.

4.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 and response files, refer to "Silent Installation and Deinstallation" in Oracle Fusion Middleware Installation Planning Guide.

4.2 Using the Oracle Service Bus Response Files

Before doing a silent installation or deinstallation, you must provide information specific to your installation or deinstallation 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

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.

To create a response file for silent deinstallation, repeat the same procedure by clicking Save on the Deinstall Oracle Home screen.

Response file templates for Oracle Service Bus 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.1, "Obtaining the Software"):

4.2.1 Using the Installation Response Files for Oracle Service Bus

Table 4-1 lists the installation response files provided for Oracle Service Bus:

Table 4-1 Oracle Service Bus Installation Response File Templates

Template Description

custom_installtype.rsp

This is the template response file that should be used if you want to customize the products installed on your system. For example, if you want to perform a silent installation and exclude OEPE (thereby not installing Oracle Service Bus IDE) then you would use this template.

The equivalent using the GUI would be to run the installer and select Custom on the Installation Type screen. In the response file, you must specify which products you want to install.

See Section 4.2.1.1, "Using the custom_installtype.rsp Response File Template" for more information.

typical_installtype.rsp

This is the template response file that should be used if you want to install all Oracle Service Bus products on your system. You will not have the option to exclude any products from being installed.

The equivalent using the GUI would be to run the installer and select Typical on the Installation Type screen. All Oracle Service Bus products will be installed.

See Section 4.2.1.2, "Using the typical_installtype.rsp Response File Template" for more information.


In addition to these pre-existing response files, you can create your own response file by running the deinstaller 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.

4.2.1.1 Using the custom_installtype.rsp Response File Template

Table 4-2 describes the parameters found in the custom_installtype.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 4-2 Parameters in the custom_installtype.rsp Response File

Corresponding SCreen Parameter Description

Install Software Updates

SPECIFY_DOWNLOAD_LOCATION

SOFTWARE_UPDATES_DOWNLOAD_LOCATION

Set the SPECIFY_DOWNLOAD_LOCATION parameter to 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 this parameter to true if you do not want the installer to check for software updates.

Installation Location

ORACLE_HOME

Specify the full path to the location of your Oracle home directory.

MIDDLEWARE_HOME

Specify the full path to the location of your Middleware home directory.

Installation Type

TYPICAL TYPE

CUSTOM TYPE

Set CUSTOM TYPE=true and TYPICAL TYPE=false to perform a silent custom installation.

Components to Install

Oracle Service Bus Examples

Oracle Service Bus IDE

Set Oracle Service Bus Examples=true if you want to install the Oracle Service Bus examples. If not, set this parameter to false.

Set Oracle Service Bus IDE=true if you want to install the Oracle Service Bus IDE. If not, set this parameter to false.

Product Home Location

WL_HOME

Specify the full path to your WebLogic Server home directory. The default is the wlserver_10.3 directory inside the Middleware home.

OEPE_HOME

If you are installing Oracle Service Bus IDE, you must specify the full path to the directory where OEPE is installed. By default, this directory under your Middleware home is named oepe_11.1.1.8.0


4.2.1.2 Using the typical_installtype.rsp Response File Template

Table 4-3 describes the parameters found in the typical_installtype.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 4-3 Parameters in the typical_installtype.rsp Response File

Corresponding SCreen Parameter Description

Install Software Updates

SPECIFY_DOWNLOAD_LOCATION

SOFTWARE_UPDATES_DOWNLOAD_LOCATION

Set the SPECIFY_DOWNLOAD_LOCATION parameter to 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 this parameter to true if you do not want the installer to check for software updates.

Installation Location

ORACLE_HOME

Specify the full path to the location of your Oracle home directory.

MIDDLEWARE_HOME

Specify the full path to the location of your Middleware home directory.

Installation Type

TYPICAL TYPE

CUSTOM TYPE

Set CUSTOM TYPE=false and TYPICAL TYPE=true to perform a silent typical installation.

Product Home Location

WL_HOME

Specify the full path to your WebLogic Server home directory. The default is the wlserver_10.3 directory inside the Middleware home.

OEPE_HOME

Specify the full path to the directory where OEPE is installed. By default, this directory under your Middleware home is named oepe_11.1.1.8.0


4.2.2 Using the Deinstallation Response File for Oracle Service Bus

The deinstall_oh.rsp response 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.