Jump to: navigation, search

Startup Options in Configuration File

These options are located in the Configuration Server configuration file.At first startup of the master Configuration Server, the configuration file is named confserv.cfg (on Windows) or confserv.conf (on UNIX) by default. This file can be renamed as required, but must be specified by the -c command-line option at startup. If there is a Configuration Server section in the configuration file other than confserv, you must use the -c <section> parameter in the command line to make sure that Configuration Server is using configuration settings from that section. The section name must also match the name of the Configuration Server object.

  • If you have a configuration file and/or a Configuration Server section with a name other than the default, you must specify the parameters -c <config file name> and/or -s <Configuration Server section name> in the command line when starting this instance of Configuration Server.This is in addition to any other command-line options that you want to use, whenever you start Configuration Server or any command-line utility modes provided by Configuration Server.
  • Options in the Configuration Server and dbserver sections are always read from the configuration file and re-saved to the Configuration Database at each startup. Values from the database are ignored. Genesys Administrator restricts the editing of such options in runtime. Some options in these sections are exempt from this rule, such as the port option. See the option descriptions for details.
  • Options in the [log] section of the configuration file apply up to the point that Configuration Server is fully initialized. After initialization is complete, log options stored in the Configuration Database are applied. You can still use the [log] section in the configuration file to change options that are in effect during startup, but be aware that they will be overridden with those in the database.
This page was last edited on January 31, 2020, at 14:32.
Comments or questions about this documentation? Contact us for support!