Installation Guide

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Running the Installation in the Silent Mode

The following sections describe how to run the installation program in silent mode:

 

What Is Silent-Mode Installation?

Silent-mode installation is a way of setting installation configurations once and then using these configurations to duplicate the installation on many machines. During installation in silent mode, the installation program reads the settings for your configuration from an XML file that you create prior to beginning the installation. The installation program does not display any configuration options during the installation process. Silent-mode installation works on both Windows and UNIX systems.

It is assumed that you have already acquired the installation program, either on DVD or from the Oracle Web site. For more information on different modes of product distribution, see Product Distribution Methods.

 

Using Silent-Mode Installation

The silent-mode installation process for Oracle Enterprise Repository has three primary steps:

  1. Follow the preparation guidelines in Preparing for Your Installation, especially the Database Installation Procedures for your DBMS.
  2. Creating a silent.xml file that defines the configuration settings normally entered by a user during an interactive installation process, such as graphical-mode or console-mode installation. For example, values for the Oracle Home directory, the product directory, and the components to be installed are supplied in a silent.xml file.

    3. For a detailed procedure, see Creating a silent.xml File for Silent-Mode Installation. For a sample silent.xml file, see Sample silent.xml Files for Silent-Mode Installation.

  3. Starting the silent-mode installation process using the values specified in the silent.xml file.

    4. For more information on launching the installation in silent mode, see Starting the Installation Program.

Important Considerations for Silent-Mode Installation

When you are performing an installation in silent mode, keep in mind the following considerations:

 

Creating a silent.xml File for Silent-Mode Installation

When you install your Oracle Enterprise Repository software in silent mode, the installation program uses an XML file (silent.xml) to determine which installation options should be implemented. Therefore, before you can run the installation program in silent mode, you must first create a silent.xml file in which you specify the installation options that you want to invoke.

Incorrect entries in the silent.xml file can cause installation to fail. To help you determine the cause of a failure, Oracle recommends that you create a log file when you start the installation.

Caution: Before running the installer in silent mode, follow the preparation guidelines in Preparing for Your Installation, especially the Database Installation Procedures for your DBMS.

To create a silent.xml file for use in the silent-mode installation process, follow these steps:

  1. In a supported browser, view the sample silent.xml file for silent-mode installation. The sample file is available at http://e-docs.bea.com/common/docs92/install/scripts/silent.xml

    2. This sample silent.xml file is also presented in this section. See Sample silent.xml Files for Silent-Mode Installation.

  2. Save the sample XML file, with the name silent.xml, in the same directory that contains the installation program.
    3. Note: The XML definition (<?xml version="1.0" encoding="ISO-8859-1"?>) must be at the very beginning of the silent.xml file. There should not be any spaces or line breaks before the XML definition.
  3. In the silent.xml file that you saved on your system, edit the values for the keywords shown in Table 6-1 to reflect your configuration.
    4. Note: You must follow XML guidelines for characters when modifying values. That is, do not use characters reserved for use in XML, such as <, >, [, and].

    Table 6-1 Parameters for Silent.xml
    For this data-value name...
    Enter the following value...
    OracleHOME
    The full path for the Oracle Home directory of your choice. For details about the Oracle Home directory, see Choosing a Oracle Home Directory.
    COMPONENT_PATHS
    The components and subcomponents you want to install on your system:
    • To install Oracle Enterprise Repository, use the following values:
        Oracle Enterprise Repository
        Core Repository with Examples
        Oracle Enterprise Repository Plug-In for Eclipse
    For more information about entering these values, see Guidelines for Component Selection.
    APP_SERVER_TYPE
    The application server type used to run Oracle Enterprise Repository. Valid values are:
    • value for user-supplied Tomcat (GUI = Tomcat 5.5.17/18 (user supplied))
    • value for WLS (GUI = WebLogic Server 10.3)
    • value for WAS (GUI = WebSphere 6.1)
    • value for Generic App Server (GUI =Generic Application Server)
    APP_SERVER_NAME
    The application server name used to run Oracle Enterprise Repository.
    Valid values are:
    • Tomcat 5.5.17/18 (user supplied)
    • WebLogic Server 9.2.1/9.2.2
    • WebSphere 6.1
    • Generic Application Server
    APP_PATH
    The Oracle Enterprise Repository application path. For example, if the ALER_URL is ultimately http://www.myhost.com:8001/OER301, then the APP_PATH is OER301.
    WEB_PATH
    The web application path. It is recommended that the WEB_PATH value should be the APP_PATH value with -web appended. For example, if APP_PATH=oer10300, then WEB_PATH is recommended to be oer10300-web.
    ALER_URL
    The fully-qualified server and domain name where Oracle Enterprise Repository is being installed (for example, myserver.mydomain.com)
    DOMAIN_LISTEN_PORT
    The domain listening port.
    USER_INSTALL_DIR
    The directory where Oracle Enterprise Repository will be installed within the specified OracleHOME.
    RUN_DBCONFIG_WIZARD
    The flag to run the DB Configuration Wizard:
    • true or yes, to run the Database Configuration wizard. The default is true.
    • false or no, to skip the database wizard.
    CONFIG_RESPOSIT_DB
    The flag to run the Repository Database Configuration wizard, which initializes the repository database properties.
    • true or yes, to configure a Repository Database Configuration wizard. The default is true.
    • false or no, to skip the configuration of a database.

    Note: This flag is skipped if RUN_DBCONFIG_WIZARD is set to false or no.
    DB_TABLE_BLOB
    Tablespace name for BLOBs.

    Note: For the BLOB Tablespace field, enter the same value that you specify for DB_TABLE_DATA.
    DB_TABLE_DATA
    The data tablespace name to be used by Oracle Enterprise Repository. For example:
    • SQL Server – PRIMARY
    • Oracle – OER_DATA
    • DB2 – oerdatats
    DB_TABLE_INDEX
    The index tablespace name to be used by Oracle Enterprise Repository. For example:
    • SQL Server – INDEX
    • Oracle – OER_INDEX
    • DB2 – oerindxts
    DB_DRIVER
    Name of the driver. For example: oracle.jdbc.driver.OracleDriver
    DB_JARFILES
    Path to the driver JAR file. For example:
    • Oracle – d:\jdbc14.jar
    • SQL 2005 – d:\qljdbc.jar
    DB_DBMS
    The database management system.
    • Oracle – enter the SID that the Oracle Enterprise Repository schema was installed on. For Oracle, the default SID is orcl; for Oracle XE, the default SID is xe.

      • Note: You can determine the SID needs to be entered by running this SQL statement: select instance_name from v$instance;

    • SQL – enter the database name (e.g., OER)
    DB_PORT
    The database port number.
    DB_HOST
    The fully-qualified server and domain name where Oracle Enterprise Repository is being installed (for example, myserver.mydomain.com).
    DB_USERNAME
    The database user name.
    Enter the appropriate user information from the Database Installation Procedures instructions for your DBMS.
    DB_PASSWORD
    The password for a database user.
    Enter the appropriate user information from the Database Installation Procedures instructions for your DBMS.
    APP_SERVER_HOME
    The application server home directory
    For example: OracleHOME\weblogic103
    USER_DOMAIN_DIR
    The Oracle Enterprise Repository User Domain Directory directory.
    For example: OracleHOME\user_projects\domains\oerDomain
    SUPPORTED_WL_HOME
    The supported WebLogic Server home.
    For example: OracleHOME\weblogic103
    WL_HOME
    The WebLogic Server home.
    For example: OracleHOME\weblogic103
    ECLIPSE32_HOME
    For installations pointing at existing Eclipse plug-ins for Oracle Enterprise Repository, specifies the optional Eclipse installation. If this key/value is not specified, the installer continues as in the normal GUI installation.
    <data-value name="ECLIPSE32_HOME" value="c:\my_eclipse_home" />

Note: The application server name and the types supported for Oracle Enterprise Repository 10.3 are as follows (these combinations must be used together):

Apache Tomcat Installs:

APP_SERVER_NAME=Tomcat 5.5.17/18 (user-supplied)

APP_SERVER_TYPE=user_tomcat

WebLogic Installs:

APP_SERVER_NAME=WebLogic Server 10.3

APP_SERVER_TYPE=wls

WebSphere Installs:

APP_SERVER_NAME=WebSphere 6.1

APP_SERVER_TYPE=was

Generic Application Server Installs:

APP_SERVER_NAME=Generic Application Server

APP_SERVER_TYPE=generic

Guidelines for Component Selection

Use the following guidelines when you specify values for the COMPONENT_PATHS data-value name:

 

Sample silent.xml Files for Silent-Mode Installation

The following sample silent.xml demonstrate how to install Oracle Enterprise Repository and configure a database.

Listing 6-1 Sample XML File -- Install Oracle Enterprise Repository with Database Configuration and Oracle BPM Process Engine 
<?xml version='1.0' encoding='UTF-8'?>
<Oracle-installer>
  <input-fields>
  <data-value name='OracleHOME' value='D:\dev\silentInstall\oer_obpm'/>
  <data-value name='COMPONENT_PATHS' value='AquaLogic Enterprise Repository/Core Repository with Examples|AquaLogic Enterprise Repository/AquaLogic Enterprise Repository Plug-In for Eclipse|AquaLogic BPM/Process Engine'/>
  <data-value name='APP_SERVER_TYPE' value='ce_tomcat' />
  <data-value name='APP_SERVER_NAME' value='Default'/>
  <data-value name='APP_PATH' value='oer3'/>
  <data-value name='WEB_PATH' value='oer3-web'/>
  <data-value name='ALER_URL' value='MyURL' />
  <data-value name='DOMAIN_LISTEN_PORT' value='8080' />
  <data-value name='APP_SERVER_HOME' value='D:\dev\silentInstall\oer_obpm\my\tomcat'/>
  <data-value name='USER_INSTALL_DIR' value='D:\dev\silentInstall\oer_obpm\repostoryXXX'/>
  <data-value name='RUN_DBCONFIG_WIZARD' value='yes'/>
  <data-value name='CONFIG_RESPOSIT_DB' value='yes'/>
  <data-value name='DB_TABLE_BLOB' value='USER_BLOB'/>
  <data-value name='DB_TABLE_DATA' value='USER_DATA'/>
  <data-value name='DB_TABLE_INDEX' value='USER_INDEX'/>
  <data-value name='DB_DRIVER' value='oracle.jdbc.driver.OracleDriver'/>
  <data-value name='DB_JARFILES' value='d:\ojdbc14.jar'/>
  <data-value name='DB_DBMS' value='sid2'/>
  <data-value name='DB_PORT' value='1521'/>
  <data-value name='DB_HOST' value='MyHostName'/>
  <data-value name='DB_USERNAME' value='silent'/>
  <data-value name='DB_PASSWORD' value='silent'/>
  <data-value name='CONFIGURE_WORKFLOW' value='yes'/>
  </input-fields>
\</Oracle-installer>
Listing 6-2 Sample XML File -- Install Oracle Enterprise Repository Only with Database Configuration 
<?xml version='1.0' encoding='UTF-8'?>
<Oracle-installer>
  <input-fields>
  <data-value name='OracleHOME' value='D:\dev\silentInstall\oer3'/>
  <data-value name='COMPONENT_PATHS' value='AquaLogic Enterprise Repository/Core Repository with Examples|AquaLogic Enterprise Repository/AquaLogic Enterprise Repository Plug-In for Eclipse'/>
  <data-value name='APP_SERVER_TYPE' value='ce_tomcat' />
  <data-value name='APP_SERVER_NAME' value='Default '/>
  <data-value name='APP_PATH' value='oer3'/>
  <data-value name='WEB_PATH' value='oer3-web'/>
  <data-value name='ALER_URL' value='MyURL' />
  <data-value name='DOMAIN_LISTEN_PORT' value='8080' />
  <data-value name='APP_SERVER_HOME' value='D:\dev\silentInstall\oer_obpm\my\tomcat'/>
  <data-value name='USER_INSTALL_DIR' value='D:\dev\silentInstall\oer_obpm\repostoryXXX'/>
  <data-value name='RUN_DBCONFIG_WIZARD' value='yes'/>
  <data-value name='CONFIG_RESPOSIT_DB' value='yes'/>
  <data-value name='DB_TABLE_BLOB' value='USER_BLOB'/>
  <data-value name='DB_TABLE_DATA' value='USER_DATA'/>
  <data-value name='DB_TABLE_INDEX' value='USER_INDEX'/>
  <data-value name='DB_DRIVER' value='oracle.jdbc.driver.OracleDriver'/>
  <data-value name='DB_JARFILES' value='d:\ojdbc14.jar'/>
  <data-value name='DB_DBMS' value='sid2'/>
  <data-value name='DB_PORT' value='1521'/>
  <data-value name='DB_HOST' value='MyHostName'/>
  <data-value name='DB_USERNAME' value='silent'/>
  <data-value name='DB_PASSWORD' value='silent'/>
  </input-fields>
\</Oracle-installer>

For more information on launching the installation in silent mode, see Starting the Installation Program.

 

Returning Exit Codes to the Console

When run in silent mode, the installation program generates exit codes that indicate the success or failure of the installation. These exit codes are shown in the following table.

Code
Description
0
Installation Completed Successfully.
1
Installation failed due to a fatal error.
2
Installation failed due to an internal XML parsing error.

If you are launching the silent-mode installation process from a script, you can choose to have these exit codes displayed on the console. Listing 6-3 provides a sample command file that invokes the installation program in silent mode and echoes the exit codes to the console from which the script is executed.

Listing 6-3 Sample Command File Displaying Silent-Mode Exit Codes 
rem Execute the installer in silent mode
@echo off
OER10XX_win32.exe -mode=silent -silent_xml=mySilentXMLFile.xml -log=oer_30.log
@rem Return an exit code to indicate success or failure of installation
set exit_code=%ERRORLEVEL%
@echo.
@echo Exitcode=%exit_code%
@echo.
@echo Exit Code Key
@echo ---------------
@echo  0=Installation completed successfully
@echo -1=Installation failed due to a fatal error
@echo -2=Installation failed due to an internal XML parsing error
@echo.

 

What’s Next

After completing the installation process, complete the following post installation tasks, as described in Post-Installation Instructions.


  Back to Top       Previous  Next