The JobScheduler is an Open Source solution for enterprise level workload automation. It is used to launch executable files and shell scripts and to run database procedures automatically. JobScheduler stores all information in a back-end database management system.
- Launch executable files, shell scripts and database procedures automatically.
- Trigger events for job starts such as calendar events, monitored incoming file events and API events initiated by external applications.
Mode of Operation
- Used for batch scheduling, the JobScheduler runs in the background as a Unix daemon or Windows service.
- Job control is carried out from the command line or a built-in graphical user interface, JOC (JobScheduler Operations Center).
- A graphical XML editor JOE (Job Object Editor) is available for job configuration.
- Jobs are the basic unit for the processing of executable files, shell scripts, database procedures and for job implementations based on the JobScheduler API.
- Jobs can be executed independently from one another. Any number of successor jobs can be started according to the execution result of a job, i.e. an exit code signaling success, failure or a specific exit code.
- Jobs can be executed in parallel up to a configurable number of simultaneous tasks.
- Job chains can be seen as an assembly line on which multiple job nodes are passed. Each job comprises exactly one step in the processing of a job chain. Dependencies can be configured in a job chain according to the execution results for individual job nodes.
- Jobs can use the built-in FTP and SFTP capabilities to execute file transfers as a widespread means to integrate applications.
- Job starts can be triggered by a built-in calendar, from the command line or from a web interface.
- Job starts can also be triggered from monitored directories, allowing the integration of legacy applications into the business workflow.
- Other applications can start jobs or otherwise control the JobScheduler via APIs.
- Job activities can be limited to time slots. The JobScheduler supports any number of time slots, which can be configured according to individual requirements.
- The JobScheduler allows the assignment of job priorities.
- Job history protocols are optionally stored in a database.
- A locking feature prevents jobs simultaneously accessing resources such as a file or database at the same time. In other words, only one process at a time can receive the exclusive right to access the resource as long as the lock is active.
- Standard job packages are available for tasks such as log rotation and cleanup, sanity checking, job execution by remote JobSchedulers and FTP file transfer.
- Notifications of the results of job execution can be sent by e-mail.
- Logging and monitoring of logs are configurable.
- An API is available for the implementation of jobs and job scripts, e.g. for complex conditional processing.
- Graphical user interfaces: a built-in interface for job control is available as well as a GUI for managing configurations of multiple JobSchedulers on different server systems.
- High-availability Clustering: a JobScheduler backup cluster will ensure fail-safe operation and fault tolerance with automatic fail-over. Fail-safe systems consist of a primary JobScheduler and at least one backup, with both JobSchedulers running on different computers.
- Load Sharing: multiple JobSchedulers will speed up the processing time considerably and provide higher availability when processing a high volume of data with time consuming procedures. In load sharing mode processing tasks are shared between multiple JobSchedulers that are handle distributed orders on more than one host.
- Interfaces: allow implementation with third party components such as:
- System Monitors - e.g. Nagios, op5, Zabbix etc.
- Reporting interfaces for data warehouse applications
- Secure Shell remote execution, SCP Secure Copy and SFTP Secure File Transfer applications.
- The JobScheduler is written in C++,Java and Scala, standard jobs are implemented with Java Version 1.7 and higher.
- A JRE 1.7 or higher is required for JobScheduler release 1.6.4036 onwards.
- A JRE 1.8 or higher is required for JobScheduler release 1.9 onwards.
- The Open Source JobScheduler can be customized according to specific business requirements. Enterprise level Support is available.
- JobScheduler can be operated for 32bit and 64bit environments, see:
- JobScheduler is supported according to release cycles, see: