Skip to main content

Creating a Job Scheduler rule

Pega Community logo

Note: The following content, referenced from Pega Community, is included here to help you better achieve the module learning objectives.

To perform tasks and jobs that are configured to run on a periodic basis, such as bulk processing or system cleanup jobs, create a Job Scheduler rule.

  1. In Dev Studio, click Create SysAdmin Job Scheduler .

  2. Add a label and a ruleset to your Job Scheduler rule.

  3. Click Create and open.

  4. Configure the Job Scheduler to run on specific node types by performing the following actions:

    1. Click the Select node types icon.

    2. Select the check boxes next to the node types that you want to associate with the Job Scheduler rule.

    3. Click Submit.

  5. 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.
  6. In the Schedule drop-down list, click the schedule for the Job Scheduler rule and provide additional details, such as a start time.

  7. In the Context drop-down list, select the context for the activity resolution:

    • If you want to resolve the activity in a specific context, select Specify access group, and then provide the access group.

      Make sure the access group that you specify has the access to the class and activity that you specify in the following steps.

    • If you want to resolve the activity in the context specified in the System Runtime Context, for example use the same context for the job scheduler and activity resolution, select Use System Runtime Context.

      For more information, see Creating a service-level agreement rule.

  8. In the Class field, enter a class for the Job Scheduler rule.

    The class that you provide must contain the activity that you want the Job Scheduler rule to resolve.
  9. In the Activity field, enter an activity that you want the Job Scheduler rule to resolve.

  10. In the Alerts configuration section, in the Long running queue processor threshold field, change the threshold for long running job processor activities.

    An alert is saved to the log file when the activity’s execution time exceeds the threshold value. For more information, see PEGA0118 alert: Long-running queue processor activity.
  11. Click Save.

  • 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.

  • Configuring the Job Scheduler rule thread pool
  • Configuring the Performance tool for Job Scheduler rules

    Configure the Performance tool to manage aggregating statistics for Job Scheduler rules by modifying the prconfig.xml file.

  • Replacing an agent with a Job Scheduler rule

    Use Job Scheduler rules for better scalability, performance, and ease of use compared to agents. Replace an existing advanced agent with a Job Scheduler rule to execute scheduled tasks, such as updating a database of email addresses every day at a specific time.

  • AsyncProcessor requestor type

    Use the AsyncProcessor requestor type to resolve Job Scheduler and Queue Processor rules.

  • Classifying nodes

    Node classification is the process of separating nodes by purpose, predefining their behavior by assigning node types. When you associate a work resource with a specific node type,you optimize work performance in your Pega application.

If you are having problems with your training, please review the Pega Academy Support FAQs.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Academy has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice