8.5.100.25
Solution Control Server 8.5.x Release Notes
| Release Date | Release Type | Restrictions | AIX | Linux | Solaris | Windows |
|---|---|---|---|---|---|---|
| 08/22/17 | General | X | X | X | X |
Helpful Links
Releases Info
Product Documentation
Genesys Products
What's New
This release contains the following new features or enhancements:
- Support for the Windows 2016 64-bit operating system. See the Supported Operating Environment: Framework page for more detailed information and a list of all supported operating systems.
- As of 9/26/17, Solution Control Server supports the Microsoft Hyper-V Server 2016 virtualization platform. Refer to the Supported Operating Environment: Display by Product, Operating System, and Other page for more detailed information and a list of all supported virtualization platforms.
Resolved Issues
This release contains the following resolved issues:
SCS now attempts to reestablish a failed connection with an SMTP server when the the time interval specified by the following new configuration option smtp-reconnect-timeout in the [mailer] section of the SCS application object expires. Previously, when an SMTP server connection failed, SCS did not reconnect until there was a clearance alarm, or another alarm that triggered a connection to be established.
smtp-reconnect-timeout
Default value : 60000 (ms)
Valid values: 0 or any positive integer
Changes take effect: After restart
This option specifies the time, in ms, for which SCS will wait to reconnect to the SMTP server when there is outstanding mail. If this option is set to zero (0), the feature is disabled. (MFWK-18606)
If SCS is configured with hangup detection, it now sends heartbeat messages to LCA in all cases. Previously, if a server running on the same host as LCA was in a race condition, SCS did not always send heartbeat messages to LCA when LCA was restarted. (MFWK-18377)
When the connection between SCS and Message Server is secured using TLS, logs generated by SCS use the secured connection and the secure port. Previously in this scenario, the SCS logs used the secure connection but the default port. (MFWK-17818)
When TLS is enabled between SCS and LCA, SCS now processes the data sent and received through sockets. Previously in this scenario, some data was sent or received before TLS was established, and the data was not processed properly. As a result, SCS generated the error message LCALIB: Can't send to socket. (MFWK-17746)
Upgrade Notes
No special procedure is required to upgrade to release 8.5.100.25.