Skip to end of metadata
Go to start of metadata

Introduction

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

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.

Start Times

  • Jobs can be started when a predefined point in time has been reached: time of day, weekday, day of the month, a date relative to end of month etc. 

Read more on this feature on the Start Times page and in the Run Times documentation.

Manual Job Start

Start by Events

  • Event driven job starts can be initiated by using the XML Interface.
  • Such events that are sent via TCP or UDP protocol.

Read more on this feature in the Event Handling section and in the XML command documentation.

Directory Monitoring and File Watching

  • Job starts can be triggered by Directory Monitoring - should changes in directories or the addition or deletion of files in directories occur. 
  • JobScheduler offers File Watching and will start jobs automatically for individual files arriving in a directory.

Read more on these features in the directory monitoring and file orders documents.

Start by API

Read more on this feature in the internal API documentation and in the XML command documentation.

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.

See Start Times for more information.

Resources

How To ... Articles

Frequently Asked Questions

Examples in Detail

 

Write a comment…