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

In this dialog box, you can click Add to move a selected trigger to the active, scheduled triggers that
are to be associated with this job schedule. You can also click Remove to unassociate a trigger.
When a trigger is moved to the scheduled list, it becomes associated to the job schedule and it is
displayed in the Job Scheduler view.
Most example jobs in PlateSpin Orchestrate are associated with event triggers, which are shown in
the previous illustration. The dialog box can also list other job schedule triggers that are based on
time.
Event Triggers
An Event trigger is the signal to the Job Scheduler to initiate, or "fire" a job when a given event
occurs. An Event can be one of three types:
Event objects: These objects are user defined events that are fired when an event rule is
triggered. If an event object is deployed, it automatically shows in the trigger chooser as a
possible choice.
built-in events: These events are system wide events such as when a resource comes online or
when a resource health condition change occurs. Built-in events are always available as a
trigger choice. The Job Scheduler has eight possible built-In event triggers:
AGENT_VERSION_MISMATCH
RESOURCE_ONLINE
REPOSITORY_HEALTH
RESOURCE_HEALTH
SERVER_UP
USER_HEALTH
USER_ONLINE
VMHOST_HEALTH
You can select any combination of these event triggers for a single schedule.
The first trigger,
Agent of an incompatible version attempts to connect to this Orchestrate Server. It can be used
to initiate a configuration management tool for an agent software update or the job could e-mail
an administrator to report the incompatible agent. The other seven available built-in event
triggers are listed with accompanying descriptions in the dialog box.
External events: These events are fired by an outside process. These are not automatically
shown as choices in the trigger chooser, but must be defined by the trigger editor.
An event trigger can be used in conjunction with a time trigger to allow flexibility in scheduling the
job application for maximum effectiveness or convenience. Jobs triggered by events require that
their job arguments contain a dictionary named
should have this jobarg element in its policy:
<policy>
<jobargs>
<fact name="context" type="Dictionary"
</jobargs>
</policy>
32 PlateSpin Orchestrate 2.0 Development Client Reference
AGENT_VERSION_MISMATCH
description="Dictionary containing the context for the event" />
, triggers the job when a PlateSpin Orchestrate
. For example, your event-triggered job
context