C Silent Installation and Deinstallation

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

Section C.1, "About Silent Installation and Deinstallation"
Section C.2, "Oracle SOA Suite Response Files"

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

C.2 Oracle SOA Suite Response Files

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.

C.2.1 Installation Response Files

A sample response file called sampleResponse_wls.rsp (see Section C.2.1.1, "Contents of the sampleResponse_wls.rps File") is provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory in the location where you unzipped your downloaded archive file for installation. This template response file can be used to install the Oracle SOA Suite software if you are using Oracle WebLogic Server as the application server. If you are using IBM WebSphere as your application server, you need to use the sampleResponse_was.rsp file (see Section C.2.1.2, "Contents of the sampleResponse_was.rsp File").

In either case, you will still need to run the Configuration Wizard after installation to create or extend your WebLogic domain and configure Oracle SOA Suite products.

C.2.1.1 Contents of the sampleResponse_wls.rps File

Below are the contents of the sampleResponse_wls.rsp file:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Set this to true if you wish to specify a directory where latest updates are downloaded. This option would use the software updates from the specified directory
SPECIFY_DOWNLOAD_LOCATION=false
 
#
SKIP_SOFTWARE_UPDATES=true
 
#If the Software updates are already downloaded and available on your local system, then specify the path to the directory where these patches are available and set SPECIFY_DOWNLOAD_LOCATION to true
SOFTWARE_UPDATES_DOWNLOAD_LOCATION=
 
#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 SOA Oracle Home.
ORACLE_HOME=/home/middleware/Oracle_SOA1
 
#Provide existing Middleware Home location.
MIDDLEWARE_HOME=/home/middleware
 
#Application Server choices are WLS, WAS, JBoss
APPSERVER_TYPE=WLS
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS
]

The parameters you should change in this file are:

SKIP_SOFTWARE_UPDATES. Set this to true if you do not want to configure your system to receive software updates. If you do, then set this parameter to false. Set the SPECIFY_DOWNLOAD_LOCATION parameter to true if you want to specify a directory where the latest updates are downloaded, then specify this location with the SOFTWARE_UPDATES_DOWNLOAD_LOCATION parameter.
ORACLE_HOME. Specify the full path to your Oracle home directory.
MIDDLEWARE_HOME. Specify the full path to your Middleware home directory.

C.2.1.2 Contents of the sampleResponse_was.rsp File

Below are the contents of the sampleResponse_was.rsp file:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Set this to true if you wish to specify a directory where latest updates are downloaded. This option would use the software updates from the specified directory
SPECIFY_DOWNLOAD_LOCATION=false
 
#
SKIP_SOFTWARE_UPDATES=true
 
#If the Software updates are already downloaded and available on your local system, then specify the path to the directory where these patches are available and set SPECIFY_DOWNLOAD_LOCATION to true
SOFTWARE_UPDATES_DOWNLOAD_LOCATION=
 
#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 SOA Oracle Home.
ORACLE_HOME=/home/middleware/Oracle_SOA1
 
#Provide Middleware Home location.
MIDDLEWARE_HOME=/home/middleware
 
#Application Server choices are WLS, WAS, JBoss
APPSERVER_TYPE=WAS
 
#Application Server Location to be specified for WAS and JBoss.
APPSERVER_LOCATION=/home/wasinstall
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS
]

The parameters you should change in this file are:

SKIP_SOFTWARE_UPDATES. Set this to true if you do not want to configure your system to receive software updates. If you do, then set this parameter to false. Set the SPECIFY_DOWNLOAD_LOCATION parameter to true if you want to specify a directory where the latest updates are downloaded, then specify this location with the SOFTWARE_UPDATES_DOWNLOAD_LOCATION parameter.
ORACLE_HOME. Specify the full path to your Oracle home directory.
MIDDLEWARE_HOME. Specify the full path to your Middleware home directory. Remember that this directory must be specified even if you are not using Oracle WebLogic Server as your application server.
APPSERVER_LOCATION. Specify the installation directory for your IBM WebSphere application server.

C.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 in the location where you downloaded and unzipped your archive file for installation. This template response file can be used to deinstall a SOA 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]