scheduler package — Scheduling Service
The scheduling service is responsible for scheduling
the execution of resource-intensive methods, and keeping a history of their
outcomes. It can be used to fire off agent processes, in addition to scheduling
a method invocation.
Scheduler
Model
The scheduling service manages the schedule items in
the system. Schedule items can be scheduled to run once or periodically, and
can start immediately or be deferred to start at a later time. Schedule items
maintain a collection of their histories and their method arguments. Method
arguments can be any object. The scheduler provides a higher-level interface to
the wt.queue package. Schedule items are executed with the same privileges as
the user who created them.
The ScheduleHistory class provides the history of the
execution instances. A default CountedHistory object is supplied for use by
agents that perform a number of internal operations. The execScheduled method
is provided so that when the execution fires off an autonomous agent, the agent
can record its results to the schedule history.
A running instance can be in the following states:
READY
The item is scheduled and awaiting execution.
EXECUTING
The schedule item is executing its method.
SUSPENDED
The operator has suspended the method.
COMPLETED
The operation has run successfully.
FAILED
The operation has failed.
The statuses that pertain to agent processes are as
follows:
ABORTED
The operation has been aborted.
ERROR_CONTINUED
An error has occurred in the agent session, but the
agent has decided to continue.
ERROR_COMPLETED
An error has occurred in the agent session, but the
agent process continued to completion.
ERROR_STOPPED
An error has occurred in the agent session and the
agent has stopped processing.
External Interface
There is no external API for customer use.
Event Processing
This service does not emit any events.