Pega is transitioning to Dynamic System Settings (DSS) to replace the traditional prconfig file, marking a significant shift in how configurations are managed. Custom settings in the prconfig file are no longer supported, making it a best practice to use DSS for all configuration settings. This blog post will focus on the benefits of DSS and how to transition from custom prconfig settings.
What are Dynamic System Settings?
Dynamic System Settings are instances of the Data-Admin-System-Settings class, used to define settings for both the system and applications. Unlike prconfig settings, DSS are stored in the database and can be automatically replicated across nodes. This means changes can be made without the need to undeploy and redeploy your system.
Why Move to DSS?
Ease of Management: DSS settings can be updated dynamically, without redeploying applications, making system administration more efficient.
Centralized Storage: Stored in the Pega Platform database, DSS settings are accessible to all nodes sharing the database, streamlining configuration management.
Enhanced Flexibility: DSS can override prconfig.xml settings, provided your Pega Platform database is configured correctly.
Identifying Custom prconfig Settings
Custom prconfig settings should be identified during the infrastructure assessment as they are not flagged by the Pega Cloud Readiness Tool. Here’s how to identify them:
Conduct a thorough review of your infrastructure.
Document all custom prconfig settings.3. Transition these settings to DSS as shown in the graphic below.
Creating a Dynamic System Setting
To create a DSS and change default system behavior, follow these steps:
In Dev Studio, navigate to Create > SysAdmin > Dynamic System Settings.
Enter a short description and the Owning Ruleset (e.g., Pega-RULES).
Specify the Setting Purpose with a detailed name.
Click Create and open.
Enter the appropriate value for the setting (e.g., true for a Boolean value).6. Click Save.
Configuring Dynamic System Settings
Using DSS for configuration is considered a best practice. For example, you can use DSS to configure fields for full-text search or to enable encryption among search nodes. DSS settings, stored in the Pega Platform database, ensure consistent configurations across all nodes.
Overriding prconfig.xml Settings
DSS can override prconfig.xml settings when the database is configured to retrieve data using JNDI, and the prconfig.xml file includes the following setting: `<env name="initialization/settingsource" value="merged" />`.
Understanding the Different Settings
Application Settings Rules: Use these to hold constant values that remain the same across all deployments.
Dynamic System Settings: Ideal for values that vary by site, such as URLs or port numbers.
Setting Rules: Use these in role-based access control when defining access roles and permissions.
Viewing System Configuration Settings
The System Settings Guide in Pega Infinity™ provides insights into configuration settings, helping you make informed decisions to enhance system performance.
Default Dynamic System Settings
Pega Platform™ allows you to create or update DSS instances to customize your implementation. DSS can control background processing features, manage memory thresholds, and much more.
Updating Dynamic System Settings
Active Instances: Use the prpcServiceUtils tool to update DSS values via a web service.
Database Connection: Automate updates by connecting directly to the database, ideal for stopped instances.
Java Methods: Applications can create, set, or query DSS instances using Java methods in the PublicAPI PRSystemSettings interface.
Adding MIME Types through DSS
Pega Platform supports new MIME-type mappings to meet diverse business requirements, ensuring your documents and files are correctly identified and processed.
Embrace the transition to Dynamic System Settings in Pega to simplify your configuration management and enhance system performance.
– Team Enigma Metaverse
Comments