1 Configuring the Job Scheduler - SOS-Berlin

Configuring the Job Scheduler 22
Use of this directory takes the definitions of jobs, job chains and other objects away from the Job Scheduler - see
(page 81).
configuration_add_event="job_path" Job for Creating a New Configuration File
The job in question is started when the Job Scheduler loads a new file from its configuration directory.
The job is started when allowed by its parameter. It should be defined in the Job Scheduler
configuration file, so that it is recognised when the Job Scheduler reads the configuration directory.
The task which is started by this job has three parameters (which can be reached using Task.params ):
The following task parameters are available as environment variables SCHEDULER_LIVE_EVENT,
SCHEDULER_LIVE_FILEPATH and SCHEDULER_LIVE_FILEBASE.
configuration_modify_event="job_path" Job for Modifying a Configuration File
The job in question is started when the Job Scheduler loads a modified file from its configuration directory.
The job is started when allowed by its parameter. It should be defined in the Job Scheduler
configuration file, so that it is recognised when the Job Scheduler reads the configuration directory.
Parameters and environment variables are set as for .
configuration_delete_event="job_path" Job for Deleting a Configuration File
The job in question is started when a file which has been loaded by the Job Scheduler is removed from its
configuration directory.
The job is started when allowed by its parameter. It should be defined in the Job Scheduler
configuration file, so that it is recognised when the Job Scheduler reads the configuration directory.
Parameters and environment variables are set as for .
supervisor="host:port"
The supervisory Job Scheduler, at which the current Scheduler should log on and off. This takes place
asynchronously and errors do not affect operation.
No more than 4 other (Workload) Schedulers should log on to a supervisory Job Scheduler running on Windows.
The supervisor can set the configuration for the Workload (secondary) Job Schedulers, see. (page 20). The Job Scheduler retains this new configuration in its
cache directory.
spooler_id="spooler_id"
This element is only effective when its attribute is identical to the -id= parameter which was set as the Job
Scheduler was started, or when the -id= parameter was not set as the Job Scheduler was started.
port="number" (Initial value:0) Port Number for TCP and UDP
Combines the tcp_port and udp_port settings.
See also (page 20). and (page 20).
Software- und Organisations-Service GmbH November 2011