Introduction
JobScheduler uses a database to store the status of jobs, job chains and orders as well as job protocols and the job history. The database allows such information to be persistent, allowing, for example a job or order to be restored to its previous state after a JobScheduler restart or in case of failover.
- JobScheduler can use a number of Database Management Systems (DBMS).
- One database can be used for a number of JobSchedulers, for example in Cluster Operation.
- Job scripts and Monitor scripts can access any DBMS product to read and write data, see Database Access Layer - SOSHibernate Connection
Resources
Feature in detail
How To ... Instructions
Frequently Asked Questions
There is no content with the specified labelsExamples in detail
Access to DBMS products