Product Knowledge Base

Space shortcuts

Page tree

Versions Compared

Old Version 2

changes.mady.by.user Andreas Püschel

Saved on

compared with

New Version Current

changes.mady.by.user Alan Amos

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Introduction

Excerpt

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

  • A job Jobs can have multiple Pre-/Post-Processing Monitors ordered starting from 0 onward to be . The order in which these are executed by the JobScheduler can be specified by setting a parameter.
    • A PrePre-Processing Monitor can Monitors 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 Monitors can check the job's execution status, return code, total execution time etc..
  • The Pre-/Post-Processing Monitors can be programmed independent from the independently of a job's programming language e. g. a Shell For example, a shell script job can have a Pre-/Post-Processing Monitor written in JavaScript.  

Scripted

...

Pre-/Post-Processing Monitors

  • Monitor The scripts can include
    • Java classes
    • JavaScript code
  • Scripted conditions are Scripting is a powerful means for flexibility:
    • JavaScript code can be added directly to Jobs and Monitors and is interpreted at run-time. No A build cycle is not required.
    • Java classes can be added that make use of of the ecosystem of available Java librarieslibrary ecosystem.
  • The JobScheduler exposes its objects, methods and properties by use way of the its API Interface.Scripted conditions can be applied by implementing a spooler_process_before() function for a preprocessor monitor with jobs in a job chain that will
  • return the value true if the job should start,
  • return the value false if the job should not start,
    • move Orders to the next state in a job chain if the current job should be skipped

Methods of Specifying Monitors

Monitors can be specified in the following ways:

  • As Named Monitors:
    • Named Monitors are specified in the configuration of individual jobs.
  • As Enforced Monitors:
    • Enforced Monitors are specified in the JobScheduler configuration and are therefore by default applicable to all jobs executed by the JobScheduler.
      • Filters can be used to limit the monitors and the jobs that they are applied to.

A Monitor can be specified as both a Named Monitor and as an Enforced Monitor.

See also