Threading | Active Scripts | SDZeCOM Threading Orchestrator
This script is used for monitoring and controlling export/import chains.
In such chains, Run Next starts subsequent jobs, with the last one restarting the first one. This leads to problems, for example, during nightly web container restarts.
With the Orchestrator, all parallel jobs provided by CentricTM are always used optimally and problems caused by interruptions due to web container restarts are intercepted.
Run the script at short intervals, e.g., every 15 minutes.
Field | Description |
Designation | Name of the context |
Categorie | SDZeCOM Threading If you append further text to the category name, a separate folder is generated. |
Description |
|
Script | SDZeCOM Threading Orchestrator |
Scripts to check | Select all Starters to be monitored and controlled. |
Script to start jobs from | Select the Starter (if necessary, the first of several connected in series) to be restartet. |
Example:
Import-Starter 3 starts at 01:00 h.
At 01:30 h, the server goes down for maintenance.
The server returns online at 05:00 h.
The Orchestrator starts at 05:15 h. and detects that Import Starter 3 is no longer running.
The Orchestrator starts the chain from Import Starter 1. However, since Import Starter 1 and Import Starter 2 have already been completed, Import Starter 3 is started directly.
