| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
THIS PAGE IS 'WORK IN PROGRESS'
There are a number of techniques available for a JobScheduler to control job execution on remote servers:
- SSH;
- Using a JobScheduler agent (Dynamic (setting of the) JobScheduler agent).
Up till now, process classes have been used to define Whilst the possibilities offered by SSH execution are limited (see What is the difference between SSH-Job execution and remote JS-Agents?), the possibilities offered by Agents or remote JobSchedulers has also been restricted, due to the need for process classes having to be defined for the JobScheduler a job is to be executed on.
This has Process classes have had the disadvantage that instances of the job chain and job have to exist (and be maintained) on every JobScheduler that the job is to be (potentially) executed on.
...