Configuration Options
Contents
Important
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.Co-browse Server
You can set the following configuration options on your Co-browse Server application in Genesys Administrator:
Section Name | Options |
---|---|
cbdb Configure Cassandra to support the Co-browse Server cluster |
cassandraClusterName |
cbdb-retention-policy Configure the data retention policy for Cassandra |
|
cross-origin Configure list of websites allowed to access the Co-browse server |
|
chat Settings for chat |
connectionTimeout |
cluster Configure the Co-browse Server cluster |
|
cometd Settings for CometD |
|
forward-proxy Configure a forward proxy |
|
log Configure the logs generated by the Co-browse Server |
all |
security Enable TLS on connections with other Genesys servers |
|
session Configure DOM restrictions |
|
slave Configure localization for the slave UI |
|
static-web-resources Configure static web resources |
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:
Section Name | Options |
---|---|
cobrowse Configure the Co-browse Plug-in for Interaction Workspace |
url |
This page was last edited on September 28, 2015, at 13:01.
Comments or questions about this documentation? Contact us for support!