Queue Processor and Job Scheduler in Pega

 Pega Job Scheduler and Queue Processor provide enhanced scalability and performance for Pega Platform. The Job Scheduler allows for the creation of a job that will execute based on a schedule. Queue Processor is a server that can process tasks, activities and other work assignments stored in the system. It can be used to process bulk data, such as posting to an external system, or to run report jobs. Queue Processor enables better performance, scalability and fault tolerance. It allows tasks to be distributed across multiple process nodes, improving efficiency. It also allows for more sophisticated processing of queued tasks, and allows additional customization of processing logic. By using Queue Processor and Job Scheduler, businesses maximize the performance, scalability and fault tolerance of the system.

Identify performance issues with queue processor and job scheduler activities in Pega

Identify performance issues with queue processor and job scheduler activities in Pega

We often see Queue processor activity or a Job scheduler activity runs longer than the threshold values which is directly impacting the performance of our applications, sometimes we don't know how to investigate those performance-related things.

Pega has come up with new alerts for Long-running queue processor and Job scheduler activities from Pega 8.5.

• PEGA0117 alert: Long-running queue processor activity.
• PEGA0118 alert: Long-running job scheduler activity.

Pega now saves these alerts in the performance alert log. We can easily analyze these alerts directly in the log and address potential performance issues with long-running processes.

Queue Processor and Job Scheduler in Pega

What is Background processing in Pega?

Executing tasks in the background allows for improved scalability and performance. 

As we are famous on Agents for background processing to send emails, performing some tasks on the Work objects and queuing items, etc,

Pega has provided below two Rules to accommodate background processing instead of Agents, were previously required agents, such as service-level agreements, sending daily emails, or queuing items.

1. Queue Processor 
2. Job Scheduler

These rules are in the SysAdmin category in Pega.