Jump to: navigation, search

Configuration Server Release Notes

Configuration Server is part of 9.x starting in
Release Date Release Type Restrictions AIX Linux Solaris Windows
11/30/18 General X X X X

Helpful Links

Releases Info

Product Documentation

Management Framework

Genesys Products

List of Release Notes

What's New

This release contains the following new features or enhancements:

  • Support for the following operating systems:
    • Oracle Linux 7 with Unbreakable Enterprise Kernel (UEK) 4.x
    • SUSE Linux Enterprise 12
    See the Framework page in the Genesys Supported Operating Environment Reference Guide for more detailed information and a list of all supported operating systems.
    For Oracle and SUSE Linux operating systems, select RedHat Enterprise Linux as host OS type while creating a host object in Genesys Administrator or Genesys Administrator Extension.
  • Configuration Server now supports FIPS 140-2 compliance for authentication using LDAP. For more information, see Enable FIPS 140-2 compliance.
  • Staring with this release, Configuration Server supports installation on all minor releases of Red Hat Enterprise Linux 7.x operating system.

Resolved Issues

This release contains the following resolved issues:

Configuration Server no longer terminates unexpectedly upon startup if the Description field in a predefined object (such as Alarm Condition or Time Zone) is cleared. (MFWK-21190)

Configuration Server now updates the correct username in the history logs when a user makes configuration changes through a writable Configuration Server Proxy. Previously in this scenario, Configuration Server incorrectly updated the username as "default". (MFWK-20585)

Configuration Server running in backup and proxy mode can now automatically recover from situations when the master server stops sending data while this instance is starting or reloading from it. Previously in this scenario, the server may get stuck and requires a restart (after master server restored its operation or network connection recovered).

To adjust timeout after which the server considers the master server as non-responsive, use the primary-master-response-timeout option in the main section of the configuration file used by each master Configuration Servers in the High Availability pair (for example, the [confserv] section in confserv.cfg for server configured as "confserv"), or use the command line option -primary-master-response-timeout <value_in_secounds> when starting Configuration Server in proxy mode. By default, the server considers master server as non-responsive during load/reload phase in 600 seconds.

Upgrade Notes

No special procedure is required to upgrade to release

Supported Languages

See Release 8.5.x Translation Support.

This page was last modified on September 18, 2019, at 03:29.


Comment on this article:

blog comments powered by Disqus