PEGA PRPC | Difference Between Job Scheduler and Queue Processor In PEGA | PEGA Training

[@manivirat...1880]

No Coding Software Job....PEGAPRPC

[@chiruglory2523]

Hi Harsha, On what context queue processor or job scheduler will run ? What is meant by system run time context ? And how it is related to queue processor or Job scheduler ?

[@HarshaTrainingsacademy]

QP , JSC runs on system run time context / we can provide our own access group as well... SRC provides the access application and its related access group...

[@ShivamGupta-rk4yi]

Hi Harsha, can you please help in telling difference between job scheduler and advanced agents in terms of performance like how job scheduler has better performance than agent when there is almost no difference in both? Also, as we know the importance of thread count in queue processor making its processing faster than standard agent, how we can increase thread count for job scheduler and how will it work as compared to thread in queue processor by avoiding race condition also?

[@HarshaTrainingsacademy]

I will make a video about this soon and upload

[@ShivamGupta-rk4yi]

@@HarshaTrainingsacademy Hi, when can we expect the video?

[@chiruglory2523]

Hi Harsha, Need one clarity here, I understand that there is a improved processing speed with queue processor over standard agent but there is no much difference with job scheduler over advanced agent right then why Pega introduced job scheduler ?

[@HarshaTrainingsacademy]

Job scheduer has more advanced options of processing compared to advanced agent... it can even call BIX rule and run which is not present in advnaced agent... We offer pega trainings with 4 real time projects, complete hands on. If you or any one of oyur friends looking for same , please forward our number 9652532753. New batch stared from sept 9, time 7 PM to 830 PM IST Please do not forget to subscribe our channel. Your Subscription will help us to do more better videos. Also hit the BELL icon for new video notifications. Harsha Trainings is one of the leading and Placement Consultant Provided training with qualified trainers on PEGA,DEVOPS, PowerBI,JAVA,DATA SCIENCE, MULESOFT ,Spring&Microservices,OracleFinance,Appian,Core&Advance java,Django,Communication&Varbal and other various leading software technologies…. For those who have gap after education, we have job placement assurance courses... Subscribe to our channel to learn best of best in technology... For training call us on 9652532753, 9885312299

[@chiruglory2523]

@@HarshaTrainingsacademy thanks Harsha, you provide few differences of job scheduler over advanced agent.

[@saunakdas3161]

Hi Harsha , Please explain the difference between Job scheduler and queue processor with one scenario for both .

[@HarshaTrainingsacademy]

Both job schedulers and queue processors are mechanisms used in Pega to manage and automate background processing tasks. They serve different purposes and are used in specific scenarios to achieve different goals. Here's an explanation of the difference between job schedulers and queue processors, along with a scenario for each: Job Scheduler: A job scheduler is used to execute scheduled tasks or activities at specific times or intervals. These tasks can be one-time or recurring, and they are usually triggered based on a defined schedule. Job schedulers are often used for batch processing, data synchronization, cleanup tasks, and other activities that need to run periodically. Scenario for Job Scheduler: Imagine you have an e-commerce application. Every night at midnight, you want to run a task that generates a report of the day's sales and sends an email to the management team. In this scenario, you can use a job scheduler to schedule the report generation and email sending activity to run at midnight every day. Queue Processor: A queue processor is used to process items in a queue asynchronously. Items in the queue can represent tasks, cases, or any type of work that needs to be executed by the system. Queue processors process items sequentially and can handle multiple queues concurrently, providing efficient background processing of work. Scenario for Queue Processor: Consider a customer support application. Customers submit requests for support, and these requests are placed in a queue for processing. Each request needs to go through a series of steps, including assigning to an agent, reviewing, resolving, and closing. The queue processor can be used to process each request in the queue, ensuring that they are handled in the correct order and without overwhelming the system. Key Differences: 1.Execution Trigger: Job Scheduler: Triggered based on a predefined schedule (e.g., daily, hourly). Queue Processor: Triggered when items are added to the queue. 2.Work Type: Job Scheduler: Suited for tasks that need to be executed periodically or at specific times. Queue Processor: Suited for processing asynchronous tasks, cases, or items in a sequential manner. 3.Processing Order: Job Scheduler: Typically handles individual tasks or activities. Queue Processor: Ensures orderly processing of items in a queue. 4.Concurrency: Job Scheduler: Handles individual tasks one at a time based on the schedule. Queue Processor: Can handle multiple items concurrently while maintaining order within the queue. In summary, job schedulers are best suited for executing tasks at scheduled intervals, while queue processors are designed for asynchronous, sequential processing of items in a queue. The choice between them depends on the nature of the processing you need to achieve in your application......Thank You !!!

[@saunakdas3161]

@@HarshaTrainingsacademy Thanks for such a nice explanation 🙂

[@saunakdas3161]

Hi Harsha, Adv Agent is replaced by Job scheduler and Standard Agent with Queue processor in the current version of Pega so what are the extra features added to JS and QP w.r.t Adv Agent and Std Agent ? Thanks,

[@saunakdas3161]

Why custom filter in report defination used for and what is the applied to class ?

[@HarshaTrainingsacademy]

Here's a breakdown of how custom filters and the "Applied To" class work in a Report Definition: 1.Applied To Class: When you create a Report Definition, you need to specify the class on which the report is based. This class determines the source of the data for your report. For example, if you're creating a report on customer data, you might choose the "Customer" class as the "Applied To" class. 2.Custom Filters: Once you've selected the "Applied To" class, you can define custom filters within the Report Definition. Custom filters are conditions that you set up to filter the data based on specific criteria. These criteria can be based on properties within the chosen class or related classes. For instance, if you're creating a report on customers and you want to see only the customers who have made a purchase in the last 30 days, you would create a custom filter that includes a condition like "Purchase Date > Today - 30 days." This filter ensures that only customers meeting this condition will appear in the report results. Custom filters are useful for various purposes: *Data Segmentation: They allow you to segment your data and focus on specific subsets of information that are relevant to your analysis. *Data Quality: Filters help you exclude irrelevant or incomplete data, ensuring the accuracy and reliability of your reports. *Performance Optimization: By narrowing down the data retrieved, custom filters can improve the performance of your reports, especially when dealing with large datasets. *Ad Hoc Reporting: Custom filters enable you to perform ad hoc analysis by quickly applying different filter conditions without modifying the report definition itself. In summary, custom filters in a Report Definition are used to define conditions that data must meet to be included in the report results. The "Applied To" class specifies the context or source of the data against which these filters are applied. This combination of filters and class selection allows you to create focused and relevant reports tailored to your specific needs.