Monitors

Introduction

The Monitors (also called Pre-/Post-Processing Monitors) are used with Jobs to provide pre-processing and post-processing capabilities by Scripting. The Pre-Processing Monitors are executed before a task or processing step is being executed by the JobScheduler. Similarly the Post-Processing Monitors are executed once a task or processing step is completed. 

• A job can have multiple Pre-/Post-Processing Monitors ordered starting from 0 onward to be executed by the JobScheduler.
  • A Pre-Processing Monitor can be created to 
    • validate required conditions for a particular task to be started or 
    • set a parameter value dynamically, e.g. today's date.
  • At the same time a Post-Processing Monitor can check the job's execution status, return code, total execution time etc..
• The Pre-/Post-Processing Monitors can be programmed independent from the job's programming language, e.g. a shell script job can have a Pre-/Post-Processing Monitor written in JavaScript. 

Scripted Pre-/Post-Processing Monitors

• The scripts can include
  • Java classes
  • JavaScript code
• Scripting is a powerful means for flexibility:
  • JavaScript code can be added directly to Jobs and Monitors and is interpreted at run-time. No build cycle is required.
  • Java classes can be added that make use of of the ecosystem of available Java libraries.
• The JobScheduler exposes its objects, methods and properties by use of the API Interface.
  • Find details and examples with the Reference Documentation.

See also

• How to configure a Named Monitor
• How to configure an Enforced Monitor
• How to add conditions for job execution with date calculation