Page History

...

The ease of this method means that job execution on remote JobSchedulers can be more flexibly allocated than with process class based methods. In particular, it allows the decision about which JobScheduler a job is to be executed on to be made dynamically, for example, depending on the result of the preceeding 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, thereby considerably increasing flexibility and reducing maintenance.

...

• The remote JobScheduler can be either a workload instance or an Agent.
• Job, job chain and order configuration data is only transferred to the remote JobScheduler as required, JobScheduler objects are not saved on the remote JobScheduler.
• The operations carried out on the remote JobScheduler are recorded in log files in the $SCHEDULER_DATA/logs directory as defined in the JobScheduler Master - Installation Guide.
• Log information for the operations carried out on the remote JobScheduler is also saved in the $SCHEDULER_DATA/logs directory of the 'main' JobScheduler.

...

• Example for complex dynamic setting of remote JobSchedulers

See also

• Dynamic (setting of the) JobScheduler agentHow to dynamically assign JobScheduler Agents to a job