4 Silent Installation and Deinstallation

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

About Silent Installation and Deinstallation
Oracle Service Bus Response Files

4.1 About Silent Installation and Deinstallation

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

4.2 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.

4.2.1 Installation Response Files

Table 4-1 lists the installation response files provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory:

Table 4-1 Oracle Service Bus Installation Response File Templates

Template Description

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. 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, "Contents of the custom_installtype.rsp Response File" to view the contents of this file.
`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. 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, "Contents of the typical_installtype.rsp Response File" to view the contents of this file.

custom_installtype.rsp

This is the template response file that should be used if you want to customize the products installed on your system.

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, "Contents of the custom_installtype.rsp Response File" to view the contents of this file.

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.

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, "Contents of the typical_installtype.rsp Response File" to view the contents of this file.

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 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 Contents of the custom_installtype.rsp Response File

This section shows the contents of the Disk1/stage/Response/custom_installtype.rsp response file on a UNIX operating system:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Set this to true if typical installation must be done. If this is set to true then wariable "CUSTOM TYPE" must be set to false as the variables are mutually exclusive
TYPICAL TYPE=false

#Set this to true if custom installation must be done, all other required variables need to be provided. If this is set to true then variable "TYPICAL TYPE" must be set to false as the variables are mutually exclusive.
CUSTOM TYPE=true

#Set this to true if component Oracle Service Bus Examples must be installed. This input will be needed only in the case of custom installation
Oracle Service Bus Examples=true

#Set this to true if component Oracle Service Bus IDE must be installed. This input will be needed only in the case of custom installation
Oracle Service Bus IDE=true

#Provide the Oracle Home location. The location has to be the immediate child under the specified Middleware Home location. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. The total length has to be less than or equal to 128 characters. The location has to be an empty directory or a valid OSB Oracle Home.
ORACLE_HOME=

#Provide existing Middleware Home location.
MIDDLEWARE_HOME=

#Give the complete path to a valid WebLogic Server Home for the corresponding Middleware Home entered.
WL_HOME=

#Give the complete path to a valid OEPE Home for the corresponding Middleware Home entered. This input will be needed in both typical and custom installations. But in case of custom installation, Oracle Service Bus IDE must be set to true.
OEPE_HOME=

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

4.2.1.2 Contents of the typical_installtype.rsp Response File

This section shows the contents of the Disk1/stage/Response/typical_installtype.rsp response file on a UNIX operating system:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Set this to true if typical installation must be done. If this is set to true then wariable "CUSTOM TYPE" must be set to false as the variables are mutually exclusive
TYPICAL TYPE=true
 
#Set this to true if custom installation must be done, all other required variables need to be provided. If this is set to true then variable "TYPICAL TYPE" must be set to false as the variables are mutually exclusive.
CUSTOM TYPE=false
 
#Provide the Oracle Home location. The location has to be the immediate child under the specified Middleware Home location. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. The total length has to be less than or equal to 128 characters. The location has to be an empty directory or a valid OSB Oracle Home.
ORACLE_HOME=
 
#Provide existing Middleware Home location.
MIDDLEWARE_HOME=
 
#Give the complete path to a valid WebLogic Server Home for the corresponding Middleware Home entered.
WL_HOME=
 
#Give the complete path to a valid OEPE Home for the corresponding Middleware Home entered. This input will be needed in both typical and custom installations. But in case of custom installation, Oracle Service Bus IDE must be set to true.
OEPE_HOME=
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

4.2.2 Deinstallation Response Files

A sample deinstallation response file called deinstall_oh.rsp is provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory. This template response file can be used to deinstall your Oracle Service Bus Oracle home.

The contents of the deinstall_oh.rsp file are shown below:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Identifies if the Instance deinstallation is valid or not
DEINSTALL_IN_ASINSTANCE_MODE=false
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]