...
- Job chain node parameters for orders are defined in a similar manner to conventional order parameters - but using a special syntax.
- Job chain node parameters for the job chain itself are defined ina in a job chain parameter file. The jobs in the job chain use a special monitor to read the job chain parameter file.
...
- transfer a file by FTP to host a,
- transfer a file by FTP to host b,
- delete file.
The Job chain node parameters allow the same job could to be used for both steps 1 and 2 but with different parameters each time.
Article Scope
Two example job chains are described in this article:
- The first uses job chain node parameters defined for an order and demonstrates referencing of global parameters.
- The second example uses job chain node parameters defined for the job chain itself.
Example showing job chain node parameters defined for an order
To be done
Example showing job chain node parameters defined for the job chain
Downloads
- job_chain_node_params.zip - configuration files
Instructions
- Unzip all files into the
./config
folder of your JobScheduler installation. Open
config/scheduler.xml
and add the following lines right before the<security>
element:Code Block <params> <param name="global_configuration_params" value="config/scheduler_global_vars.xml"/> </params>
...
Nothing special so far. The next section explains how these resulting parameters were configured.
How it works
The job chain chain_a
consists of two steps, "first" and "second". Both steps use the same job readparam
. The readparam
job is a small JavaScript job which reads all order parameters and logs them on info
-level.
The Java monitor implementation
The sos.scheduler.managed.configuration.ConfigurationOrderMonitor
is configured as a monitor for the job. This is a special pre/post-execution script which is included in the JobScheduler distribution. It can be used for all jobs.
...