...
We recommend that the following syntax is used for the names of job nodes that are to be processed in parallel:
"node name of the splitter job
...
" ":" "job name".
...
For example split_partitions:export_table_partition_1
...
(see Best Practice - Parallel nodes).
The use of the above syntax is not necessary for the correct functioning of the JobScheduler.
Splitter job parameters
See documentation of the JobChainSplitter job.
...
A unique sync job is required at the end of every group of processes running in parallel (see Setting_up_a_sync_job) when the nodes in the job chain after the sync node are only to be processed after all the jobs (tasks) that are to be carried out in parallel have been completed without errors (see Best Practice - Give each sync job a unique name).
Each sync job has to be unique within a JobScheduler instance - and within a job chain - as long as a cross-over pattern has not been implemented (see Synchronizaton of Job Chains).
For more information see the documentation for the JobSchedulerSynchronizeJobChains job.
Best practice
Use "Start" and "End" nodes:
We recommend that you use our /sos/jitl/JobChainStart start job as the first node in every job chain and our /sos/jitl/JobChainEnd end job as the last full node.
Give each sync job a unique name:
Give each sync job a unique name by using the name of the job chain in which the sync job is included as a prefix in the name of the sync job.
- For example: ideal_insert_to_export_table_parallel.sync_partitions
Follow our convention for node naming:
Splitter nodes
We recommend that you use the following syntax for the names of job nodes that are processed in parallel:
- "splitter job node name" ":" "job name". In the example diagram above, one of the first nodes would then have the name split_partitions:partition_1.
This syntax allows the diagram algorithm in JOE to draw job chain diagrams and correctly display the nodes that directly follow on from the splitter. It is necessary to use this type of job name syntax for the algorithm as the syntax used by JobScheduler does not recognize predecessor relationships (only successors).
Parallel nodes
We recommend that you use the following syntax for the names of job nodes that are processed in parallel:
"splitter job node name" ":" "job name".
In the example described above, one of the first nodes would then be split_partitions:export_table_partition_1.
This allows the diagram algorithmus in JOE to know and correctly display the nodes that directly follow on from the splitter. This is because the JobScheduler syntax does not recognise predecessor relationships (only successors).
Job nodes
As far as possible, the names of job nodes should identical to the job names (poss. without the folder name). If a job is used more than once in a job chain, then the node name can be uniquely specified using a letter or number as a suffix.
Error nodes
The name of the error node should either contain the job name or be identical with it. This means that in the event of an processing error in the job chain, it is possible to see immediately in JOC the point in the job chain where the abnormal termination occured.
In addition, the name should start with an "!" (an exclamation point, or with another unique special character). This makes it easier to see in the order history in JOC that the job chain has terminated abnormally.
See also:
see also
- Documentation of jobs JobSchedulerSynchronizeJobChains.
- Examples for the use of sync jobs see JobScheduler FAQ - How to syncronize jobs.
- JobSchedulerSynchronizeJobChains.
- Examples for using Sync-Jobs see JobScheduler_FAQ
- Best Practice.
Downloads
You can download the example described in this FAQ : insert_to_export_table_parallel.zip.