onestoppega

  Queue processor FAQ A queue processor rule is an internal background process that you configure for queue management and asynchronous message processing. Use standard queue processor rules for simple queue management or low-throughput scenarios, or use dedicated queue processor rules for higher-scaling throughput, and customized or delayed processing of messages. Best practice is to configure queue processors instead of using standard agents to manage message queuing in Pega Platform. For details, see   Background processing best practices . Frequently Asked Questions about queue processors include the following: How do I queue a message to a queue processor? You can queue a message to a queue processor by performing either of the following actions: Use the   Queue-for-Processing   activity method. Use the   Run in Background   SmartShape when you create a case. For more information, see   Queue-For-Processing method   and   Running a background process . Can I queue a message to be

  Job Scheduler rules   Job Scheduler is a background server process that runs activities on a periodic basis. In a multinode cluster, Job Scheduler rules can run on multiple nodes. For better performance, monitoring and diagnostics, Job Scheduler rules replace advanced agents. You can use Job Scheduler rules to perform jobs that are configured to run at a particular time, such as system cleanup jobs. You can associate a Job Scheduler rule to a node type, and you can run the rule on any node or all nodes of that type. Configure Job Scheduler rules to run on the following schedules: Multiple times a day Daily Weekly Monthly Yearly If you configure your Job Scheduler rule to run on all the nodes in a cluster, you can also enable it to run at a startup. Job Scheduler management Create job schedulers in Dev Studio. Use the Jobs landing page in Admin Studio to trace and override Job Scheduler rules in your application. To create and manage Job Scheduler rules, make sure you have the   pzJob

  Creating a Job Scheduler rule In Dev Studio, click   Create   SysAdmin   Job Scheduler   . Add a label and a ruleset to your Job Scheduler rule. Click   Create and open . Configure the Job Scheduler to run on specific node types by performing the following actions: Click the   Select node types   icon. Select the check boxes next to the node types that you want to associate with the Job Scheduler rule. Click   Submit . In the   Runs on   drop-down list, configure the Job Scheduler rule to run on one or all nodes by selecting one of the following options: To run the job scheduler on all nodes in a cluster, click   All associated nodes . To run the job scheduler on only one node in a cluster, click   Any one associated node . If you configure the Job Scheduler to run on any node, the Pega Platform application chooses the node on which it processes the task. In the   Schedule   drop-down list, click the schedule for the Job Scheduler rule and provide additional details, such as a start

 diff. between pega agent and jobscheduler     This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product. Share Configuring resources - use job schedulers and queue processors instead of agents + This content applies to   On-Premises Services and Cloud   environments. For better scalability, ease of use, and faster background processing, use job scheduler and queue processor rules instead of agents in scenarios that previously required agents, such as service-level agreements, sending daily emails, or queuing items. Although you can still use agents, a warning is displayed if you try to create an agent. Job scheduler and queue processor rules also facilitate the management of multiple nodes because you do not have to maintain the instances of   Rule-Agent-Queue   and   Data-Agent-Queue   that are combinations of multiple agent rules. Job scheduler versus agents Job scheduler rules rep