Page History

...

The ease with which this method allows remote JobScheduler's to be set means that job execution on remote JobSchedulers can 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 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.

...

Operation details

• The remote JobScheduler has to can be either a 'full' JobScheduler and not 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 - Installation Guide
• Log information for the operations carried out on the remote JobScheduler is saved in the $SCHEDULER_DATA/logs directory of the 'main' JobScheduler.

A simple scheduler.remote_scheduler example

...

To get the example ready to use, simply unpack the 'remote_scheduler_variable_demo.zip' file into the 'live' folder of the 'main' JobScheduler that will be controlling the remote onesone(s).

If you then open the folder containing the example in JobScheduler's JOE interface you will see that the example consists of a job chain ("Job_Chain_1") with three nodes ("Start", "Job_1" & "End") and two orders:

...