Skip to main content


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

Configuring the secondary data center nodes

Updated on May 17, 2024

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

Enable communication and data replication between the primary and secondary data centers by updating the prconfig.xml file for each node in the secondary data center, and starting the Decision Data Store service.

  1. Update the prconfig.xml file with the following configuration:
    <!-- list all available Cassandra data centers -->
    <env name="dnode/cassandra_datacenters" value="DC1,DC2"/>
    <!-- specify current data center -->
    <env name="dnode/cassandra_datacenter" value="DC2"/>
    <!-- list one or more IP addresses from DC1 -->
    <env name="dnode/extra_seeds" value="IP_FROM_DC1.."/>
    where:
    • extra_seeds – Lists other data centers that connect with this data center. This setting ensures clustering and replication across all data centers when Pega Platform creates the internal Cassandra cluster.
    For more information, see Changing node settings by modifying the prconfig.xml file.
  2. Enable the Decision Data Store service by adding secondary data center nodes as part of that service.
Result: When you enable the secondary data center, the Services landing page displays both the primary and secondary data center nodes. The nodes from the current data center have their proper names. Each data center recognizes the node from the other data center as an EXTERNAL NODE.
What to do next: Configure additional services, such as the Adaptive Decision Manager, Data Flow, Real-time Data Grid, and Stream, as required by your business use case. For more information, see Enabling decision management services

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us