The Scheduler is incorporated into part of the application server and is integrated into the configuration service. The configuration service poller tells the application server when it is time to go and look for tasks related to a specific Scheduler.
Each Scheduler can be related to a site object that denotes the location of the application server responsible for processing the tasks for that Scheduler. Once the Scheduler on the server has been notified to poll, it queries the database tasks to be processed. When a task needs to be run, the software starts a new thread to execute the task. Each task object holds information about how to process the task, and like any other modeled object, it is stored in the database. For example, the task holds information that determines whether it runs once, a number of times, or repeatedly on a specified schedule.
The user interface is available only in the Desktop Client and allows administrators to change the Scheduler options to start, stop, or pause the Scheduler. The task information is displayed in the Desktop Client through the Scheduler task query, which retrieves the information from the database and displays it in the List View window.
As each Scheduler is stored as an object in the database, the Desktop Client allows users to change each Scheduler independently. Information that is displayed in the details window can be filtered and sorted by any of the columns in the table.
The scheduler tasks delivered by default are:
-
Print
-
E-mail digest
-
Title block
-
Export compress
-
Alternative rendition
-
Archive purge
-
Progress rollup
-
FTR
-
Progress accrue event progress
-
Published document load queue management
Some Scheduler services can be set up on an alternate server to offload the processing to a separate physical machine connected through the network or the internet, such as for printing, title block, and alternate rendition. If the task fails to complete, an error message is stored that can be viewed in the Scheduler task window.
Tasks that need to interact with the database (such as e-mail digest, data loading,
and archive and purge) cannot be offloaded and are processed within a SmartPlant Foundation
server site.