Jump to: navigation, search

Silent Setup

Genesys Silent Configuration allows for an automated electronic software distribution, also known as a silent setup. With silent setup, you do not have to monitor the setup or provide input via dialog boxes. Instead, the setup parameters are stored in a response file, and the silent setup runs on its own, without any intervention by the end-user.



An installation procedure for a server application differs slightly from an installation procedure for a GUI application. Both, however, require that you update a response file with the necessary parameters and then use it for the actual installation.

Genesys Silent Configuration works on both UNIX and Windows operating systems.

The following Framework components support Silent Setup installation:

  • Configuration Server
  • Message Server
  • Solution Control Server
  • T-Server
  • HA Proxy
  • Stat Server


Creating the Response File

A template for the response file, called genesys_silent.ini, is included in the Installation Package (IP) for each supporting component. This template file guides you through the task of entering required information, by providing the following information for each field:

  • A full description of the field.
  • If applicable, a description of valid values, either a range or a list.
  • If application, any conditions in which the parameters may not be used.

Open this file and provide values for all required fields by replacing the text contained in angle brackets (<>)(see the examples). Then save the file. By default, it is saved as genesys_silent.ini in the installation folder.

Subsequently, you can use the same response file any time you need to install an application with the configured parameters.

Sample Response File Entries (genesys_silent.ini)

The following is an example of the Genesys Configuration Server information section in the genesys_silent.ini for Configuration Server, with values entered for the required fields.

[+] Show sample entries

Running the Silent Installation

The silent setup program does not display a message if an error occurs. The status information for the silent installation is recorded in a file called (by default) genesys_install_result.log.

Use the appropriate command line to launch the Genesys Silent Configuration, depending on your operating platform as follows:


./install.sh -s -fr <full path to the setup response file> -fl <full path to the setup log file>

where:

      <full path to the setup response file>
            The full path to the setup response file. By default, install.sh looks for a response file called genesys_silent.ini in the same directory as install.sh.
 
      <full path to the setup log file>
            The full path to the setup log file. By default, genesys_install_result.log is generated in the same directory as the response file being used.

Example

.\install.sh -s -fr /home/user/genesys_silent.ini -fl /home/user/genesys_install_result.log


.\setup.exe /s /z"-s <full path to the setup response file> -sl <full path to the setup log file>"

where:

      <full path to the setup response file>
            The full path to the setup response file. By default, setup.exe looks for a response file called genesys_silent.ini in the same directory as setup.exe.
 
      <full path to the setup log file>
            The full path to the setup log file. By default, genesys_install_result.log is generated in the same directory as the response file being used.
Important
  • Enclose the entire string of parameters -s <full path to the setup response file> -sl <full path to the setup log file> in double quotation marks.
  • Do not enter a space between the /z parameter and its value.

Example

.\setup.exe /s /z"-s c:\win\genesys_silent.ini -sl c:\win\genesys_install_result.log"

Silent Setup Log File

The silent setup program prints installation results into a setup log file. By default, the results file is named genesys_install_result.log, and is stored in the same folder as genesys_silent.ini.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 11 April 2018, at 12:02.