Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Config setting added in DSS are not reflecting in configs

SA-53636

Summary



User has added setting in DSS and restarted the server. But the changes are not reflecting in System Management Application (SMA).


Error Messages



Not Applicable


Steps to Reproduce



1. Create DSS as below:

OwningRuleset                              Setting Purpose                                                      Value
Pega-Engine database/databases/PegaDATA/dataSourceReadOnly                          java:comp/env/jdbc/PegaRULESReadOnly
Pega-Engine database/databases/pegarules/datasourcereadonly                              java:comp/env/jdbc/PegaRULESReadOnly
Pega-Engine prconfig/collections/mru/propertyreference/instancecountlimit               130000
Pega-Engine prconfig/alerts/database/blobsizeread/threshold                                     10
Pega-Engine prconfig/alerts/database/blobsizewritten/threshold                                  10


2. Restart the application server.
3. Go to SMA and verify the DSS.  The values are not reflected under Configuration Management.


Root Cause



An issue in the custom application code or rules:

DSS setting purpose is not configured properly and setting related to PegaRULES Db connection configuration is not allowed in DSS 
because "Data-Admin-System-Settings.ValidateKeysContent" Step 7 do not allow PegaRules connection in DB as DSS.

Resolution


Perform the following local-change: 

1. Add the below DSS in prconfig.xml file.

Pega-Engine   database/databases/pegarules/datasourcereadonly                         java:comp/env/jdbc/PegaRULESReadOnly

2. Restart the server after doing the above modifications. See the changes: 5 DSS in Administration > Configuration Management in SMA( 4 DSS with have source as DSS and 1 will have prconfig).

OwningRuleset                         Setting Purpose                                                                                           Value 
Pega-Engine         prconfig/database/databases/PegaDATA/dataSourceReadOnly/default              java:comp/env/jdbc/PegaRULESReadOnly 
Pega-Engine         prconfig/collections/mru/propertyreference/instancecountlimit/default                              130000 
Pega-Engine         prconfig/alerts/database/blobsizeread/threshold/default                                                      10 
Pega-Engine         prconfig/alerts/database/blobsizewritten/threshold/default                                                   10
Pega-Engine   database/databases/pegarules/datasourcereadonly                         java:comp/env/jdbc/PegaRULESReadOnly



 

 

Published July 23, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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 Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us