Page tree

Skip to end of metadata
Go to start of metadata

A silent installation is one in which you run the installation program from a command line, enabling you to install the product in situations where the operating system of the target computer does not support a graphical user interface (UI). Choose the silent installation method if you want to:

  • Run the product installer in the background instead of running it interactively.
  • Install on a remote computer that cannot display a graphical UI.
  • Maintain consistent installation configuration values across multiple computers.

You launch installation program from the command line and specify a preconfigured install configuration template file (config file) that contains details for all the parameters required to install the product. You can create a single config file and use it for multiple installations.

Sample config files that contain default parameters for installing the product in different configurations are included with the product install package, and you can modify them according to your installation requirement or scenario.

The installation scenario that you choose determines the config file that you need when running the installation program in silent mode.

Before you begin

  • You must have encrypted the passwords.
  • You must have prepared the config files for the Application Server installation.

Encrypting passwords

You will need to type the database administrator password and the schema passwords in an encrypted form in the config file. Encrypt these passwords by performing the following:

  1. Change to the directory where you extracted the downloaded installation files. Example: TSCO_temp/BCO/Disk1.
  2. Run the command:

./BCOEncoder.sh <password>
Note down the encrypted password displayed on the screen. Example: DES\:097133405e7ea7a6bcc58bbe70ece4c2.

Configuration files

After choosing one of the following installation scenarios, configure its corresponding configuration files, and then perform the installation. 

The configuration file links access descriptions about the properties in the configuration file.

Configuration fileConfiguration/Installation type
Scenario 1: Typical installation
BCO_FIRST_SERVER_TYPICAL.txtTypical install on the First Server: Installs the Application Server + ETL Engine – All components
Scenario 2: Scenario 1 + Installing components across multiple servers
BCO_FIRST_SERVER_CUSTOM_AS_FRONTEND_WEB.txtCustom installation of the First Application Server.
BCO_ADDITIONAL_SERVER_AS_BACKEND_DH_PS.txtInstalls the Additional Server: Install the Data Hub + Primary Scheduler + ETL Engine.
(Valid only if the First Server is installed using Configuration 2)
Scenario 3: Scenario 1 + Install TrueSight Capacity Optimization with an additional ETL server
BCO_ADDITIONAL_SERVER_EE.txtInstalls an Additional ETL Engine Server over a LAN connection. (Direct connection deployment)
Scenario 4: Scenario 1 + Install TrueSight Capacity Optimization with an additional remote ETL server
BCO_ADDITIONAL_SERVER_EE.txtInstalls an Additional ETL Engine Server over a LAN connection. (Direct connection deployment)
Scenario 5: Scenario 1 + Install TrueSight Capacity Optimization with an additional primary scheduler that can be used to run reports
BCO_ADDITIONAL_SERVER_AS_PS.txtInstalls the Primary Scheduler on the Additional Server.
Scenario 6: Scenario 1 + Install TrueSight Capacity Optimization with an additional web server
BCO_ADDITIONAL_SERVER_AS_WEB.txtInstalls the Additional Web Server.

1 Comment

  1.