Page tree
Skip to end of metadata
Go to start of metadata

Using the features of the Jabatix Job Control System (JCS) on a Jabatix server requires several definitions in a process flow. 

Defining a Job

The minimuml requirement for using JCS is to create a special type of process flow.

First, create a new process flow. In the creation wizard, you can choose several types of process flow. Select the type Job.

There are further options available that define the behaviour of a job.

  • Restartable → defines if the job is restartable after a processing error, e.g. a lost database connection.
  • Concurrent → defines if the defined job can be started multiple times or only once. Checking the concurrent option allows the job to be run multiple times.

The type of process flow can be changed anytime. Select the process flow to be changed, open the context menu and select Change Type. In the edit window, you can select now the new process flow type.


Defining a Sub-Job

The process flow type sub-job also defines the visible structure in the job execution hierarchy on the server. Job defines the root node and sub-job defines a child node. A sub-job can also be a part of another sub-job.


Click Scheduling Button:

The configuration window for Process Flow Scheduling opens. To define a trigger, open the context menu in the group Dynamic Scheduling and choose Add trigger:

A new record will be created. The possible settings are as follows:

Mandatory: Type

The type defines the moment of processing. 

  • Start_ → the sub-job will be started at the start of the defined process flow, layer and/or action
  • End_  → the sub-job will be started at the end of the defined process flow, layer and/or action
Mandatory: Model

Defines the model, in which a job or sub-job will be checked for execution.

This can be the model where the initial process flow is defined or the referenced model. The referenced model must also be available on the server.

Mandatory: Process flow

Defines the process flow that is going to be checked for execution.

Optional: Layer 

When a layer is defined, the execution will be evaluated at layer level.

Optional: Action

An action is the least entity within a process flow. The evaluation will be performed at action level.


This option sets whether the job is started synchronously or asychronously.

  • Sync → set the job to be executed synchronously
  • Async → set the job to be executed asynchronously

As shown in the sample configuration, the process flow flagged as a sub-job with the defined scheduling will be executed whether the defined process flow has been finished or not.

Optional Job Design

In order to define children of a job, create process flows containing sub-jobs and job steps.

To do so, a job starts sub-jobs. These sub-jobs then start a job step. The job step contains the processing logic.

For example, the following job tree can be defined:

The  job tree example can be explained as follows:

→ Job:

(Job starts) → Job Step (Processing)

(Job starts) → Sub Job:

(Sub Job starts) → Job Step (Processing)

(Sub Job starts) → Job Step (Processing)

(Job starts) → Sub Job :

(Sub Job starts) → Job Step (Processing)

(Job starts) → Job Step (Processing)





  • No labels