JobScheduler jobs and orders can be started / triggered in a number of ways: Job activities can also be limited to time-slots:
JobScheduler jobs and orders can be started / triggered in a number of ways:
Job activities can also be limited to time-slots:
- 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.
Manual Job Start
- Manual job starts can be made using the JOC - JobScheduler Operations Center.
- Jobs can be started manually from the command line.
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.
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.
Start by API
- Program-controlled job starts can be made using the JobScheduler API Interface with a Scripting language and using the XML Interface.
- Jobs can be started from the command line.
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.
How To ... Articles
Frequently Asked Questions
Examples in Detail