Configuration Server Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features or enhancements:
- Support of MS SQL Always On with MultiSubnet Listener for disaster recovery and business continuity scenarios involving the Configuration Database. This support is enabled using the following configuration option, set in the Configuration Server configuration file.
- [<Configuration Database section>]
- Default Value: No
- Valid Values: Yes, No
- Changes Take Effect: At restart of Configuration Server
- Enables multi-subnet failover using MS SQL 2016 and later for disaster recovery and business continuity scenarios involving the Configuration Database. When set to Yes, subnet failover is supported; when set to No, subnet failover is not supported.
- For more information about this feature and the new option, refer to MS SQL Always On with MultiSubnet Listener in the Framework Database Connectivity Reference Guide.
- The performance of the audit process has been improved when collecting audit records from larger databases. A filter has also been added to extract records from a large set of results.
- To support MS SQL Server Native Client 11.0 on Windows, an alternate version of the dbclient_mysql file is provided in the dbclient_next subfolder. During installation, you must take a backup of the default version of the dbclient_msql file from the default installation folder and replace it with the dbclient_msql file from the dbclient_next folder, and then restart the application.
This release contains the following resolved issues:
The Configuration Server Application Template now correctly contains default options. Previously, there was an error in the metadata file that contained the default options, and Genesys Administrator was unable to load the file. As a result, no options appeared in the Template. (MFWK-20192)
In a distributed Configuration Server environment, the master Configuration Server no longer terminates unexpectedly when it does not receive a response from the Configuration Database within the time specified by the [<Configuration Database section>].response-timeout option. Instead, Configuration Server attempts to restore the connection, and cancels any uncompleted requests.
Previously in this scenario, if a large number of submitted requests remained in the queue waiting for a response, a database restart caused the connection between Configuration Server and the database to be lost, after which Configuration Server sometimes terminated unexpectedly.
No special procedure is required to upgrade to release 126.96.36.199.