The BatchJobService is required in the Supervisor station to facilitate provisioning. Copy it from the batchJob or provisioningNiagara palette into the Supervisor’s Services folder. As shown in Figure 53, it has no special views.
The BatchJobService is responsible for dispatching all provisioning jobs (as batch jobs) on a Supervisor, where batch jobs are run by the station’s JobService. The BatchJobService provides “job control” functions for provisioning jobs. However, you do not normally interface with it, apart from specifying the station’s alarm class to use for provisioning alarms. See the next section BatchJobService properties.
Properties and slots of the BatchJobService (Figure 53) are described as follows:
-
Status — Is either
faultif provisioning is not licensed,disabledif Enabled property is false, and in all other cases isok. -
Enabled — If set to false, provisioning activity via the BatchJobService cannot occur.
-
Fault Cause — Text explanation for why service is in fault.
-
Job Queue — (Thread Pool Job Queue) Manages the submission of provisioning batch jobs by using a thread pool, to ensure the Supervisor’s CPU and network resources are not overtaxed by concurrent sessions. A single property, Max Threads, defaults to one (1), meaning only one provisioning job can run at a time. No special views or other features are provided.
Only after determining the station has available resource overhead, should Max Threads be adjusted to values over 2 or 3.
Otherwise, other tasks performed by the station may be affected.
-
Alarm Class — (Recommended to be changed from default) The Alarm class in the Supervisor station’s AlarmService to be used for alarms (technically, alerts) when provisioning batch jobs fail and/or complete—as set in the alarm checkboxes of the view used to build the provisioning job. For example (in the Niagara Network Job Builder), see alarm checkboxes.
For further details, see About provisioning-related alarms.