Jump to: navigation, search

Cassandra Configuration

This page describes Cassandra configuration in Genesys Co-browse.

Overview of Cassandra Access and Management

  • Co-browse server can be interconnected with an external Cassandra cluster.
  • Co-browse server uses a new approach to configuring embedded Cassandra.
  • Genesys Co-browse splits the configuration of the embedded Cassandra node and the Co-browse keyspace.
  • Genesys Co-browse configuration is now similar to configuration of GWE and UCS.
  • Co-browse uses Cassandra 2.X. For supported versions of Cassandra, see Genesys Co-browse in the Supported Operating Environment Reference Guide.

Co-browse Keyspace Configuration

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

Embedded Cassandra Configuration

Starting in Genesys Co-browse 8.5.0, Embedded Cassandra mode was deprecated; support for this mode will be discontinued in a future release of 9.0.x.

Co-browse server may act as a Cassandra node. The options to configure the embedded Cassandra service changed in 8.5.0 and higher. These options are in a dedicated section, cassandraEmbedded.

Cassandra Cluster Access Configuration

Embedded Cassandra Access Configuration

When embedded Cassandra is enabled, the Co-browse server will always connect to the embedded Cassandra node when it needs to read or write data in the database. No additional configuration needed.

External Cassandra 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.
    • Set the enabled option to false in the cassandraEmbedded section of 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

    Configuring a Cassandra Cluster

    For more information on configuring a Cassandra Cluster, see:

    Configure a Cluster of Co-browse Servers
This page was last modified on March 2, 2018, at 10:55.


Comment on this article:

blog comments powered by Disqus