Starting jobs on different servers using process classes for remote execution
- JobScheduler can execute jobs on different servers.
- Such jobs can be distributed in a way that within one job chain the respective jobs are executed on different servers.
A job chain contains 3 jobs, i.e. TaskB1, TaskB2, TaskB3.
A user wants to configure TaskB1 to be executed on server ServerA (localhost), TaskB2 to be executed on server ServerB (Windows) and TaskB3 on server ServerC (Linux).
JobScheduler can execute jobs on remote JobScheduler instances, by JobScheduler Agents or by SSH.
In this example JobScheduler will execute jobs on remote JobScheduler instances using a process class.
- A JobScheduler process class is similar to a connection configuration where the remote JobScheduler's host name and port number are defined.
- With that process class being defined jobs can be configured to use the process class for remote execution.
- JobScheduler will excute jobs on the remote JobScheduler instance and that instance will report back the status and the log to the local JobScheduler.