Skip Headers
Oracle® Database Companion CD Installation Guide
10g Release 2 (10.2) for Microsoft Windows (32-Bit)

Part Number B14324-02
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
View PDF

B Installing Oracle Database Companion CD Using Response Files

This appendix covers the following topics:

B.1 How Response Files Work

You can automate the installation and configuration of Oracle software, either fully or partially, by specifying a response file when you start Oracle Universal Installer. Oracle Universal Installer uses the values in the response file to provide answers to some or all of the Oracle Universal Installer prompts.

Typically, Oracle Universal Installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you run Oracle Universal Installer at a command prompt using either of the following modes:

You define the settings for a silent or noninteractive installation by entering values for the variables listed in the response file. For instance, to specify the Oracle home name, you would supply the appropriate value for the ORACLE_HOME_NAME variable, as in the following example:

ORACLE_HOME_NAME="OraDBHome1

Another way of specifying the response file's variable settings is to pass them as command line arguments when you run Oracle Universal Installer. For example:

SYSTEM_DRIVE:\setup.exe_location> setup -silent "ORACLE_HOME_NAME=OraDBHome1" ...

This method is particularly useful if you do not want to embed sensitive information, such as passwords, in the response file. For example:

SYSTEM_DRIVE:\setup.exe_location> setup -silent "s_sysPwdFresh=binks342" ...

Ensure that you enclose the variable and its setting in quotes.

See Also:

Oracle Universal Installer and OPatch User's Guide for more information about response file formats.

B.1.1 Reasons for Using Silent Mode or Noninteractive Mode

Table B-1 describes several reasons why you might want to run Oracle Universal Installer in silent mode or noninteractive mode.

Table B-1 Reasons for Using Silent Mode or Noninteractive Mode

Mode Uses

Silent

Use silent mode if you want to:

  • Complete an unattended installation

  • Complete several similar installations on multiple systems without user interaction

Oracle Universal Installer displays progress information in the window that you used to start it, but it does not display the Oracle Universal Installer screens.

Noninteractive

Use noninteractive mode if you want to complete similar Oracle software installations on more than one system, providing default answers to some, but not all, of Oracle Universal Installer prompts.

If you do not specify information required for a particular Installer screen in the response file, Oracle Universal Installer displays that screen. It suppresses screens for which you have provided all of the required information.


B.1.2 General Procedure for Using Response Files

You follow these general steps to install the Oracle Database Companion CD products using response files:

  1. Customize or create a response file for the installation settings that you need.

    You can create the response file by using one of the following methods:

    • Modify one of the sample response files that is provided with the installation.

    • Run Oracle Universal Installer at a command prompt using record mode.

    "Preparing a Response File" explains how to customize or create the response file.

  2. Run Oracle Universal Installer from a command prompt, specifying the response file, using either silent or noninteractive mode.

    "Running Oracle Universal Installer Using the Response File" explains how to run Oracle Universal Installer with a response file.

B.2 Preparing a Response File

This section describes the methods that you can use to prepare a response file for use during silent-mode or noninteractive-mode installations:

B.2.1 Editing a Response File Template

Oracle provides response file templates for each product and installation type, and for each configuration tool. These files are located in the companion\response directory on the Oracle Database installation media.

Creating a response file using a response file template is most useful for the Enterprise Edition or Standard Edition installation types.

Table B-2 lists the available sample response files:

Table B-2 Response Files

Response File Name This File Silently Runs The...

companionCD.db.rsp

Oracle Database Products installation type

companionCD.midtier.rsp

Oracle Database Companion CD installation type

htmldb.HTMLDBONLY

Oracle HTML DB-only installation of Oracle HTML DB installation type

htmldb.HTMLDBwithOHS.rsp

Oracle HTML DB and Oracle HTTP Server installation of Oracle HTML DB installation type


To copy and modify a response file:

  1. Copy the appropriate response files from the companion\Response directory on the Oracle Database media to your hard drive.

  2. Modify the response files with a text file editor.

    In addition to editing settings specific to the Oracle Database Companion CD products 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="\\myserver\companion\stage\products.xml"
    
    

    Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file. "How Response Files Work" explains this method.

    See Also:

    Oracle Universal Installer and OPatch User's Guide for detailed information on creating response files. In an installed Oracle Database, select Start, then Programs, then Oracle - HOME_NAME, then Oracle Installation Products, then Universal Installer Concepts Guide. It appears in HTML format.
  3. Run the response file by following the instructions in the "Running Oracle Universal Installer Using the Response File" section.

B.2.2 Recording a Response File

You can create a response file by running Oracle Universal Installer in interactive mode using record mode. This method is most useful for custom or software-only installations.

Recording the response file generates the response file immediately after you complete the Summary window, so you do not need to install the Oracle Database Companion CD products to create the response file. After you create the response file in this manner, you can customize it to meet your needs.

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

Note:

You cannot use record mode to create a response file based on the Basic installation type.

To record a response file:

  1. Ensure that the computer on which you are creating the response file has met the requirements in Chapter 2.

  2. At the command prompt, use the cd command to change to the directory that contains the Oracle Universal Installer setup.exe executable.

    On the installation DVD, setup.exe is located in the db directory. Alternatively, navigate to the directory where you downloaded or copied the installation files.

  3. Enter the following command:

    SYSTEM_DRIVE:\setup.exe_location> setup -record -destinationFile response_file_name
    
    

    Replace response_file_name with the complete path name for the new response file. For example:

    SYSTEM_DRIVE:\setup.exe_location> setup -record -destinationFile c:\response_files\install_oracle10_2.rsp
    
    
  4. After Oracle Universal Installer starts, enter the installation settings, which will be recorded in the response file.

  5. When the Summary window appears, do one of the following:

    • Click Install to create the response file and continue with the installation.

    • Click Cancel if you only want to create the response file but not continue with the installation. The installation will stop, but the settings you have entered will be recorded in the response file.

    Afterwards, Oracle Universal Installer saves your new response file using the path and file name you specified on the command line.

  6. Edit the new response file to have any environment-specific changes for the computer on which you will run it.

    In addition to editing settings specific to the Oracle Database Companion CD products 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="\\myserver\companion\response\stage\products.xml"
    
    

    Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file. "How Response Files Work" explains this method.

  7. Run the response file by following the instructions in the "Running Oracle Universal Installer Using the Response File" section, next.

B.3 Running Oracle Universal Installer Using the Response File

At this stage, you are ready to run Oracle Universal Installer at the command line, specifying the response file you created, to perform the installation. The Oracle Universal Installer executable, setup.exe, provides several options. For help information about the full set of these options, run setup.exe with the -help option, for example:

SYSTEM_DRIVE:\setup.exe_location> setup -help

A new command window appears, with the "Preparing to launch..." message. In a moment, the help information appears in that window.

To run Oracle Universal Installer and specify a response file:

  1. Place the response file on the computer where you want to install the Oracle Database Companion CD products.

  2. At a command prompt, run Oracle Universal Installer with the appropriate response file. For example:

    SYSTEM_DRIVE:\setup.exe_location> setup [-silent] "variable=setting" [-nowelcome] [-noconfig] [-nowait] -responseFile filename 
    
    

    where:

    • filename: Identifies the full path of the response file.

    • -silent: Runs Oracle Universal Installer in silent mode and suppresses the Welcome window. When you use -silent, then the -nowelcome option is not necessary.

    • "variable=setting" refers to a variable within the response file that you may prefer to run at the command line rather than set in the response file. Enclose the variable and its setting in quotes.

    • -nowelcome: Suppresses the Welcome window that appears during installation.

    • -noconfig: Suppresses running the configuration assistants during installation, performing a software-only installation instead.

    • -nowait: Closes the console window when the silent installation completes.

See Also:

  • "Installing Oracle Products" in Oracle Universal Installer and OPatch User's Guide for more information about installing using response files

  • "Deinstalling Products" in Oracle Universal Installer and OPatch User's Guide for more information about deinstalling using response files

B.4 Running Oracle Workflow Configuration Assistant in Noninteractive Mode

You can run Workflow Configuration Assistant in noninteractive mode by entering your configuration parameter settings directly in the Workflow Configuration Assistant wfinstall.bat 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:

  1. Go to the ORACLE_BASE\ORACLE_HOME\wf\install directory, which is the default location of the wfinstall.bat script.

  2. Open the wfinstall.bat script in a text editor and locate a line 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
    
    
  3. Edit the script to append your additional parameters after the /wfdir, /orahome, and /ospath parameters. Enter the parameters all 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
    
    

    where:

    • /wfdir: The Oracle Workflow directory within your Oracle Home directory. The default directory is ORACLE_BASE\ORACLE_HOME\wf.

    • /orahome: Your Oracle home directory location, for example, C:\oracle\product\10.2\Db_1.

    • /wintz: The time zone you are using, for example, "Pacific Daylight Time". (Enclose the time zone in quotes.)

    • /systemroot: The location of the system root files for your operating system, for example, C:\WINDOWS.

    • /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, this section lists the name of the corresponding field in the Oracle Workflow Configuration Assistant window alongside the noninteractive mode parameter name.
  4. If you specified add_language for the /instype parameter, enter the /nlsopt parameter with the languages you want to add.

    Enclose the languages in quotes. 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 languages that Oracle Database supports.

    See Also:

    "Locale Data" in Oracle Database Globalization Support Guide for a list of standard language abbreviations.
  5. If you specified server for the /instype parameter, 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 username

    • /ldaplogbase - Changelog DN

    • /ldapuserbase - User base (for example, /ldapuserbase cn=Users,dc=us,dc=oracle,dc=com)

    In these cases, Oracle Workflow Configuration Assistant configures your Oracle Internet Directory integration using the existing LDAP parameters defined in your database. However, if you specify new LDAP parameters here, the Oracle Workflow Configuration Assistant will update your settings.

  6. If you specified server or all for the /instype parameter, enter these parameters if you want to use Oracle Workflow Notification Mailer:

    • /mailserver - Inbound e-mail account: server name

    • /mailuser - Inbound e-mail account: username

    • /mailhost - Outbound e-mail account: server name

    • /htmlagent - Mail 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

  7. If you specified server for the /instype parameter, and if you want to change the tablespace assigned to the Oracle Workflow database account, set the /tablespace parameter to a valid existing tablespace name.

  8. To control how Oracle Workflow Configuration Assistant writes log information, set these 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 where 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_BASE\ORACLE_HOME\wf\install directory.

  9. Save your changes and exit the wfinstall.bat script.

To run the wfinstall.bat script, enter the following command:

ORACLE_BASE\ORACLE_HOME\wf\install\wfinstall.bat

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