Page History

...

This example shows how job chain node parameters can be defined configured in an order and assigned to specific job chain nodes.

...

As already described above, the values of the jobParam and orderParam parameters are substituted into the orderNodeParameter at the 200 node of the job chain.

Running the example

• Open the JobScheduler Operating Center, JOC, in your browser using http://scheduler_host:scheduler_port
• Open the JOB CHAINS tab and enable "Show orders".
• Start the order1 usingOrder Menu / Start order now as shown in the screenshot:

...

• Image Modified

• Opening the log file for the order (clicking on the order ID in the Order History pane - in the bottom right of the above screenshot) will show that at step 100 the job1 shell script will give out the value for the orderNodeParam defined in the order:

  Code Block
  language xml
  [stdout] job1: Value of orderNodeParam = 100

• At step 200 the shell script will give out the value for the orderNodeParam defined in the order (200) together with the values set for the orderParam and jobParam:

  Code Block
  language xml
  [stdout] job1: Value of orderNodeParam = 200 Parameter-value-from-job - Parameter-value-from-order

Use with API Jobs

At the time of writing (current releases are 1.8.4, 1.9.8 and 1.10.2) the above example works with shell jobs and not with API jobs - which includes many of the JITL jobs.

...

Example showing job chain node parameters defined for the job chain

This example shows how job chain node parameters can be configured for a job chain and assigned to specific nodes in that chain.

In addition, the example shows how these parameters can be called in shell jobs and used together with global variables.

Example Download

• You can download the example here.

Downloads

• You can download the example:
  
  • 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 before the <security> element:

  Code Block
  <params> <param name="global_configuration_params" value="config/global_scheduler_vars.xml"/> </params>

...