Skip Headers
Oracle® Communications Order and Service Management Installation Guide
Release 7.2.2

Go to Documentation Home
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
Go to next page
PDF · Mobi · ePub

8 Installing OSM in Silent Mode

You can install Oracle Communications Order and Service Management (OSM) in two modes: interactive mode or silent (unattended) mode. This chapter provides instructions on installing OSM in silent mode.

The silent installation procedure enables you to perform a non-interactive installation of OSM. Installation settings are pre-configured in the configuration files install_cfg.xml and installOptions.txt. The installer runs in the background without requiring any user intervention.


Silent installation configuration files are created during an interactive installation of OSM when the SDK samples and OSM Server are selected for installation. Configuration files created on one operating system can be used on other operating systems.

During installation, save the configuration in the Save Configuration screen of the OSM installer. This saves a copy of the install_cfg.xml file in the location you specify. In addition, if you have installed the SDK, samples of both configuration files are stored in the OSM_home/SDK/Samples/installation folder.


The prerequisites for a silent installation are the same as an interactive installation:

  • Oracle Database is correctly set up with tablespaces created for OSM, and is running.

  • Oracle WebLogic Server is running.

  • Third-party plug-ins Saxon and JBoss are available on the target machine.

Configuring the installOptions.txt and install_cfg.xml Files

For a silent installation to run correctly, the installOptions.txt and install_cfg.xml files must be customized to reflect the specifics of your target system, and to contain your preferred installation options. These options are analogous to what you would select in an interactive installation.

Configuring the installOptions.txt File

This file contains installation options. The parameters in this file can also be specified on the command line if desired, although it is not recommended to specify all of them on the command line. However, if you wanted to have a standard file with set options and to specify, for example, the software and log locations on the command line, that would be possible. If an option is specified both in the file and on the command line, the command-line option will take precedence over the value in the file.

Further information about the options below is specified in the sample file.

  1. Set the name of the XML file containing the installation configuration, for example, install_cfg.xml. This file should be located in the same directory as the installOptions.txt file.

  2. Set the location for the OSM product to be installed. Use double-quotes if the directory contains spaces.

  3. Set the location of the installation log. You need to monitor this file during the silent installation, to know if the installation is progressing successfully.

  4. The Remove option instructs the OSM Installer to always remove files that are modified after installation while performing uninstallation. These are default settings.

  5. The Replace option instructs the OSM Installer to always replace the files with the newer version. These are default settings.

  6. Choose the Setup type, either Typical or Custom.

  7. Check whether the database schema is selected for installation. If you have not created your database schema already, ensure you select it here.

  8. Check whether the OSM server feature is selected for installation. Select it if you want to install the OSM server now.

  9. Select other components that you want to install, such as Administrator, or SDK tools and samples.


    Two of these other components, Database Manager Utility and Administrator, are Windows-only components that do not work on UNIX or Linux environments.
  10. Save and close the file.

Configuring the install_cfg.xml File

Customize the install_cfg.xml file to reflect your OSM, Oracle WebLogic, and Oracle database parameters. For details about install_cfg.xml parameters, see "Silent Installation install_cfg.xml Parameters".

You can obtain this information from your WebLogic and Oracle database administrator.

Performing a Silent Installation

  1. Navigate to the directory where the installation executables are placed.

  2. Do one of the following:

    • On Oracle Linux and Red Hat Enterprise Linux, execute the command:

      ./InstallLinux.bin -options installOptions.txt -silent
    • On Oracle Solaris, execute the command:

      ./InstallSparc.bin -options installOptions.txt -silent
    • On IBM AIX, execute the command:

      ./InstallAix.bin -options installOptions.txt -silent
    • On Windows, execute the command:

      Install.exe -options installOptions.txt -silent


      For UNIX systems, you can optionally specify the location of the OSM log file that logs all OSM installer activity. Use the following attributes when running the silent installation command:
      -is:tempdir temp_directory is:log log_file.log

      where temp_directory is the location of the log file and log_file is the log file name.

      For example:

      ./InstallLinux.bin -is:tempdir /tmp/asap -is:log asaplog.log -options installOptions.txt -silent

You can monitor the progress of the installation by viewing the InstallLog.txt file. If a problem occurs, the installation stops and the reason for the failure is written to the InstallLog.txt file. Based on the error, you may have to edit the installOptions.txt file and restart the installation.

Once the Installation is complete, you can verify the installation the same way you do for the interactive installation. See "Installing OSM in Interactive Mode" for more information.