Jump to: navigation, search

Local Control Agent (LCA)

To enable the Management Layer to control the startup and status of applications and solutions, and manage application failures, you must install an instance of Local Control Agent on every computer that is to run either Genesys server applications or third-party server applications you want to control with Management Layer.

Genesys Deployment Agent

Support is discontinued for Genesys Deployment Agent (GDA) in LCA release and later.

The Genesys Deployment Agent (GDA) is a component of LCA that Genesys Administrator Extension uses to remotely deploy Installation Packages to remote hosts in the network. See the Genesys Administrator Extension Deployment Guide for more information about this functionality.

GDA is not installed by default in release 8.5.1. You can still choose to install it as part of LCA installation (see Installing Local Control Agent below) if you want to use the remote deployment functionality of Genesys Administrator Extension.

Notes on Configuring the LCA Port

  • The LCA port must be set to a value of 2000 or greater. When the LCA port is specified within the range of 1-1999, LCA starts on port number 4999 (default value).
  • If the LCA port value is changed in the Host configuration while Solution Control Server (SCS) is connected to LCA, SCS does not disconnect from and reconnect to LCA; instead, the new LCA port value takes effect after LCA restarts.
  • If you change the LCA port value for the LCA installed as a Windows Service, you must also change the LCA port number in the LCA startup parameters in the Registry Editor. The LCA Registry Key is located at:
    The value must have the following format:

       <full path>\lca.exe <LCA port number> -service <lca_service_name>

    Change the LCA port number to the current value.

Installing Local Control Agent

All running LCA processes must be stopped before installing another LCA.

[+] Installation Steps

LCA Log Options

Local Control Agent supports the unified set of log options (common log options) to allow precise configuration of log output. For a complete list of unified log options and their descriptions, see the "Common Log Options" section of the Framework Configuration Options Reference Manual.

If you do not specify any log options for LCA, the default values apply. To specify log options for LCA, modify the lca.cfg configuration file that was created during LCA deployment, and is located in the same directory as the LCA executable. The LCA configuration file has the following format:

<log option name> = <log option value>
<log option name> = <log option value>

A sample LCA configuration file is available in the Framework Configuration Options Reference Manual.

Configuring ADDP Between Solution Control Server and Local Control Agent

Advanced Disconnection Detection Protocol (ADDP) is enabled automatically between Solution Control Server (SCS) and LCA. By default, SCS generates polling messages to LCA. If SCS does not receive messages from LCA within this interval, SCS sends a polling message. A lack of response to the polling message from LCA within the same time period is interpreted as a loss of connection.

If you want to change the ADDP timeout between SCS and LCA, configure the addp-timeout option. If you also want to enable LCA polling messages to SCS, configure the addp-remote-timeout option. Both of these options are set in the annex of the Host object configured for the computer on which LCA runs. For detailed instructions on specifying these options, refer to the Framework Configuration Options Reference Manual.

To avoid false disconnect states that might occur because of delays in the data network, Genesys recommends setting the ADDP timeouts to values equal to or greater than ten seconds.

For more information about ADDP, see Advanced Disconnection Detection Protocol.

This page was last edited on May 3, 2019, at 09:23.
blog comments powered by Disqus