Question
Optum
US
Last activity: 19 Jul 2016 11:04 EDT
Connector Threshold Setting in DDS is not matching the PRConfig setting
Hello All: Thanks in Advance for Reading!
I have made the following DDS setting. It is to set the Threshold Value, for Connector Total Request Time to 5000s.
We are doing this to suppress the multiple messages coming to AES, and Alert Log Files, for the Pega0020 Alert.
However, the setting in PRConfig reads the following. It is not getting updated with the updated Threshold.
So, we are seeing numerous message still coming, as it is only set as 100s
Is it because the Source is "prconfig". Should the source be "Dynamic System Setting"??
If so, how do I change that??
Accepted Solution
PEG
IN
It seems you have same setting set in prconfig. Could you check the prconfig.xml and change accordingly?
Optum
US
Hello Gangababu:
I am trying to manage the setting via the DDS setting. That should be a viable option.
I do not want to go through the logistics necessary, to update the prconfig file, directly on the server.
PEG
IN
I think you have this setting already present in prconfig.xml. You could observe the same in SMA. In source it shows prconfig.
As far as I know prconfig setting takes precedence than DSS. Could you please cross verify whether you do have any setting in prconfig.xml or not.
Just for your reference
Hope this helps!
Optum
US
Hello Kevin:
I am a little confused by this?? It looks like the exact same spelling, with two T's??
Please note: Even though I have typed the setting in camel case, with the proper punctuation as you have listed, Pega turns the punctuation into all lower case.
NJ Courts
US
Hi Guys,
We have a smilar situation.
We added below setting as DSS :
prconfig/alerts/browser/interactionTimeThreshold/warnMS but PRPC is converting the same to
prconfig/alerts/browser/interactiontimethreshold/warnms
And the new threshold value is not being reflected. Are these settings case sensitive ?
Thanks,
C