Table of Contents
Advertisement
Figure 3-14
Any other constraints associated with the context of this job invocation (including but not limited to
this job), with the user you've selected, with that user's group, with the jobs group, with the
resources that the job uses, or with the resource groups that the job uses, run in spite of the policy
that you define here. These additional constraints usually restrict or refine what the job does when
this schedule fires.
These constraints are passed to the job only when this schedule is invoked. For example, you could
add a start constraint to delay the start of a job, a resource constraint to run on only one of three
named machines, or a continue constraint to automatically time out the job if it takes too long to run.
Anything you can do with a regular job policy constraint, you can add as a special constraint here for
this particular schedule invocation.
Click Save icon
For more information about policies, see
Developer Guide and
3.2.4 Activating the New Schedule
When the new schedule has been created and its triggers defined, you need to take it from the
disabled state to an active state where it is ready to run.
1 In the Job Scheduler view, select the newly created job. The job shows that it is in a Disabled
state.
2 Click Enable to enable the schedule.
The schedule is now enabled, but has not run yet.
3.2.5 Running the New Schedule Immediately
You can trigger the schedule immediately, rather than waiting for the triggers to fire.
1 In the Job Schedules Table of the Job Scheduler view, select cleaner (the name of the schedule
you want to run), click Run Now, then click the job monitor icon on the toolbar (Jobs) to open
the Job Monitor view.
48
PlateSpin Orchestrate 2.0 Development Client Reference
The Constraints Tab of the Job Schedule Editor
to update the Orchestrate Server with the new schedule.
Reference.
"Policy
Elements" in the
PlateSpin Orchestrate 2.0
Advertisement
Table of Contents
