Disabling OOTB Job Scheduler and Queue Processor
Hi,
Back in Pega 7x days, there were a lot of discussions about which OOTB Agents should be disabled for better performance, such as below.
- https://collaborate.pega.com/question/need-info-best-practice-what-agent-configuration-multi-hostmuti-node-environment-pega-7
- https://collaborate.pega.com/question/ootb-agents-need-be-disabled-and-adjusted-production
- https://mesh.pega.com/docs/DOC-81378
However, I am unable to find the same for Pega 8x. Can someone redirect me to the appropriate information source? Agents are now converted to Job Scheduler and Queue Processor in 8x but I believe disabling unnecessary ones for production is still required.
Thanks,
Accepted Solution
Updated: 2 Jun 2023 7:46 EDT
N/A
NL
Bit late answer but i was looking for the same today, how to disable ootb Pega jobs that we dont need. So for all with same question. In Pega 8 All jobs are rule resolved against the context specified in the System Runtime Context You can disable or change a job schedule by overriding the job in another application that has higher priority in the system runtime context configuration (accessible via admin studio jobs page, link on top).
Pegasystems Inc.
GB
The changes done in admin studio are valid until the restart. If the server restart is done, then those changes will be reverted. If you want to stop run of a agent even after the restart, then you need to disable the agent schedule.
From Pega 8 on wards, the agent schedules are created per the Node type.
For example, if the agent is designated to run on a "BackgroundProcessing" nodetype, then a agent schedule is created to run that agent on all the nodes for which the "BackgroundProcessing" nodetype is assigned.
For example you can assign 'Custom1' node type for node1 and 'Custom2' node type for node2.
You can designate your agent to run on 'Custom1' and 'Custom2'. Then you can observe that two agent schedules are created for your agent.
Now you can disable the agent schedule, if you do not want to run agent on particular node having particular node type.
References:
The changes done in admin studio are valid until the restart. If the server restart is done, then those changes will be reverted. If you want to stop run of a agent even after the restart, then you need to disable the agent schedule.
From Pega 8 on wards, the agent schedules are created per the Node type.
For example, if the agent is designated to run on a "BackgroundProcessing" nodetype, then a agent schedule is created to run that agent on all the nodes for which the "BackgroundProcessing" nodetype is assigned.
For example you can assign 'Custom1' node type for node1 and 'Custom2' node type for node2.
You can designate your agent to run on 'Custom1' and 'Custom2'. Then you can observe that two agent schedules are created for your agent.
Now you can disable the agent schedule, if you do not want to run agent on particular node having particular node type.
References:
Please see also the suggestions in Queue Processing and Job Scheduler
Accepted Solution
Updated: 2 Jun 2023 7:46 EDT
N/A
NL
Bit late answer but i was looking for the same today, how to disable ootb Pega jobs that we dont need. So for all with same question. In Pega 8 All jobs are rule resolved against the context specified in the System Runtime Context You can disable or change a job schedule by overriding the job in another application that has higher priority in the system runtime context configuration (accessible via admin studio jobs page, link on top).