The following sections describe how to run the installation program in silent mode:
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 BEA Web site. For more information on different modes of product distribution, see Product Distribution Methods.
The silent-mode installation process for ALER has three primary steps:
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 BEA Home directory, the product directory, and the components to be installed are supplied in a silent.xml
file.
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.
silent.xml
file. For more information on launching the installation in silent mode, see Starting the Installation Program.
When you are performing an installation in silent mode, keep in mind the following considerations:
silent.xml
file can cause installation failures. To help you determine the cause of a failure, BEA recommends that you create a log file when you start the installation. For more information on generating a verbose log, see Generating a Verbose Installation Log.<?xml version='1.0' encoding='UTF-8'?>
) must be at the very beginning of the silent.xml
file. There cannot be any spaces or line breaks before the XML definition.
When you install your ALER 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, BEA recommends that you create a log file when you start the installation.
Caution: | Before running the BEA Product 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:
silent.xml
file for silent-mode installation. The sample file is available at
http://e-docs.bea.com/common/docs92/install/scripts/silent.xml
This sample silent.xml
file is also presented in this section. See Sample silent.xml Files for Silent-Mode Installation.
silent.xml
, in the same directory that contains the installation program.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. |
silent.xml
file that you saved on your system, edit the values for the keywords shown in Table 6-1 to reflect your configuration.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]. |
The full path for the BEA Home directory of your choice. For details about the BEA Home directory, see Choosing a BEA Home Directory.
|
|||
For more information about entering these values, see Guidelines for Component Selection.
|
|||
The flag to run the Repository Database Configuration wizard, which initializes the repository database properties.
|
|||
|
|||
Note: You can determine the SID needs to be entered by running this SQL statement: |
|||
Enter the appropriate user information from the
Database Installation Procedures instructions for your DBMS.
|
|||
Enter the appropriate user information from the
Database Installation Procedures instructions for your DBMS.
|
|||
Use the following guidelines when you specify values for the COMPONENT_PATHS
data-value name:
silent.xml
installs both ALER and the examples: <data-value name="COMPONENT_PATHS" value="AquaLogic Enterprise Repository'/>" />
silent.xml
file:<data-value na
me="COMPONENT_PATHS" value="AquaLogic Enterprise Repository|AquaLogic BPM'/>" />
component/subcomponent
combination for each entry. For example: <data-value name="COMPONENT_PATHS
" value="AquaLogic Enterprise Repository/AquaLogic Enterprise Repository Plug-In for Eclipse" />
Note: | You can include the component/subcomponent of the products you want to install. |
COMPONENT_PATHS
data-value name in the silent.xml
file, the “complete” ALER product is installed. Note: | The installation program performs dependency checking to ensure that all components that provide functionality on which other components depend for proper operation are installed. These dependencies are visible during graphical and console mode installations. The same dependencies are enforced during silent installation: components on which other components depend are installed even if they are not explicitly referenced in a silent script. |
The following sample silent.xml demonstrate how to install ALER and configure a database.
<?xml version='1.0' encoding='UTF-8'?>
<bea-installer>
<input-fields>
<data-value name='BEAHOME' value='D:\dev\silentInstall\aler_albpm'/>
<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 (built-in Tomcat)'/>
<data-value name='APP_PATH' value='aler3'/>
<data-value name='WEB_PATH' value='aler3-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\aler_albpm\my\tomcat'/>
<data-value name='USER_INSTALL_DIR' value='D:\dev\silentInstall\aler_albpm\repository30'/>
<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='DBA_ALBPM_USER' value='system'/>
<data-value name='DBA_ALBPM_PASSWORD' value='aler30'/>
<data-value name='ALBPM_ADMIN_USER' value='system'/>
<data-value name='ALBPM_ADMIN_PASSWORD' value='manager'/>
<data-value name='FDI_USER_NAME' value='fd1'/>
<data-value name='FDI_USER_PASSWORD' value='fd1'/>
<data-value name='SERVER_USER_NAME' value='fd2'/>
<data-value name='SERVER_USER_PASSWORD' value='fd2'/>
<data-value name='CONFIGURE_WORKFLOW' value='yes'/>
</input-fields>
\</bea-installer>
<?xml version='1.0' encoding='UTF-8'?>
<bea-installer>
<input-fields>
<data-value name='BEAHOME' value='D:\dev\silentInstall\aler3'/>
<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 (built-in Tomcat)'/>
<data-value name='APP_PATH' value='aler3'/>
<data-value name='WEB_PATH' value='aler3-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\aler_albpm\my\tomcat'/>
<data-value name='USER_INSTALL_DIR' value='D:\dev\silentInstall\aler_albpm\repository30'/>
<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>
\</bea-installer>
For more information on launching the installation in silent mode, see Starting the Installation Program.
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.
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.
rem Execute the installer in silent mode
@echo off
aler30_win32.exe -mode=silent -silent_xml=mySilentXMLFile.xml -log=aler_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.
After completing the installation process, complete the following post installation tasks, as described in Post-Installation Instructions.