JobScheduler

• The JobScheduler can be configured to run as a standalone application.[10]
• The JobScheduler implements a master / agent architecture to run jobs on the master and on agents that are deployed to remote computers.[10]
• The JobScheduler master and agents can be configured to run in high availability and load balancing clusters with fixed priority scheduling and round-robin scheduling.[11]
• For deployment of jobs a JobScheduler supervisor can be used that synchronizes the configuration in a cluster.[12]

• The JobScheduler runs unattended in the background as a Unix daemon or Windows service:[6]
  • The JobScheduler can be used for batch processing to run a series of operations.
  • Near real-time processing can be initiated for individual operations. Near real-time triggers can be generated on the fly in response to external events such as the arrival of incoming files.[13]
• Monitoring and manual intervention can be carried out from the command line or with a built-in web-based graphical user interface.[14]

• Job chains, which can be seen as an assembly line on which multiple job nodes are passed. Each job in a job chain makes up a step in the processing of the chain.[15]
• Job dependencies, which can be based on the results of the execution of preceding job nodes in one or more job chains.[16]
• Cross-platform scheduling:[17]
  • Universal agents to execute jobs directly on remote hosts across different operating systems,[18]
  • Agentless scheduling to execute jobs across different operating systems.[19]
• Active/passive clusters for scalability & high-availability.[20]
• Recording of job history,[21] frequency and log information[22] in SQL databases.
• Triggering of job starts by directory monitoring[23] and file watching.[24]
• Built-in file transfer capabilities.[25]
• Scripting capabilities (Shell, JavaScript, PowerShell, etc.).[26]
• A monitoring interface for integration with system monitors such as Nagios, Zabbix, SCOM, etc.[27]
• A library of standard job templates covering operations such as file transfer and log rotation.[28]
• Graphical interfaces for job configuration, workflow control and access to the job logs and history.[29]

• The JobScheduler master is written in C++ and Java, the agent has been developed with Scala and Java. Standard jobs distributed with the JobScheduler are implemented with Java.[14]
• Information about the individual objects processed by the JobScheduler - jobs, job chains, orders, schedules, etc. - are persistently stored in the form of XML files.[6]
• A database management system (DBMS) is used by the JobScheduler master to store job status, protocol and history information.[6] Supported DBMSs are listed below.

• The Universal Agent has been introduced for carrying out complex scheduling tasks on remote computers and operating systems not otherwise supported by the JobScheduler master.[30]
• The agent runs on any operating system that supports a Java Virtual Machine.[18][30]
• The agent acquires its configuration and task execution requests from one or more JobScheduler master instances and does not require a DBMS.[30]
• Master / agent communication uses a single HTTP or HTTPS connection.[31]
• A number of JobScheduler agents can be configured in an agent cluster for redundancy and fail-over.[18]

Operating systems:[32]

• Windows (32 & 64 bit)
• Linux (32 & 64 bit)

Database management systems:[33]

• Oracle
• SQL Server
• MySQL
• MariaDB
• PostgreSQL

The Universal Agent can be run on any operating system that supports a Java Virtual Machine. A DBMS is not required.[30]

The JobScheduler can be used under the open source GPL 2.0 license. Users can also purchase commercial licenses.[4] The JobScheduler Universal Agent can be used under a freeware license (under restriction) or commercial licenses.[4]

Enterprise-level support and services are available for users with commercial licenses.[4] Users operating JobScheduler under the open source license can obtain support from the JobScheduler Knowledge Base and the forum on SourceForge.