For Co-browser Server clusters, every Co-browse Server in the cluster generally plays the same role as the others, except some embedded Cassandra nodes act as seed nodes. This means that to see consistent behavior on the cluster, regardless of which server serves requests, all Co-browse Servers should have the same options set in their application objects in Configuration Server. The rule of thumb is to configure the cluster servers the same, unless it is absolutely necessary to do otherwise (for example, a port is busy on a machine). This simplifies maintenance of production deployments.
You can set the following configuration options on your Co-browse Server application in Genesys Administrator:
Co-browse Plug-in for Interaction Workspace
You can set the following configuration options for the Co-browse plug-in on your Interaction Workspace application in Genesys Administrator:
This page was last modified on March 1, 2017, at 16:51.