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 the JobScheduler a job is to be executed on.
This has 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.
The technique described on this page has been introduced with JobScheduler version 1.7 and allows a job in a job chain to be executed on a remote JobScheduler without the need for a job chain or the job itself to be installed in the live folder of the remote JobScheduler. This means that job execution on remote JobSchedulers can more flexibly allocated than with process class based methods to the extent of the decision about which JobScheduler a job is to be executed on depending on the result of the preceding job. In addition, only one instance of the job and job chain need to be defined in the live folder of the 'main' JobScheduler.