Niagara Provisioning uses batch jobs as the method for doing most of its tasks. A combination of objects, including components, files, and histories are used to model provisioning jobs, and their contained steps.
Note that batch jobs are different than other jobs run by the Supervisor’s JobService, because:
File records of a batch job execution are retained until the job is explicitly disposed of, instead of being held temporarily as children of the JobService, then quickly disappearing.
Batch jobs can optionally trigger alarms (alerts) upon successful or unsuccessful completion.
Batch jobs are first dispatched to a thread pool job queue, before being given to the JobService.
Histories are automatically created for provisioning batch jobs as well as for individual device steps.
These sections describe those objects and their relationship to each other.
Copyright © 2000-2014 Tridium Inc. All rights reserved.