Local Control Agent 8.5.x Release Notes
|Release Date||Release Type||Restrictions||AIX||Linux||Solaris||Windows|
This release contains the following new features and enhancements:
- Throttling can be applied to log outputs to prevent a log queue from growing to a size that could impact normal operation of an application.
- The LCA configuration file (lca.cfg) is now created when LCA is deployed; you do not have to create it manually.
- Local Control Agent supports a new virtualization platform. Refer to the Genesys Supported Operating Environment Reference Guide for more information.
This release contains the following resolved issues:
On the RHEL platform, LCA now correctly handles the situation when an application is started with the Management Layer, even if the working directory of the application object is incorrect. Previously, if a user tried to start the application from a GUI application but the working directory configured in the application's properties was incorrect, LCA disconnected from Solution Control Server. (MFWK-15306)
The Genesys Interaction Server application can now be stopped successfully by the Management Layer. Previously, it could be started successfully, but could not be stopped. (MFWK-14531)
TLS connections to a Genesys server running Windows no longer fail if the security certificate is generated using a tool other than Windows certificate services and then manually imported into Windows. Previously, if you used something other than Windows certificate services and manually generated the certificate, the CERT_TRUST_REVOCATION_STATUS_UNKNOWN validation error was generated, and the TLS connection to the Genesys server failed. (MFWK-14166 / ER# 324547671)
LCA no longer detects the application as having stopped responding if you significantly decrease the value of the heartbeat-period option for an application in your configuration that is configured to use hangup detection. Previously, LCA sometimes considered the application to have stopped responding. (MFWK-14153 / ER# 324295707)
No special procedure is required to upgrade to release 8.5.000.09.