Skip to main content

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

Configuring an internal Cassandra database

Updated on May 17, 2024

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

Start storing data in an internal Cassandra database by creating a Cassandra cluster and configuring the Decision Data Store (DDS) service.

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

  1. Create a Cassandra cluster by assigning the DDS node type to at least three Pega Platform nodes.
    Tip: To increase the volume of data and the volume of interactions that you process, assign the DDS node type to a higher number of nodes.

    For more information, see Assigning node types to nodes for on-premises environments.

  2. In the header of Dev Studio, click ConfigureDecisioningInfrastructureServicesDecision Data Store.
  3. In the Decision data store nodes section, click Edit settings.
  4. In the Edit decision data store settings window, clear the Use external Cassandra cluster check box.
  5. In the Cassandra CQL port field, enter 9042.
  6. In the Cassandra user ID and Cassandra password fields, enter dnode_ext.
  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.
What to do next: Configure the Cassandra cluster that you created. For more information, see Configuring the Cassandra cluster.
  • Previous topic Connecting to an external Cassandra database through the Decision Data Store service
  • Next topic Configuring the Adaptive Decision Manager service

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