...
- Jobs are the basic unit for the processing of executable files, shell scripts, database procedures and of job implementations based on the JobScheduler API.
- Jobs can be executed independently from one another. Depending on the execution result, i.e. exit code signalling code signaling success, failure or a specific exit code, of a job any number of successor jobs can be started.
- 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. Therefore, each job comprises exactly one step in the processing of a job chain. Job dependencies based on execution results of the respective job nodes can be configured for a job chain.
- Monitoring of directories can trigger job starts, this allows the integration of legacy applications into the business workflow.
- Jobs execute file transfers based on the built-in FTP and SFTP capabilities as a widespread means to integrate applications.
- Job starts are triggered by built-in calendar, by command line or by web interface.
- Other applications can start jobs or otherwise control the JobScheduler via APIs.
...
- High-availability Cluster: a JobScheduler backup cluster ensures fail-safe operation and fault tolerance with automatic fail-over. A fail-safe system consists of a primary JobScheduler and at least one backup, with both these JobSchedulers running on different computers.
- Load balancing: For a high volume of data with time consuming processing using multiple JobSchedulers will speed up the processing time considerably and provide higher availability. In load balancing mode the processing tasks are shared between multiple JobSchedulers that are handling distributed orders on more than one host.
- Solution stacks are implementations with third party Open Source components that are available for e.g.
- System Monitors such as Nagios, op5, Zabbix etc.
- Secure Shell remote execution, SCP Secure Copy and SFTP Secure file transfer.
...