Configuration Server 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
Improved Connections Between Configuration Servers: You can now set a timeout for a client to expect a TCP success or failure response from the server to which it is connecting. If the timeout expires, all pending connection requests are cancelled, enabling the connection to be made. Without the timeout, the connecting client might eventually stop trying to reconnect, and then stop responding completely because of network issues. This timeout applies to the following connections:
- Primary or backup Configuration Server Proxy connecting as a client to primary master Configuration Server
- Backup master Configuration Server connecting as a client to primary master Configuration Server
- Backup Configuration Server Proxy connecting as a client to primary Configuration Server Proxy
To set the timeout, use the new command-line parameter -cfglib-conn-async-tmout (default 20 seconds). For the backup master Configuration Server, you can use this command-line parameter or you can set the new option cfglib-conn-async-tmout (default 20 seconds) in the configuration file instead. The value of this option overrides that set by the command-line parameter. For more information, refer to the Framework Deployment Guide for the new command-line parameter, or to the Framework Configuration Options Reference Manual for the new option.
Support for deployment of Genesys Applications in single sign-on environments: Configuration Server now supports simplified deployment of Genesys Administrative Applications in environments that use single sign-on. Refer to application-specific documentation to determine if the application supports this, and if so, to confirm deployment requirements.
This release contains the following resolved issue:
A master Configuration Server no longer stops responding soon after startup with a newly initialized Configuration Database. Previously in this scenario, if the configuration file contained an invalid option with a key exceeding 64 bytes in length, the server stopped responding shortly after startup. (MFWK-18513)
No special procedure is required to upgrade to release 184.108.40.206.