Second, ActiveBatch itself is also a WMI provider. This means that ActiveBatch can raise WMI events for any of its own operations. This is important in that not only can jobs run based on ActiveBatch s own events but other third party or customer products can query ActiveBatch about its various objects and run-time performance. Job Properties are easy to create and update ActiveBatch supports Job Dependencies. Job Dependencies ensure that jobs are executed only after the completion of one or more other batch jobs that they must rely upon.
Jobs can support one or more dependencies and the dependencies themselves can be conditional.
The job author also has the ability to indicate what should occur should a dependency fail. ActiveBatch supports Job Triggers. A Job Trigger is an ActiveBatch event that triggers a selected batch job for execution. Job Triggers take two forms. One type is known as the child trigger that supports the execution of different batch jobs based on whether the parent job completed successfully or failed.