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

Part Number E14260-11
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

D Silent Installation and Deinstallation

This appendix describes how to install and remove Oracle Web Tier from the command line, in silent mode.

This appendix contains the following topics:

D.1 About Silent Installation and Deinstallation

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

D.2 Creating a WebLogic Domain in Silent Mode

Oracle Web Tier can be installed as described in Section 1.2, "Methods of Installation"; the Oracle Web Tier installer does not provide a mechanism for creating an Oracle WebLogic Server domain.

If you do not have a Fusion Middleware (EM) Control deployment on your system, use the procedure described in this section to create and enable a WebLogic Server domain which contains Oracle Java Required Files and Enterprise Manager.

After the domain is created, you can run the Web Tier installer in silent mode using the response files to associate your components with the domain.

D.2.1 Task 1: Install the Latest Oracle WebLogic Server in Silent Mode

See "Product Distribution" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server to obtain the latest software.

See "Running the Installation Program in Silent Mode" in the Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server to install Oracle WebLogic Server in silent mode.

D.2.2 Task 2: Install Oracle Web Tier in Silent Mode

Table D-1 lists the installation response files provided in the Disk1/stage/Response directory on UNIX, and Disk1\stage\Response directory on Windows, in which you downloaded and extracted the archive file. These response files are designed for use in situations where you are performing a new installation of Oracle Web Tier.

Table D-1 Oracle Web Tier Installation and Configuration Response File Templates

Template Description

WebTierInstallAndConfigure.rsp

This is the template response file that should be used if you want to install and configure Oracle Web Tier products in one step.

The equivalent using the GUI would be selecting Install and Configure option on the Select Installation Type Screen.

See Section D.2.2.1 to view the contents of this file.

WebTierSoftwareOnly.rsp

This is the template response file that should be used if you only want to install the software on your system. You must run the Configuration Tool (either from the command line or the GUI) later before you can begin to manage these products.

The equivalent using the GUI would be selecting Install Software - Do Not Configure option on the Select Installation Type Screen.

See Section D.2.2.2 to view the contents of this file.

You can configure later by running the template response file for configuration alone in Section D.3.1.


D.2.2.1 Contents of the WebTierInstallAndConfigure.rsp File

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

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Set this to true if installation and configuration need to be done, all other required variables need to be provided. Variable "INSTALL AND CONFIGURE LATER TYPE" must be set to false if this is set to true as the variables are mutually exclusive
INSTALL AND CONFIGURE TYPE=true
 
#Set this to true if only Software only installation need to be done. If this is set to true then variable "INSTALL AND CONFIGURE TYPE" must be set to false, since the variables are mutually exclusive.
INSTALL AND CONFIGURE LATER TYPE=false
 
#Provide the Oracle 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 Web Tier Oracle Home.
ORACLE_HOME=/oracle/product/11.1.1/as_1
 
#The name of the Oracle Instance. Instance name must begin with an alphabetic character, may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters and are 4 to 30 characters long.
INSTANCE_HOME=/oracle/product/11.1.1/as_1/instances/instance1
 
#Provide the Oracle Instance location. The Oracle Instance 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 or non existing directory.
INSTANCE_NAME=instance1
 
#If set to true, installer will auto assign ports
AUTOMATIC_PORT_DETECT=true
 
#This is required if "AUTOMATIC_PORT_DETECT" variable is set to false, absolute path of a staticports file location need to be provided with values for ports.\nThe template for staticports.ini can be found from Disk1/staget/Response directory of the shiphome.
STATICPORT INI FILE LOCATION=
 
 
[SYSTEM]
 
#Set true to create a new instance and configure Oracle Process Management Notification, else skip the configuration
CONFIGURE_OPMN=true
 
#Set true to configure Oracle HTTP Server, else skip Oracle HTTP Server configuration
CONFIGURE_OHS=true
 
#Set true to configure Oracle Web Cache, else skip Oracle Web Cache configuration
CONFIGURE_WEBCACHE=true
 
#The Oracle HTTP Server (OHS) component name (required only if CONFIGURE_OHS is set to true). OHS component name must begin with an alphabetic character, may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters and are 4 to 30 characters long.
OHS_COMPONENT_NAME=ohs1
 
#The Web Cache component name (required only if CONFIGURE_WEBCACHE is set to true). Web Cache component name must begin with an alphabetic character, may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters and are 4 to 30 characters long.
WEBCACHE_COMPONENT_NAME=webcache1
 
#Valid passwords are 5 to 30 characters long, must begin with an alphabetic character, use only alphanumeric, underscore (_), dollar ($) or pound (#) characters and include at least one number.
WEBCACHE_ADMINISTRATOR_PASSWORD=<SECURE VALUE>

#The confirmation password for Web Cache administrator.
WEBCACHE_ADMINISTRATOR_PASSWORD_CONFIRM=<SECURE VALUE>
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]
 
#If set to true, the instance and components will be registered with an existing weblogic server
ASSOCIATE_WEBTIER_WITH_DOMAIN=true
 
#Provide the exiting Middleware Home location. This is required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true.
MIDDLEWARE_HOME=/Oracle/Middleware
 
#Provide an existing domain host name. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_HOST_NAME=machinename.machinedomain
 
#Provide the existing domain port number. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_PORT_NO=7001
 
#Provide the domain user name. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_USER_NAME=weblogic
 
#The domain user password. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_USER_PASSWORD=<SECURE VALUE>

D.2.2.2 Contents of the WebTierSoftwareOnly.rsp File

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

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#Set this to true if installation and configuration need to be done, all other required variables need to be provided. Variable "INSTALL AND CONFIGURE LATER TYPE" must be set to false if this is set to true as the variables are mutually exclusive
INSTALL AND CONFIGURE TYPE=false
 
#Set this to true if only Software only installation need to be done. If this is set to true then variable "INSTALL AND CONFIGURE TYPE" must be set to false, since the variables are mutually exclusive.
INSTALL AND CONFIGURE LATER TYPE=true
 
#Provide the Oracle 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 Web Tier Oracle Home.
ORACLE_HOME=/oracle/product/11.1.1/as_1
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

D.2.3 Task 3: Create the WebLogic Server Domain Using WLST

Create a WLST script containing the following WLST commands to create the WebLogic Server domain:

#!/usr/bin/python
import os, sys
readTemplate('WebLogic_Server_Home/common/templates/domains/wls.jar')
cd('/Security/base_domain/User/admin_name')
cmo.setPassword('examplepassword')
cd('/Server/AdminServer')
cmo.setName('admin_server_name')
cmo.setListenPort(admin_server_port)
cmo.setListenAddress('admin_server_address')
writeDomain('DOMAIN_HOME')
closeTemplate()
exit()

For example, you could create a file called create_domain_7001.py that contained the following:

#!/usr/bin/python
import os, sys
readTemplate('/oracle/Middleware/wlserver_10.3/common/templates/domains/wls.jar')
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('ExamplePassword1')
cd('/Server/AdminServer')
cmo.setName('AdminServer')
cmo.setListenPort(7001)
cmo.setListenAddress('examplehost.exampledomain.com')
writeDomain('/oracle/Domains/ExampleSilentWTDomain')
closeTemplate()
exit()

To run the script:

  1. Set the environment

    cd WebLogic_Server_Home/common/bin
    ./commEnv.sh
    
  2. Run the script using WLST. For example:

    wlst path_to_script/create_domain_7001.py
    

D.2.4 Task 4: Enable the WebLogic Server Domain with JRF and EM

Create a second script containing the following WLST commands to enable the WebLogic Server domain with JRF and EM:

#!/usr/bin/python
import os, sys
readDomain('DOMAIN_HOME')
addTemplate('MW_HOME/oracle_common/common/templates/applications/jrf_template_11.1.1.jar')
addTemplate('MW_HOME/oracle_common/common/templates/applications/oracle.em_11_1_1_0_0_template.jar')
updateDomain()
closeDomain()
exit()

For example, you could create a file called enable_domain_7001.py that contained the following:

#!/usr/bin/python
import os, sys
readDomain('/oracle/Domains/ExampleSilentWTDomain')
addTemplate('/oracle/Middleware/oracle_common/common/templates/applications/jrf_template_11.1.1.jar')
addTemplate('/oracle/Middleware/oracle_common/common/templates/applications/oracle.em_11_1_1_0_0_template.jar')
updateDomain()
closeDomain()
exit()

After the script is created, run it using WLST. For example:

wlst path_to_script/enable_domain_7001.py

D.2.5 Task 5: Start the Administration Server in the WebLogic Server Domain

After the domain is created, start the Administration Server. Go to the DOMAIN_HOME and run the startWebLogic.sh script. Using our example:

cd /oracle/Domains/ExampleSilentWTDomain
./startWebLogic.sh

D.2.6 Task 6: Verify that the Domain is Up and Running

Log in to Fusion Middleware Control using the following URL:

http://administration_server_host:administration_server_port/em

Log in to the Administration Server Console using the following URL:

http://administration_server_host:administration_server_port/console

D.3 Oracle Web Tier Response Files

Before doing a silent installation, you must provide information specific to your installation in a response file. The installer fails if you attempt an installation by 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 are 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.

This section contains the following:

D.3.1 Configuration-Only Response Files

This is the template response file that should be used if you have already installed the Oracle Web Tier software but have not yet run the Configuration Tool (Section D.2.2).

The equivalent using the GUI would be running the config.sh script on UNIX, and config.bat script on Windows, after you have already installed the software using the Install Software - Do Not Configure option on the Select Installation Type Screen.

The contents of the Disk1/stage/Response/WebTierConfigureOnly.rsp response file on a UNIX system is given below:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#The name of the Oracle Instance. Instance name must begin with an alphabetic character, may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters and are 4 to 30 characters long.
INSTANCE_HOME=/oracle/product/11.1.1/as_1/instances/instance1
 
#Provide the Oracle Instance location. The Oracle Instance 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 or non existing directory.
INSTANCE_NAME=instance1
 
#If set to true, installer will auto assign ports
AUTOMATIC_PORT_DETECT=true
 
#This is required if "AUTOMATIC_PORT_DETECT" variable is set to false, absolute path of a staticports file location need to be provided with values for ports.\nThe template for staticports.ini can be found from Disk1/staget/Response directory of the shiphome.
STATICPORT INI FILE LOCATION=
 
 
[SYSTEM]
 
#Set true to create a new instance and configure Oracle Process Management Notification, else skip the configuration
CONFIGURE_OPMN=true
 
#Set true to configure Oracle HTTP Server, else skip Oracle HTTP Server configuration
CONFIGURE_OHS=true
 
#Set true to configure Oracle Web Cache, else skip Oracle Web Cache configuration
CONFIGURE_WEBCACHE=true
 
#The Oracle HTTP Server (OHS) component name (required only if CONFIGURE_OHS is set to true). OHS component name must begin with an alphabetic character, may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters and are 4 to 30 characters long.
OHS_COMPONENT_NAME=ohs1
 
#The Web Cache component name (required only if CONFIGURE_WEBCACHE is set to true). Web Cache component name must begin with an alphabetic character, may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters and are 4 to 30 characters long.
WEBCACHE_COMPONENT_NAME=webcache1
 
#Valid passwords are 5 to 30 characters long, must begin with an alphabetic character, use only alphanumeric, underscore (_), dollar ($) or pound (#) characters and include at least one number.
WEBCACHE_ADMINISTRATOR_PASSWORD=<SECURE VALUE>
 
#The confirmation password for Web Cache administrator.
WEBCACHE_ADMINISTRATOR_PASSWORD_CONFIRM=<SECURE VALUE>
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

#If set to true, the instance and components will be registered with an existing weblogic server
ASSOCIATE_WEBTIER_WITH_DOMAIN=true
 
#Provide the exiting Middleware Home location. This is required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true.
MIDDLEWARE_HOME=/Oracle/Middleware
 
#Provide an existing domain host name. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_HOST_NAME=machinename.machinedomain
 
#Provide the existing domain port number. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_PORT_NO=7001
 
#Provide the domain user name. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_USER_NAME=weblogic
 
#The domain user password. Required only if ASSOCIATE_WEBTIER_WITH_DOMAIN is set to true
DOMAIN_USER_PASSWORD=<SECURE VALUE>

D.3.1.1 Contents of the WebTierConfigureOnly.rsp File

D.3.2 Patch Set Installer Response Files

This section describes the webtier_patch_install.rsp response file provided in the Disk1/stage/Response directory on UNIX, and Disk1\stage\Response directory on Windows, in which you downloaded and extracted the Patch Set Installer archive file. This response file is designed for use in situations where you are updating an existing Oracle Web Tier Oracle Home.

The contents of the Disk1/stage/Response/webtier_patch_install.rsp response file on a UNIX system is shown below:

[ENGINE]
 
#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0
 
[GENERIC]
 
#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 WebTier Oracle Home.
ORACLE_HOME=/scratch/Middleware/Oracle_WT1
 
#Provide existing Middleware Home location.
MIDDLEWARE_HOME=/scratch/Middleware
 
#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=
 
#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
 
#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My OracleSupport username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=true
 
#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
 
#
CONFIG_WIZARD_RESPONSE_FILE_LOCATION=0
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

The parameters you should set in this file are:

  • ORACLE_HOME: Specify the full path to your Oracle home directory.

  • MIDDLEWARE_HOME: Specify the full path to your Middleware home directory.

  • Decide whether or not you want to configure Oracle Configuration Manager for automatic software and security updates.

    If you do not want to configure Oracle Configuration Manager, set DECLINE_SECURITY_UPDATES to true.

    If you want to configure Oracle Configuration Manager, set SECURITY_UPDATES_VIA_MYORACLESUPPORT to true. Doing so also requires that you set the MYORACLESUPPORT_USERNAME and MYORACLESUPPORT_PASSWORD parameters with your My Oracle Support user name and password, respectively.

    For more information about Oracle Configuration Manager, see "Installing Oracle Configuration Manager" in the Oracle Fusion Middleware Installation Planning Guide.

D.3.3 Deinstallation Response Files

Table D-2 lists the response files provided for silent deinstallation in the Disk1/stage/Response directory on UNIX, and Disk1\stage\Response directory on Windows, on the installation CD-ROM:

Table D-2 Oracle Web Tier Deinstallation Response File Templates

Template Description

deinstall_managed_instance.rsp

This is the template response file that should be used if you have configured managed instances on your system. These managed instances must be removed before you remove the Oracle home.

The equivalent using the GUI would be starting the deinstaller and selecting the Deinstall ASInstances managed by WebLogic Domain option on the Select Deinstallation Type Screen.

See Section D.3.3.1 to view the contents of this file.

deinstall_unmanaged_instance.rsp

This is the template response file that should be used if you have configured unmanaged instances on your system. These unmanaged instances must be removed before you remove the Oracle home.

The equivalent using the GUI would be starting the deinstaller and selecting the Deinstall Unmanaged ASInstances option on the Select Deinstallation Type Screen.

See Section D.3.3.2 to view the contents of this file.

deinstall_oh.rsp

This is the template response file that should be used if you have already removed all managed and unmanaged instances that use this Oracle Home, and now you are ready to remove the Oracle home.

The equivalent using the GUI would be starting the deinstaller and selecting the Deinstall Oracle Home option on the Select Deinstallation Type Screen.

See Section D.3.3.3 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, and then clicking Save on the Deinstallation Summary Screen (Managed Instance) screen. You are 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 deinstallation on other systems, or modify it as needed.

D.3.3.1 Contents of the deinstall_managed_instances.rsp File

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

[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=true
 
#Specify true for Oracle Home deinstall
OH_HOME_DEINSTALL=false
 
#Specify true for Managed Instance deinstall
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=true
 
#Specify true for Un-managed Instance deinstall
UNMANAGED_ASINSTANCE_DEINSTALL=false
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]
 
#Specify the Domain Host Name
DOMAIN_HOST_NAME=localhost.domain
 
#Specify the Domain Port Number
DOMAIN_PORT_NO=7001
 
#Specify the Domain User Name
DOMAIN_USER_NAME=weblogic
 
#Specify the Domain Password
DOMAIN_USER_PASSWORD=<SECURE PASSWORD>
 
#Specify the list of Instance to be deinstalled in the following format. InstanceName^LocationOfInstance$InstanceName^LocationOfInstance
MANAGED_INSTANCE_LIST=asinst_1^C:\wls1\asinst_1$

D.3.3.2 Contents of the deinstall_unmanaged_instances.rsp File

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

[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=true
 
#Specify true for Oracle Home deinstall
OH_HOME_DEINSTALL=false
 
#Specify true for Managed Instance deinstall
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=false
 
#Specify true for Un-managed Instance deinstall
UNMANAGED_ASINSTANCE_DEINSTALL=true
 
#Specify the path of the Un-managed Instance
ASINSTANCE_LOCATION_TEXTFIELD=c:\Oracle\Middleware\asinst_1
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]

D.3.3.3 Contents of the deinstall_oh.rsp File

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

[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=true
 
#Specify true for Oracle Home deinstall
OH_HOME_DEINSTALL=true
 
#Specify true for Managed Instance deinstall
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=false
 
#Specify true for Un-managed Instance deinstall
UNMANAGED_ASINSTANCE_DEINSTALL=false
 
 
[SYSTEM]
 
 
[APPLICATIONS]
 
 
[RELATIONSHIPS]