Job execution

Just prior to execution, some steps in a provisioning batch job are combined. Currently, the only steps that are combined are Install Software, Copy File, and Upgrade Out-of-date Software steps that are adjacent to each other. Combining steps avoids duplication of dependency-checking with a station and minimizes the number of reboots required.

Upon execution, the provisioning batch job first executes any initial steps to run only once. NiagaraNetwork provisioning this means that the system runs the Update Licenses step (if included) first. Typically, the Supervisor has Internet connectivity, and makes a single, silent inquiry to the licensing server, passing the current licensing information for each host running an included station (in the job) to the licensing server. The licensing server responds with updated licensing information (if any) for these hosts in the form of a license archive, where any updated licenses are installed, as well as updated within the Supervisor’s local license database. For more background details, refer to related Niagara Platform Guide sections.

Following this, the provisioning batch job executes the remaining steps in sequence for each station, working through its list of stations in sequence. When the job reaches a station in the list, its station state reports Running. If any step fails, the station’s state reports Failed, no additional steps are run for that station, and the job continues with the next station in the list.

If every step succeeds for a station, the station state reports Success. If the job is canceled during a station step, the station state and that of all following stations in the list report Canceled.

When all steps are complete for all stations without canceling, and all steps complete successfully, the job state reports Success. However, if even one step failed, the job state reports Failed.

The Progress Indicator will show the number of job steps completed, total number of expected steps and the percent complete. Note that the total step count can change while the job runs due to automated step combination (e.g. for software installation steps), automatic step creation (for license updates), and for step failures (where subsequent steps will not be run).