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.
Batch jobs are different from other jobs run by the
Supervisor’s JobService, because:
- The 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 deleted.
- 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.