Skip to end of metadata
Go to start of metadata

JITL: The Managed Database Job



This job uses the deprecated sos.scheduler.managed.JobSchedulerManagedDatabaseJob that has been deprecated with Release 1.12.

The JobSchedulerManagedDatabaseJobSOSHibernate job is provided as an alternative.

This job is used to execute (SQL-)statements in a database and can be used standalone or triggered by orders - i.e. as an order job.
It can execute database procedures or SQL statements.

(A general overview of all JITL jobs can be found Library of Standard Jobs - JITL).

The description JobSchedulerManagedDatabaseJob.xml is stored in the ./jobs directory of the JobScheduler installation.

The SQL instructions are written in the command parameter.
It is possible to define more than one instruction in the command parameter.
Such instructions are then carried out in the order in which they are written and must be separated by a semicolon and a subsequent new line.

You can use 
 as newline.

The following is an example of a job chain in which the command contains two statements separated by 

The job chain launchDB.job_chain.xml:

The order launchDB,updateMyTable.order.xml:
It contains an update statement and a commit.

The job launchDB.job.xml (i.e. with a MySQL database connection, examples for other DBMS see below): It executes the statements where the statement in the order command parameter overwrites the statement in the job command parameter.

MySQL (MariaDB)

For other database management systems you have to modify the connection parameter like in the following examples:

MS SQL Server


See also: