| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Introduction
There are a number of methods available for controlling job execution on remote servers with JobScheduler. The most important of these are:
...
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.
Method of operation
- The remote JobScheduler has to be 'full' JobScheduler and not 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/logsdirectory as defined in the JobScheduler - Installation Guide
A simple scheduler.remote_scheduler example
A scheduler.remote_scheduler example has been prepared and can be downloaded from:
...
used to set up a simple remote scheduling demonstration.
To run the example you only need two JobSchedulers, one of which is to be used as the main JobScheduler and the other as the remote.
Note that scheduler.remote_scheduler only works when both the main and remote JobSchedulers are
...
version 1.7
...
or newer.
Download the example
To get the example ready to use, simply unpack the 'remote_scheduler_variable_demo.zip' file into your JobSchedulerthe 's 'live' folder of the 'main' JobScheduler that will be controlling the remote ones.
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:
...
A scheduler.remote_scheduler parameter is not set in the "Order_1_Local" order and therefore when started with this order "Job_1" will be executed by default on your local computer. The name of your local computer or host (depending on the operating system - see above) will be entered in the log file.
Application in a Production Environment:
In a production environment, particularly one where a large number or remote servers were being addressed, the scheduler.remote_scheduler parameters would be saved in an .inc file, which would be loaded as required.
...