Jump to: navigation, search

Redundant (HA) Solution Control Servers

This section describes how to deploy redundant Solution Control Servers.

Redundancy

Redundant Solution Control Servers support only the Warm Standby redundancy type, with the addition that the data is synchronized between the primary and backup servers.

Deploying Redundant Solution Control Servers

This section describes how to install and set up redundant Solution Control Servers.

Recommendations

If you are installing the primary and backup Solution Control Servers on the same host computer:

  • Install them in different directories.
  • Specify a different port number for each server.

Prerequisites

  • Configuration Layer components are installed and running as described in Deploying Configuration Layer.
  • You are logged into Genesys Administrator.
Important
Once installed, the two Solution Control Servers must be started from the same account.

Installation and Configuration

Tip
(Optional) If the backup Solution Control Server is to reside on a remote Host, you can deploy it to that Host using Genesys Administrator Extension. For detailed instructions, refer to Genesys Administrator Extension Help.
1. Configure an Application object for the backup Solution Control Server. [+] Show steps
2. If you did not deploy the backup Solution Control Server remotely using Genesys Administrator, install it now.
3. Modify the primary Solution Control Server Application object to work with the backup Solution Control Server. [+] Show steps
4. If you installed the backup Solution Control Server on UNIX, check the run.sh file and modify it, if necessary, so the application can be started properly. [+] Show steps
5. Synchronize options and ports between the redundant Solution Control Servers.

Starting the Backup Solution Control Server

When starting a backup Solution Control Server, be sure to use the following command-line options:

-host The name of the host on which Configuration Server is running.
-port The communication port that client applications must use to connect to Configuration Server.
-app The exact name of the backup Solution Control Server Application object as configured in the Configuration Database.

For a description of the command-line parameters specific to Solution Control Server, refer to Solution Control Server.

Prerequisite

  • The run.sh file has been modified accordingly. See Step 4, above.

Procedure

  • To start from Genesys Administrator, refer to Starting and Stopping with the Management Layer.
  • To start manually, go to the directory in which the backup Solution Control Server is installed, and do one of the following:
    • To use only the required command-line parameters, type the following command line:
      sh run.sh
    • To specify the command line yourself, or to use additional command-line parameters, type the following command line:
      scs -host <Configuration Server host> -port <Configuration Server port> -app <backup Solution Control Server Application> [<additional parameters and arguments as required>]

Starting the Backup Solution Control Server on Windows

  • To start as a Windows Service, refer to Starting and Stopping with Windows Services Manager.
  • To start from Genesys Administrator, refer to Starting and Stopping with the Management Layer.
  • To start manually, do one of the following:
    • Use the Start > Programs menu.
    • To use only the required command-line parameters, go to the directory in which the backup Solution Control Server is installed, and double-click the file startServer.bat.
    • To specify the command line yourself, or to use additional command-line parameters, open the MS-DOS window, go to the directory in which the backup Solution Control Server is installed, and type the following command line:
      scs.exe -host <Configuration Server host> -port <Configuration Server port> -app <backup Solution Control Server Application> [<additional parameters and arguments as required>]
Retrieved from "https://docs.genesys.com/Documentation:FR:Dep:HASCS:8.5.1 (2019-05-22 05:35:29)"
This page was last modified on January 24, 2018, at 11:34.

Feedback

Comment on this article:

blog comments powered by Disqus