...
- Database Configuration
- The JobScheduler requires a database except it will be used as an agent. The JobScheduler needs the database to archive logs and to remember Job and Order states. A JobScheduler agent doesn't have own Jobs or Orders and the logging is made by the JobScheduler which calls the Agent. So an Agent is running without a database.
- You find the supported database management systems listed in the Which Database Management Systems are supported by JobScheduler? article.
- Because of licensing restrictions when used with MySql®, Sybase or Microsoft® SQL Server databases, a JDBC® driver appropriate to the database version used must be provided by the end user themselves. Alternatively, a jTDS JDBC® driver, delivered with the JobScheduler setup, can be used for Microsoft® SQL Server and Sybase databases. Similarly, the MariaDB® driver is delivered with the JobScheduler setup, for use for MySql® Server and MariaDB® databases. For IBM® DB2 a JDBC® driver inlusive the license file must be provided by the end user too. Drivers for Oracle® Database and PostgreSQL are contained in the JobScheduler setup.
- JobScheduler Installation
- Installation of the JobScheduler is carried out using a setup program. This can be downloaded from the SOS Web-Site for Microsoft® Windows® and Linux®.
- For more information see the Which platforms is JobScheduler available for and what platform support is provided? article.
| Anchor | ||||
|---|---|---|---|---|
|
1.1 Requirements
The JobScheduler is for Linux® and Microsoft® Windows® in 64-bit and 32-bit available, for other operating systems currently still only in 32-bit.
...