Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Scheduling a pipeline by creating a job scheduler rule

Updated on July 14, 2022

You can schedule a data migration pipeline to run during a specified period of time by creating and running a job scheduler. The job scheduler runs a Deployment Manager activity (ScheduleDataSyncPipeline) on the specified pipeline, based on your configuration, such as weekly or monthly.

  1. On the orchestration server, in the navigation panel of Dev Studio, click RecordsSysAdminJob Scheduler.
  2. On the Create Job Scheduler rule form, enter the label of the scheduler and select the ruleset into which to save the job scheduler.
  3. Click Create and open.
  4. On the Edit Job Scheduler rule form, on the Definition tab, from the Runs on list, configure the job scheduler to run on all or one nodes:
    • 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.
  5. From the Schedule list, select how often you want to start the job scheduler, and then specify the options for it.
  6. Select the context for the activity resolution.
    • If you want to resolve the ScheduleDataSyncPipeline activity in the context of Deployment Manager, go to step 7.
    • If you want to resolve the activity in the context that is specified in the System Runtime Context, go to step 8.
  7. To resolve the ScheduleDataSyncPipeline activity in the context of Deployment Manager:
    1. From the Context list, select Specify access group.
    2. In the Access group field, press the Down arrow key and select the access group that can access Deployment Manager.
    3. Go to step 9.
  8. to resolve the activity in the context that is specified in the System Runtime Context:
    1. From the Context list, select Use System Runtime Context.
    2. Update the access group of the batch requestor type access group with the access group that can access Deployment Manager; in the header of Dev Studio, clicking ConfigureSystemGeneral.
    3. On the System:General page, on the Requestors tab, click the BATCH requestor type.
    4. On the Edit Requestor Type rule form, on the Definition tab, in the Access Group Name field, press the Down arrow key and select the access group that can access Deployment Manager.
    5. Click Save.
  9. On the Job Schedule rule form, in the Class field, press the Down arrow key and select PegaDevOps-Work-PipelineConfig.
  10. In the Activity field, press the Down arrow key and select ScheduleDataSyncPipeline.

    Choosing the right Activity, Class name, and Parameters according to your Deployment Manager version.

    Deployment Manager versionActivity in job schedulerClass nameParametersIs the Activity shipped?
    4.8- 5.2pzScheduleDataSyncPipelinePega-Pipeline-DataSyncpipelineName
    5.3, 5.4ScheduleDataSyncPipelinePegaDevOps-Work-PipelineConfigpipelineIDNo
    5.5ScheduleDataSyncPipelinePegaDevOps-Work-PipelineConfigpipelineID
  11. Click the Parameters link that appears below the Activity field.
  12. In the Activity Parameters dialog box, in the Parameter value field for the PipelineID parameter, enter the data migration pipeline that the job scheduler runs.
  13. In the Parameter value field for the ApplicationName parameter, enter the application that the data migration pipeline is running.
  14. Click Submit.
  15. Save the Job schedule rule form.
  • Previous topic Merging test rules into a merge pipeline
  • Next topic Best practices for using pipelines in Deployment Manager

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

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.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us