Page History
...
- This job template makes use of JDBC connections and the Hibernate database access layer.
- This job template can be used to access any database for which a JDBC Driver is available with for on the Agent.
- JS7 includes a number of JDBC Drivers for supported DBMS, see the JS7 - Database article.
- For other DBMSs users can provide an individual JDBC Driver and store the that Driver's .jar file in the .
/lib/user_lib
directory of the Agent installation.
- This job template supports use of a JS7 - Credential Store.
- Delimitation:
- Note that specific SQL language extensions such as Oracle® PL/SQL are not supported by Hibernate.
- For Oracle® PL/SQL use the JS7 - JITL PLSQLJob.
- For Oracle® SQL*Plus use the JS7 - JITL SQLPLUSJob.
The job supports encryption of database credentials if used with a Hibernate configuration file, see JS7 - How to encrypt and decrypt Database Credentials.
Usage
When defining the job either:
...
Name | Required | Default Value | Purpose | Example |
---|---|---|---|---|
command | yes | Carries the SQL statements. | ||
| no | ./config/hibernate.cfg.xml | Specifies the configuration file (XML) format for Hibernate connections, see JS7 - Database. By default Agents ship without hibernate configuration files. However, if a file with the default name is available then it will be applied. | |
| no | Raises a warning if the SQL statement creates a result set. | ||
| no | If stored procedures are called that which return a result set are called then this argument has to be set to | ||
| no | Specifies how a result set is forwarded to order variables for subsequent jobs:
| ||
result_file | no | Specifies the path to an output a result file if the resultset_as_variables argument is used with one of the value values csv, xml, json . An absolute path can be specified and a relative path can be used that which starts from the Agent's working directory. | ||
credential_store_file | Location of a credential store database (*.kdbx) | false | ./config/private/jobs.kdbx | |
credential_store_key | Location of a credential store key file (*.key) | false | ./config/private/jobs.key |
...
- The cancel operation is applied to the order, not to the SQLExecutorJob. In case of cancellation the job will continue until completion and the order will be put in set to the failed state.
- The cancel/killforce operation is applied to the order and to the job. The SQLExecutorJob will be forcibly terminated, any transactions will be killedrolled back, the database connection will be closed and the DBMS session will be terminated. The order will be put in set to the failed state.
- The DBMS decides about rolling back transactions when closing the client session.
Further Resources
- JS7 - JITL PLSQLJob
- JS7 - JITL SQLPLUSJob
- JS7 - JITL Common ParametersVariables
- JS7 - Job Resources
- JS7 - Use of Credential Store with JITL Jobs
...