Question

Exclude Agents without using -DExcludeAgents option

Hi,

I've excluded some Pega agents that are not needed on our applications by using the -DExcludeAgents option (so I cannot see all these agents on SMA).

But I've added option -DNodeType and agents were not excluded anymore. I've raised a ticket on GCS and I've learned that it's not possible to have both options -DNodeType and -DExcludeAgents: I can use either one of them and not both together.

So, for now, I've only used -DNodeType.

The only way to not see the none used agents is to go on each Data-Agent-Queue Instance and uncheck the box "Enable this agent": it will take a lot of times and in case of a new instance, I will have to do these steps again.

Do you know another way to manage them easily ?

Thanks

Regards

***Edited by Moderator Marissa to update SR Details; update platform capability tags***

Group Tags

Comments

Keep up to date on this post and subscribe to comments

Pega
October 24, 2018 - 5:19am

Hi Alex,

You can try the below work around if it is feasible in your application and environment.

Define your node to a node type and make sure that specific node type is associated with none of the agents.

Example:- You can use 'Custom3' node type for the node where you want none of the agents to run and make sure that node of the agents are associated with this node type.

Pleas let me know if it works for you.

Thanks,

Venkat

November 13, 2018 - 11:26am
Response to janav

Hi Janav,

For now, I have:

Node ID: backoffice_01, backoffice_02, frontoffice_01, frontoffice_02

For each RAQ, 4 DAQ instances have been created by the master agent.

If I define a customized node type 'Custom3', a new DAQ instance will be created by the master agent but all olders DAQ instances will still be present and enabled, no? If it's the case, I will have to disable each DAQ and I've more than 140 DAQ instances to disable ....

But, of course, your proposal will be helpfull for new nodes that I will create (just need to define the node type to 'Custom3' and start the instance).

Thanks

November 6, 2018 - 12:40pm

Hi Janav,

Thanks for your answer (I've just seen today that someone has replied...).

In fact, I'm on Pega 7.22 and customized node type is defined only on Pega 7.3 and higher

Thanks for your help

Is there a way to execute a SQL query for doing same as the action to uncheck box "Enable this agent" ? Thanks

Regards

November 20, 2018 - 4:01am

Hi,

I've seen with Pega Support and they told me that there is no SQL query to disable agent...

So I'm thinking about this configuration:

1- Define a Node Type = RunOnAllNodes who is associated with none of the agents

2- Define a Node Type = BackgroundProcessingNode who is associated with agents that only need to run on backoffice nodes

3- Define for backoffice nodes a Node Type = RunOnAllNodes,BackgroundProcessingNode

Is it possible? Thanks

Regards

November 21, 2018 - 9:16am

Hi,

I've tried to configure on my Tomcat instance with setting below:

-DNodeType=RunOnAllNodes,BackgroundProcessingNode

But I've got this error message:

 ERROR   - Provided NodeType: RunOnAllNodes,BackgroundProcessingNode is not Valid. Hence turning off NodeClassification

I have a doubt if we can configure multiple types for one node...

Regards

December 27, 2018 - 10:38am
Response to Alex_Pan

Where exactly are you specifying the JVM argument? I have a 7.3 node configured with two node types in the setenv.bat file:

-DNodeType=Custom1,Search