Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.


Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Distributed Solution Control Servers

Multiple Solution Control Servers operating in Distributed mode (referred to as Distributed Solution Control Servers) distribute management-related tasks among the sites in a distributed enterprise that uses a single Genesys Configuration Database.

What are Distributed Solution Control Servers?

In these installations, each SCS controls its own subset (defined by you) of the Hosts, Applications, and Solutions, and communicates with the others through a dedicated Message Server.

Specifically, a Distributed Solution Control Server performs the following functions:

  • Performs the same functions of monitoring, control, alarm detection, and alarm processing as the SCS in non-Distributed mode, but on a subset of Hosts, Applications, and Solutions explicitly assigned to this SCS in the Configuration Database.
  • Communicates all the updates to statuses of the assigned objects to other Distributed Solution Control Servers, using a dedicated Message Server.
  • Receives notifications about updates to the status of non-assigned objects (that is, objects assigned to other Solution Control Servers) from Message Server.
  • When receiving a control command on an object not assigned to this SCS, forwards this command via Message Server to the appropriate SCS.

Because Distributed Solution Control Servers communicate with each other, they all have the same information about all hosts, applications, and solutions. Thus, you can connect the interface object associated with Genesys Administrator to any Distributed SCS and monitor and control the whole environment as a single entity (given appropriate permissions). When a Distributed SCS receives a control command for an object that this SCS does not control, it forwards this command to the appropriate SCS and passes any further notifications back to the requestor.

Using Distributed Solution Control Servers helps you resolve some problems common to distributed installations:

  • It eliminates false switchovers that occur when SCS disconnects from LCA at a remote site because of the slow network connection between sites or because of temporary network problems.
  • It prevents a single point of failure. A failure of one Distributed SCS only means a temporary loss of control over a subset of Hosts, Applications, and Solutions; other Distributed Solution Control Servers continue to control the rest of the environment.

Limitation

In distributed mode, Solution Control Server reports host information for only the host it controls when Genesys Administrator or Genesys Administrator Extension (GAX) is connected to SCS. It does not provide host information for other hosts that are controlled by other Solution Control Servers in distributed mode.

For example, assume the following distributed SCS environment:

host_a
host_b
SCS_a is located on, and controls, host_a
SCS_b is located on, and controls, host_b
GAX can be connected to either SCS_a or SCS_b

When GAX is connected to SCS_a, it reports host information for only host_a.
When GAX is connected to SCS_b, it reports host information for only host_b.

Deploying Distributed Solution Control Servers

Warning
  • Do not use Solution Control Servers in Distributed and non-Distributed modes simultaneously within the same Configuration environment. If you plan to use Distributed SCS in your installation, turn on Distributed mode for all Solution Control Servers you install.
  • When using Distributed Solution Control Servers, always ensure that each Solution Control Server, either by itself or as part of a high-availability pair, is running on the host which it controls. Failure to do so can, in some cases, result in unpredictable behavior of the Solution Control Servers in the Distributed configuration. For example, different Solution Control Servers may start competing for control over Applications on the Host.
  • When working with applications in HA pairs, the same distributed SCS must be configured to control both applications working in each HA pair.
  • If you are planning to use an SNMP Master Agent MA with your Distributed SCS environment, use only one SNMP MA (or one HA pair, if required). The one SNMP MA can access and handle all traps and queries from all of the distributed servers. Deploying multiple SNMP Master Agents in a distributed system might lead to duplicate alarms and traps being generated.
1. Configure Distributed Solution Control Servers in Distributed mode. [+] Show steps
2. Divide your configuration environment between the Solution Control Servers. [+] Show steps
3. Configure a dedicated Message Server through which the Distributed Solution Control Servers will communicate with each other. [+] Show steps
4. (Optional) Configure a Message Server for centralized logging at each site with Distributed Solution Control Servers. [+] Show steps
5. (Optional) Configure redundant Application objects for Distributed Solution Control Servers. [+] Show steps
6. After you are finished with the configuration tasks, physically install all instances of Solution Control Server and Message Server to match the configuration.

Starting Distributed Solution Control Servers

Important
Starting a Solution Control Server in Distributed mode requires a special license. Refer to the Genesys Licensing Guide for more information.

Start each Distributed Solution Control Server in the same way as you would start a non-distributed SCS. See Starting SCS and Starting a Backup SCS for more information.

This page was last edited on May 5, 2017, at 18:26.

Feedback

Comment on this article:

blog comments powered by Disqus