...
- Unzip all files in the download file into the
./configfolder of your JobScheduler installation. Define a global scheduler variable:
Open the
config/scheduler.xmlfile and add the following lines before the<security>element:Code Block <params> <param name="global_test_var" value="def"/> </params>
- Restart the JobScheduler
- Open the JobScheduler Operating Center, JOC,
- the JOC Cockpit in your browser using http://scheduler_host:scheduler_port
- Open the JOB CHAINS view.
- Navigate to the folder
samples/configuration/chain_a - Click
Expand Details - Find the job chain
samples/configuration/chain_a. - Start the order by choosing "Start order now" from the Order menu.
- Watch Open the log file
The order will run through both steps of the job chain. In each step the order parameters will be logged by the job. The parameters param1 - param4 should be shown in the log file with the following values:
...
The next section explains how these resulting parameters were configured.
...
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.
In the JobScheduler Object Editor, JOE, the monitor implementation is called under JobScheduler Objects.Jobs.Jobname.Pre-/Post-Processing as a Java configuration_monitor. The monitor reads special job chain parameter files which set parameters for a job chain and are able to configure each node of a job chain individually. These parameter files are named by default according to the pattern myJobChain.config.xml. See How to configure a Named Monitor for more information.
The screenshot below shows the monitor configuration in JOE.
...
Note that the node parameters - param3 and param4 are set and edited using JOE's XML editor, which is accessed using the OpenXML button shown in the screenshot.
(See also the Example in Detail section below.)
The example in detail:
When using hot folders, the The configuration monitor looks for the job chain parameter file in the current hot live folder and expects the name job_chain_name.config.xml. So in this case, the name of the job chain parameter file is chain_a.config.xml.
...