Jobs and Job Chains

Concepts for jobs, job chains and orders

The JobScheduler's unique job and order concept includes the organization of jobs into job chains and the use of dependencies.

• Jobs are the basic unit for the processing of executable files (programs, scripts, commands etc.).
• Job Chains can be seen as an assembly line on which a number of job nodes are passed sequentially.
• Orders represent triggers that will cause a job chain to be started according to calendar events.

Read more ....

Jobs and order triggers

JobScheduler jobs and orders can be started / triggered in a number of ways:

• Time events (for example from Schedules or date/time objects)
• Manually using the JobScheduler's web-based JOC - JobScheduler Operations Center Interface
• From run-time events - such as the completion of another job chain
• Directory Monitoring and File Watching events - for example, when a file is added to or deleted from a folder
• From another job via the API Interface and from another application via the XML Interface

Job activities can also be limited to time-slots:

• Jobs are would have to wait for a time-slot to become available, e.g. between 08:00am and 11:00am.
• JobScheduler supports any number of time-slots, which can be configured according to individual job requirements.

Read more ....

Job dependencies

There are a number of approaches available for implementing job dependencies such as those required for concurrency and synchronization:

• Split & Sync
• Event Handling and Resource Contention Management
• Dynamic job and order configuration

Read more ....

Job templates

The JobScheduler Integrated Template Library is delivered with the JobScheduler and provides a set of standard jobs that can be used either as-is or as a base for custom developments.

Read more ....

Generic jobs

JobScheduler's unique job and order concept allows:

• reusable jobs and job chains,
• dynamic assignment of jobs to different JobScheduler instances.

This can be achieved by the following techniques:

• • passing parameters to jobs and orders when they are started,
  • defining generic jobs which are run with parameters generated on-the-fly,
  • executing jobs in remote JobScheduler instances that are dynamically defined according to the results of previous jobs, environment variables, etc.

Read more ....