A Standard job is a grouping of several loads that are carried out consecutively. A job may also contain and combine other jobs that are executed as sub-jobs.
Once a new job has been created, jobs and loads can be allocated to it. More than one load can be assigned to a job. For example, you could create the dimensions in a first job and fill a cube with data in a second job.
By default, when several Jedox Integrator jobs are executed, only one job runs at a time and all other jobs are queued. When the first job is terminated, the next job will start running and so on.
Standard jobs can be parameterized with variables. If a value is defined in the job, then that particular value will be used for the execution of the job; if not, then a default value will be used. For more information, see Integrator Variables.
Fail on status
If the job executes several loads or sub-jobs, the selected option defines the behavior in case of a warning or an error message in one of the loads or sub-jobs. The options are described below.
| none | All subsequent loads or sub-jobs are executed even if errors or warnings occur. The job terminates with "Completed with warnings" or "Completed with errors" or "Completed successfully". |
| error | In case of an error message, the job terminates without executing subsequent loads or sub-jobs and the job terminates with status "Failed". In case of warnings subsequent loads or sub-jobs are executed and the job terminates with "Completed with warnings". |
| warning | In case of a warning or an error message, the job terminates without executing subsequent loads or sub-jobs and the job terminates with status "Failed". |
| inherit | If the job is executed directly (without parent job) it uses failOnStatus "error". Otherwise if the job is used as a sub-job it inherits the failOnStatus of its parent job (see corresponding descriptions of these failOnStatus options above). |
Closing connections after jobs
At the end of a job, all open connections to source and target connections are closed. However, this is not necessarily happening at the end of each subload contained in a job. As a consequence, there is a difference in behavior when grouping several loads directly in a job and when grouping subjobs each containing one load. If you want to force the closing of connections immediately after the termination of a load, create individual jobs for each load and assign a single load to each of them.
Updated February 7, 2024