" /> WDE Client Side Load Balancing - Genesys CTI User Forum

Author Topic: WDE Client Side Load Balancing  (Read 978 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
WDE Client Side Load Balancing
« on: November 14, 2020, 06:30:40 PM »
Advertisement
Hello

I am implementing the client side load balancing for WDE not not sure about the extra step when using TLS (see below from WDE deployment guide in bold).
I have set up a virtual CS Proxy containing options:
cluster.nodes.CS Proxy_1 (value=ip:port of CS Proxy 1)
cluster.nodes.CS Proxy_2 (value=ip:port of CS Proxy 2)
cluster.nodes.CS Proxy_3 (value=ip:port of CS Proxy 3)
cluster.nodes.CS Proxy_4 (value=ip:port of CS Proxy 4)

Not sure whether these need changing to value=autodetect or a new option or options to be created (presuming on the same application).
thanks.



[i]Creating a CS Proxy Cluster for Workspace
Purpose:

To enable Business Continuity for CS Proxy in Workspace.

Prerequisites

The Configuration Server Proxies are created as individual Application objects of type ConfigurationServer Provisioning Configuration Server proxies. They do not have any backup instance, to ensure that all instances are independent from each other.
Start

Create a Fake Host object and set its LCA port to 0 (zero). It will not be used at runtime.
Configure another Application object of type ConfigurationServer, to create a Virtual Configuration Server Proxy that represents the Configuration Server Proxy cluster. Set its host using the fake host and assign it a fake port. Host and Port are not used at run-time. The Virtual Configuration Server Proxy object, representing the Configuration Server Proxy cluster, is not monitored by SCS.
In the options of the virtual Configuration Server Proxy application, create in the Section interaction-workspace:
A key-value pair for each Configuration Server Proxy that composes the cluster where:
Key is cluster.nodes.<CS Proxy name>, where <CS Proxy name> refers to a static name, used internally for reference to that node.
Value is host:port that represents the Configuration Server Proxy host and port.
The cluster.environment-name option with a name that represent the configuration environment name.
Add a connection in the Workspace application to this Virtual Configuration Server Proxy.
If you are using Configuration Server Proxy version 8.5 or higher, in the [csproxy] section of each Configuration Server Proxy in the proxy cluster, set the value of proxy-cluster-name to the name of the Virtual Configuration Server Proxy object. For more information about this option, refer to the Framework Configuration Options Reference Manual.
TLS
[b]To enable TLS, if available, specify autodetect Configuration Server Proxy ports in the definition of the cluster nodes through options cluster.nodes.*.[/b][/i]