B Installing Oracle Database Companion CD Products in Noninteractive Mode

This appendix describes the following advanced installation topics:

Installing Oracle Components in Noninteractive Mode
Running Oracle Workflow Configuration Assistant in Noninteractive Mode

B.1 Installing Oracle Components in Noninteractive Mode

Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information on graphical user interface (GUI) screens. Alternatively, you can run Oracle Universal Installer in noninteractive mode. This mode is also referred to as silent mode, or silent installation.

You may want to use noninteractive mode to install the Oracle Database Companion CD products in the following scenarios:

You need to perform an unattended deployment of Companion CD products to multiple nodes. You can schedule the noninteractive installation mode from the operating system scheduler or other job subsystem that your site normally uses. This method is particularly useful for large sites that require many Oracle Database installations in which you need to quickly perform multiple installations using similar settings for each computer.
No interaction with the user is intended.
A graphical facility to run Oracle Universal Installer in interactive mode is not available.

This section covers the following topics on how you can use response files to run Oracle Universal Installer in noninteractive mode:

Using Response Files to Install Oracle Components in Noninteractive Mode
Editing a Response File Template
Recording a Response File
Running Oracle Universal Installer in Silent or Suppressed Mode

B.1.1 Using Response Files to Install Oracle Components in Noninteractive Mode

To use the noninteractive mode, you run Oracle Universal Installer with a response file. A response file is a text file that contains variables and values that Oracle Universal Installer uses during the installation process. Oracle provides a set of sample response files that you can customize, or you can create your own response file by recording your installation selections.

B.1.2 Editing a Response File Template

Table B-1 lists the sample response files provided on the installation media.

Table B-1 Response Files

Response File	Description
`htmldb.HTMLDBONLY.rsp`	Oracle HTML DB only installation
`htmldb.HTMLDBwithOHS.rsp`	Oracle HTML DB with Oracle HTTP Server installation
`companionCD.db.rsp`	Oracle Database 10g Products installation type
`companionCD.midtier.rsp`	Oracle Database Companion CD installation type

To modify a response file template:

Copy the response file from the response file directory to a directory on your system as follows:
```
$ cp /directory_path/response/response_file.rsp local_directory
```
In this example, directory_path is the path of the companion directory on the installation media or the hard drive. If you have copied the software to a hard drive, then you can also edit the file in the response directory.
Open the response file in a text editor:
```
$ vi /local_dir/response_file.rsp
```
In addition to editing settings specific to the Oracle Database installation, check that the FROM_LOCATION path is correct and points to the products.xml file in the stage directory in the installation media. You may want to set this variable to point to an absolute path, for example:
```
FROM_LOCATION="/directory_path/response/stage/products.xml"
```
Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file.

See Also:
Oracle Universal Installer and OPatch User's Guide for detailed information on creating response files.
To edit the file, follow the instructions in the file.

Note:
Oracle Universal Installer or the configuration assistant fails if you do not correctly configure the response file.

Change the permissions on the file to 700:

$ chmod 700 /local_dir/response_file.rsp

Caution:

A fully specified response file for an Oracle Database installation contains the passwords for database administrative accounts and for a user that is a member of the OSDBA group (required for automated backups). Ensure that only the Oracle software owner user can view or modify response files or consider deleting them after the installation succeeds.

B.1.3 Recording a Response File

You can use Oracle Universal Installer in interactive mode to record a response file that you can edit and then use to complete silent-mode or suppressed-mode installations. When you are recording the response file, you can either complete the installation, or you can exit from Oracle Universal Installer on the Summary page, before it starts to copy the software to the system.

If you want to use Record mode during a noninteractive installation, then Oracle Universal Installer copies the variable values that were specified in the original source response file into the new response file.

To record a new response file:

Ensure that the computer on which you are creating the response file meets the requirements specified in Chapter 2.

When you run Oracle Universal Installer to record a response file, it checks the system to verify that it meets the requirements to install the software.
Enter a command similar to the following to start Oracle Universal Installer:

Note:
Do not specify a relative path to the response file. If you specify a relative path, then Oracle Universal Installer fails.
```
$ /directory_path/runInstaller -record -destinationFile filename
```
In this command:
- directory_path is the path of the companion directory on the installation media or the hard drive
- -record specifies that you want to record the responses that you enter in a response file
- filename is the full path and file name of the response file that you want to record
On each Oracle Universal Installer screen, specify the required information.
When Oracle Universal Installer displays the Summary screen, perform one of the following steps:
- Click Install to create the response file, and then continue with the installation.
- Click Cancel, and then click Yes to create the response file but exit from Oracle Universal Installer without installing the software.
The response file is saved in the location that you specified using the -destinationFile option.
If you do not complete the installation, then delete the Oracle home directory that Oracle Universal Installer created using the path you specified on the Specify File Locations screen.
Before using the recorded response file on another system, use a text editor to edit the file and make any required changes.

Use the comments in the file as a guide when editing it.
Run the response file by following the instructions in the "Running Oracle Universal Installer in Silent or Suppressed Mode" section.

B.1.4 Running Oracle Universal Installer in Silent or Suppressed Mode

To run Oracle Universal Installer in silent or suppressed mode, follow these steps:

Complete the preinstallation tasks listed in Chapter 2.
Log in as the Oracle software owner user (typically, oracle).
If you are completing a suppressed-mode installation, set the DISPLAY environment variable .

Note:
You do not have to set the DISPLAY environment variable if you are completing a silent-mode installation.
To start Oracle Universal Installer in silent or suppressed mode, enter a command similar to the following:

Note:
Do not specify a relative path to the response file. If you specify a relative path, then Oracle Universal Installer fails.
```
$ /directory_path/runInstaller [-silent] [-noconfig] -responseFile filename [-paramFile oraparamsilent.ini]
```
In this example:
- directory_path is the path of the companion directory on the installation media or the hard drive
- -silent indicates that you want to run Oracle Universal Installer in silent mode
- -noconfig suppresses running the configuration assistants during installation, and a software-only installation is performed instead
- filename is the full path and file name of the installation response file that you configured
- The optional -paramFile option specifies an alternative parameter file (oraparamsilent.ini) that you can use when performing silent installations. This alternative parameter file does not include checks for CDE or X Window System software patches for Solaris.
See Also:
For more information about other options for the runInstaller command, enter the following command:
$ /directory_path/runInstaller -help
After the installation is completed, log in as the root user and run the root.sh script:
```
$ su
# $ORACLE_HOME/root.sh
```

B.2 Running Oracle Workflow Configuration Assistant in Noninteractive Mode

You can run Oracle Workflow Configuration Assistant in noninteractive mode by entering your configuration parameter settings directly in the Oracle Workflow Configuration Assistant wfinstall.csh script. You must specify all required and conditionally required parameters for the features that you want to use.

To run Oracle Workflow Configuration Assistant in noninteractive mode:

Go to the $ORACLE_HOME/wf/install directory, which is the default location of the wfinstall.csh script.

Open the wfinstall.csh script in a text editor, and locate the line that is similar to the following:

. . . repository.jar" WorkflowCA /wfdir workflow_directory /orahome oracle_home

For example:

. . . repository.jar" WorkflowCA /wfdir /d1/iasinstall/m21pw1/wf 
/orahome /d1/iasinstall/m21pw1

Edit the script to append your additional parameters after the /wfdir, /orahome, and /ospath parameters. Enter all the parameters on the same line. Otherwise, the script will not run correctly.

. . . repository.jar" WorkflowCA /wfdir workflow_directory /orahome 
oracle_home /wfacct workflow_schema
/instype installation_type /tnsconndesc connection_string

In the preceding script line:

/wfdir: The Oracle Workflow directory within your Oracle home directory. The default directory is $ORACLE_HOME/wf.
/orahome: Your Oracle home directory location. For example, /u01/app/oracle/product/10.2/db_2.
/wfacct: Workflow Account.
/instype: Specify one of the following installation options:
- server: Configures Workflow Server only; available in both GUI mode and command-line mode
- add_language: Sets the language or languages used; available in both GUI mode and command-line mode
/tnsconndesc: Connection string to the Oracle Database.

Note:

If a parameter can be entered in both user interface mode and noninteractive mode, then this section lists the name of the corresponding field on the Oracle Workflow Configuration Assistant screen alongside the noninteractive mode parameter name.

If you specified add_language for the /instype parameter, then enter the /nlsopt parameter with the languages you want to add.

Enclose the languages in double quotation marks. For example, to specify Arabic, German, and Danish, enter the following value:
```
"ar d dk"
```
To use all available languages, set nlsop to all. Oracle Workflow Server supports all the languages that Oracle Database supports.

See Also:
The "Locale Data" section in Oracle Database Globalization Support Guide for a list of standard language abbreviations
If you specified server for the /instype parameter, then enter the following parameters if you want to integrate Oracle Internet Directory as your Oracle Workflow directory service:
- /ldaphost: LDAP host name
- /ldapport: LDAP non-SSL port
- /ldapuser: LDAP admin user name
- /ldaplogbase: Changelog DN
- /ldapuserbase: User base (for example, /ldapuserbase cn=Users,dc=us,dc=oracle,dc=com)
If you are upgrading an existing installation of Oracle Workflow that is already integrated with Oracle Internet Directory, then you can omit the LDAP parameters for Oracle Internet Directory integration if they are already defined in your database.

In this case, Oracle Workflow Configuration Assistant configures your Oracle Internet Directory integration by using the existing LDAP parameters defined in your database. However, if you specify new LDAP parameters here, then Oracle Workflow Configuration Assistant will update your settings.
If you specified server or all for the /instype parameter, then enter the following parameters if you want to use Oracle Workflow Notification Mailer:
- /mailserver: Inbound e-mail account: server name
- /mailuser: Inbound e-mail account: user name
- /mailhost: Outbound e-mail account: server name
- /htmlagent: Message generation: HTML agent
- /mailreply: Message generation: reply-to address
- /processfolder: E-mail processing: name of processed folder
- /discardfolder: E-mail processing: name of discard folder
If you specified server for the /instype parameter and if you want to change the tablespace assigned to the Oracle Workflow database account, then set the /tablespace parameter to a valid existing tablespace name.
To control how Oracle Workflow Configuration Assistant writes log information, set the following parameters:
- /debug: Specify true if you want Oracle Workflow Configuration Assistant to write debug information to the workflow.log file. By default, Oracle Workflow does not log this information.
- /logdir: Specify the path to the directory in which you want Oracle Workflow Configuration Assistant to write the workflow.log file, or specify nolog if you do not want to create a log file. By default, the log file is written to the $ORACLE_HOME/wf/install directory.
Save your changes, and close the wfinstall.csh file.
To run the wfinstall.csh script, enter the following command:
```
$ORACLE_HOME/wf/install/wfinstall.csh
```

If the wfinstall.csh script includes the minimum parameters, all entered as a single line of text in the file, then it performs the configuration in noninteractive mode, without displaying the Oracle Workflow Assistant screen. However, as a security precaution, the script may prompt you to enter the following passwords at run time, depending on the installation options that your site uses:

The password for your Oracle Workflow database account
Your SYS password
The password for the LDAP user account, if you enter LDAP parameters
The password for the notification mailer e-mail account, if you enter mailer parameters