...
JobScheduler can execute distributed jobs on different servers. Example JobChain contains 3 jobs i.e. TaskB1, TaskB1TaskB2, TaskB1TaskB3. User want to configure that TaskB1 runs on the server ServerServerA ( localhost) , TaskB2 runs in server ServerB(Windows) and TaskB3 ServerC(Linux). JobScheduler can execute jobs on remote JobScheduler instance, {{JS} Agents or over SSH. In this example JobScheduler will execute jobs on remote JobScheduler instances using process class. JobScheduler process_class is like a connection configuration where remote JobScheduler's host name and port number is defined. Once process_class is defined Job's can be configured to use process_class assigned to remote JobScheduler as target.
JOE diagram of JobChain
...
JobB1
| Code Block | ||
|---|---|---|
| ||
Process_Class
| Code Block | ||||
|---|---|---|---|---|
|
<?xml version="1.0" encoding="ISO-8859-1"?>
<job_chain visible="yes" orders_recoverable="yes" title="JobChainA_P">
<job_chain_node state="Start" job="/sos/jitl/JobChainStart" next_state="Split" error_state="Error"/>
<job_chain_node state="Split" job="/sos/jitl/JobChainSplitter" next_state="Sync" error_state="Error"/>
<job_chain_node state="Split:Job01_P1" job="Job01_P1" next_state="Sync" error_state="Error"/>
<job_chain_node state="Split:Job02_P2" job="Job02_P2" next_state="Sync" error_state="Error" delay="30"/>
<job_chain_node state="Split:Job03_P3" job="Job03_P3" next_state="Sync" error_state="Error"/>
<job_chain_node state="Sync" job="Sync_job_chain_parallel" error_state="Error" next_state="Job04"/>
<job_chain_node state="Job04" job="Job04" next_state="End" error_state="Error"/>
<job_chain_node state="End" job="/sos/jitl/JobChainEnd" next_state="Success" error_state="Error"/>
<job_chain_node state="Success"/>
<job_chain_node state="Error"/>
</job_chain>
||||