Novell PLATESPIN ORCHESTRATE 2.0.2 - DEVELOPMENT CLIENT REFERENCE 08-28-2009 Reference page 30

Priority
When you create a new schedule and associate a job and a user with it, a list of possible run
priorities becomes available in this drop-down list. The list of priorities varies, depending on the
user that is specified in the previous field. In this field, you select the priority of the job that is to be
run so that if other jobs are to start concurrently or are competing for resources, PlateSpin
Orchestrate can determine which job takes priority.
Description
For predeployed jobs, this field contains a default description of what the job's schedule does. The
field is editable, so you can enter a description of your own for job schedules that you create.
Matching Resources
This button displays a list of resources where the job runs now or where it could run. This list is
useful for checking the context of constraints that might have been affected by a choice of user or by
manually specifying additional constraints under the Policy tab. The list is also useful to verify that
a discovery job (that is, one that is triggered by the Run on Resource Start option) runs on the
preferred set of machines.
Test Schedule Now
Click this button to test the new or modified schedule you are working with. The test runs the new or
modified schedule without permanently saving the current configuration of the schedule or
recording statistics. This control differs from the Run Now control in the Job Schedules Table, which
runs a saved (persisted) schedule, disregarding any unsaved modifications that have been made to it
in the Job Schedule Editor.
Triggers
When you click the Triggers tab in the Job Scheduler view, the following page opens:
The Schedule Triggers Page in the Job Scheduler
Figure 3-6
In this view, you can add or define the triggers you want to associate with job schedules. A trigger is
the signal to the Job Scheduler to initiate, or "fire" a schedule at a given time or at the occurrence of
a given event. Job Scheduler triggers can be classified with regard to two conditions: events and
time.
30 PlateSpin Orchestrate 2.0 Development Client Reference