Product Knowledge Base

Space shortcuts

Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

The JobScheduler Master requires a database and/or database schema and a database user.

See the Which Database Management Systems are supported by JobScheduler? article for detailed information about which DBMSs are supported.

Instructions for the creation of the database itself are to be taken from the database documentation. MySql® (5.x ++), Oracle® Database (8.1.x, 9.2, 10g, 11g), Microsoft® SQL Server (2000, 2005, 2012), PostgreSQL (8.x, 9.x), IBM® DB2 (8.x ++) und SybaseASE 15.0. are supported. The JobScheduler setup program will create the necessary database tables if they do not already exist. 

The setup also requires sufficient database permissions for the following statements: CREATE TABLE, CREATE INDEX, CREATE TRIGGER, INSERT,UPDATE,DELETE and SELECT.

The database configuration information is saved in the following configuration files:

  • $SCHEDULER_DATA/config/factory.ini (used by JobScheduler) 
  • $SCHEDULER_DATA/config/hibernate.cfg.xml (used by JID) 
  • $SCHEDULER_DATA/config/sos_settings.ini (used by scheduler_install_tables.(sh|cmd))

3.1 MySql®

Because of licensing restrictions a MySql® JDBC® driver is not provided. Please download a MySql JDBC driver before you start the JobScheduler installer. Alternatively, the MariaDB® JDBC driver, delivered with the JobScheduler setup, can be used for MySql.

3.2 Microsoft SQL Server and Sybase

Because of licensing restrictions when used with Sybase or Microsoft SQL Server databases, a JDBC driver suitable for the database version being used must be provided by end users themselves. Alternatively, a jTDS JDBC driver, delivered with the JobScheduler setup can be used for Microsoft SQL Server and Sybase databases. Otherwise please download a Microsoft SQL Server or Sybase JDBC driver before you start the JobScheduler installer.

If you want to use a Windows domain user instead of an SQL user for the Microsoft SQL Server connection then please read the How to connect to an SQL Server with a domain account article for more details.

3.3 PostgreSQL

PostgreSQL requires PL/pgSQL. Check the languages that are available for your database by using:

createlang -U postgres -l scheduler

where postgres is the user name and scheduler is the database name. createlang is available from the PostgreSQL bin directory. If plpgsql is not be listed in the output of this command then please enable this language by:

createlang -U postgres plpgsql scheduler

The following two PostgreSQL server variables must have the following values:

  • standard_conforming_strings = off
  •  bytea_output = 'escape'

For all those that do not want to change this globally, this setting can be changed on a per user level:

Example: Set standard_conforming_strings and bytea_output per user leve
alter user scheduler set standard_conforming_strings = off; 
alter user scheduler set bytea_output = 'escape';

where "scheduler" is the user name of the JobScheduler database.

IBM DB2

For IBM® DB2 you have to provide a license file for the driver too. As this driver will also be required by the JobScheduler later on, it will  copied by the setup into the $SCHEDULER_HOME /lib/user_lib folder.

3.4 Manual Creation of Database Tables

SQL scripts which create the database tables required by the JobScheduler are available if they not have been correctly created by the setup program. These scripts can be run using $SCHEDULER_HOME /install/scheduler_install_tables.(sh|cmd).

Ensure that the database connection is correctly entered in the $SCHEDULER_DATA/config/sos_settings.ini configuration file.

 

 

  • No labels