Question
IKOR PX
AU
Last activity: 12 Oct 2019 6:11 EDT
JAVA Option -DExcludeAgents is not working as expected
Hi all,
The setting -DExcludeAgents doesnt seem to be working in our Multi node environment.
Pega Version
7.4
Env Type:
AWS Cloud Multi Node Cluster [Classification: WebNode, BackgroundProcessing, BIX, Search]
A portion of JVM_OPTS:
-Duser.country=AU -DExcludeAgents=PegaAESRemote:* -Djdk.tls.ephemer...
However, this configuration doesnt seem to be stopping the AES agents from running on the nodes. Is this a known issue? Has anyone got it to work?
***Moderator Edit-Vidyaranjan: Updated Platform Capability***
Accepted Solution
Pegasystems Inc.
IN
Hi,
Incase of node classification we do not support, -DExcludeAgents and -DIncludeAgent. If this configuaration is on typed node. It is not supported.
We can only disable agent schedule incase of node classification.
You can read similar issue here:
https://collaborate.pega.com/question/exclude-agents-without-using-dexcludeagents-option
Thank You
IKOR PX
AU
Thanks Shekhar..
So according to the other post, the only option I have is to clear out our existing agent schedule records and disable the newly generated schedules on node types that do not need them. I’ll do that for now..
It’s strange though! Do we have any other article from Pega that explains this decision of not using the option with node classification?
Pegasystems Inc.
IN
I am afraid I did not find any such article, but the idea of introducing Dnode and DapplicableNodeTypes was to manage most of these things from application and not from backend
https://community.pega.com/sites/default/files/help_v82/procomhelpmain.htm#engine/node-classification/eng-creating-custom-configurable-node-type-tsk.htm
Let me know if you have any other query.
IKOR PX
AU
Right! For "most" of the things as you say. I was actually checking for a way to restrict certain pega agents from running at all. AES agents are an example. There are a few other OOTB ones as well..