Jump to: navigation, search

Cassandra Configuration

Starting in, Cassandra support is deprecated in Genesys Co-browse and Redis is the default database for new customers. Support for Cassandra will be discontinued in a later release.
Starting from 9.0.014.XXX, Co-browse Server does not support External Cassandra and therefore, does not supply Cassandra_Resource_Access_Point_900 application templates.

This page describes Cassandra configuration in Genesys Co-browse.

Overview of Cassandra Access and Management

Co-browse Keyspace Configuration

Keyspace specific options are kept in a dedicated configuration section, cassandraKeyspace Section. These options apply to external Cassandra.

External Cassandra Cluster Access Configuration

You can use a dedicated Cassandra Resource Access Point in Configuration Server to link a Co-browse server to an external Cassandra cluster.

Procedure: Create a Dedicated Cassandra Resource Access Point

Start of Procedure

  1. Import the templates Cassandra_Resource_Access_Point_900.apd and Cassandra_Resource_Access_Point_900.xml
    GCB 850 Cassandra Resource Access Point 1.png
  2. Using the imported application template from the previous step, create one Cassandra Resource Access Point(RAP) for each Cassandra node in an external Cassandra cluster that the Co-browse server needs to communicate with. Configure the following:
    1. For Host, specify the host of the external Cassandra Node
    2. Add a default port with the value of the rpc port the Cassandra node is using to listen for Thrift client connections. Optionally, specify rpc protocol for the port.
    3. Add a native port with the value of the CQL native port the Cassandra node is using to listen for CQL client connections. Optionally, specify native protocol for the port.

    GCB 850 Cassandra Resource Access Point 2.png

  3. Configure Cassandra RAP Connections:
    • Add Cassandra RAP connections to the Co-browse Cluster application object.
    GCB 850 Cassandra Resource Access Point 3.png
    Several connections with different Cassandra RAP applications ensures a redundancy of connections to the external Cassandra cluster. If one Cassandra node in the cluster fails, Co-browse server will be able to cooperate with the external Cassandra cluster through a different Cassandra node.
  4. End of Procedure

This page was last edited on November 27, 2021, at 05:19.
Comments or questions about this documentation? Contact us for support!