Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Connecting to an external Cassandra database through the Decision Data Store service

Updated on May 17, 2024

This content applies only to On-premises and Client-managed cloud environments

Start storing data in an external Cassandra database by configuring the Decision Data Store (DDS) service.

For more information about external Cassandra deployments, see Cassandra overview.

Before you begin: Define Pega Platform access to your external Cassandra database resources by creating Cassandra user roles with assigned permissions.

For more information, see Defining Pega Platform access to an external Cassandra database.

  1. In the header of Dev Studio, click ConfigureDecisioningInfrastructureServicesDecision Data Store.
  2. In the Decision data store nodes section, click Edit settings.
  3. In the Edit decision data store settings window, select the Use external Cassandra cluster check box.
  4. In the Cassandra host(s) field, enter a comma-separated list of Cassandra host names or IP addresses.
  5. In the Cassandra CQL port field, enter the Cassandra Query Language (CQL) port.
    To connect to the DDS node cluster by using third-party or custom tools to load or extract data through the Thrift protocol, enter 9160. To use the CQL3 Cassandra protocol, enter 9042.
  6. In the Cassandra user ID and Cassandra password fields, enter the credentials for the Cassandra user role that you created.
  7. In the Logging level list, select a logging level.
    For more information about Cassandra driver loggers, see the DataStax driver documentation.
  8. Click Submit.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us