Access Dynamic System Setting value specific to Node Classification
I have a reasons to access the value for agent/threadpoolsize in Rules. We are configuring this (in 7.1.9) in DSS, and we are also using node classification to vary the value by node type i.e. <env name="initialization/nodeclassification" value="background" /> in prconfig.xml.
For more information on this configuration see https://docs.pega.com/how-compose-key-prconfig-dynamic-system-setting
I have been unable to access the correct value for the current node. The Engine API PRSystemSettings.getDynamic() only returns a value if the fully-qualified key is passed e.g.
@Utilities.getDataSystemSetting("Pega-Engine","prconfig/agent/threadpoolsize/background")
Is there any way to access the value of the prconfig setting initialization/nodeclassification (specific to the current node) so that I can build the DSS key dynamically?
Thanks.
Accepted Solution
Pegasystems Inc.
GB
Unfortunately the conclusion of this conversation was that it is not possible.
Pegasystems Inc.
US
It sounds like when you run @Utilities.getDataSystemSetting("Pega-Engine","prconfig/agent/threadpoolsize/background") on a background node it returns a value, but it does not if that is run on other node classifications. Is that correct?
If so, this isn't exactly what you're looking for but if nothing else you could run getDataSystemSetting() for background, see if it returns a value, and if not, check for a different node classification until you determine what the node is.
Pegasystems Inc.
GB
Hi Nick. Thanks for the suggestion.
Unfortunately the API method just returns the value of the match on the key irrespective of which node it is, so I cannot test the result to determine which request to issue or use the result to infer the node.
I am still looking for ways to determine the classification name for the current node. I now have a simple function that will return a DDS specific to the node, but only if the classification name is passed as a parameter!
Pegasystems Inc.
IN
Specializing the prconfig values via nodeclassification is applicable to only those DASS which are configured as prconfig. While startup the prconfig corresponding to the appropriate node classification are read and available wherever they are referenced. The same is not applicable for DASS. And we do not have a public API that lets you read the prconfig settings.
Pegasystems Inc.
GB
Thank you for your reply. I can see the values varying by node in SMA. Might it be possible to use JMX to read the setting that is returned to the SMA?
Pegasystems Inc.
IN
What exactly you mean by when you say the values are varying by node in SMA. Are you talking about the prconfig values that you are seeing?
CIBC
CA
We are facing a similar issue. We have multiple WebLogic nodes on separate physical servers. On each server we have server specific settings such as MQ queue manager name. At run-time, a node needs to know to what MQ queue manager to send/receive messages. Using DSS doesn't seem to help.
Pegasystems Inc.
IN
Hi,
Thank you for posting your query in the PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
You may also refer this discussion link as a reference in the new thread.
CIBC
CA
Sure, I created a new post here:
https://collaborate.pega.com/question/how-define-server-specific-settings
CollabPartnerz
IN
Could you please try with below link
https://collaborate.pega.com/question/how-define-server-specific-settings
CollabPartnerz
IN
Please find the below link might help you
https://collaborate.pega.com/question/will-backgroundprocessing-node-classification-stop-user-access