Page History

...

• 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 and also demonstrates referencing of global parameters.

Example showing job chain node parameters defined for an order

Job Node Parameters

...

This example shows how parameters can be defined in the order configuration and

...

assigned to a specific job chain nodes.

Example Download

• You can download a sample from here node.

Parameter definition

• The syntax for these order parameters that are specific to a job chain node is <node>/<name>

Scenario

• .
  (This is in contrast to the standard order parameter syntax of <name>.)

A parameter named order_param to be made available to If you have a job chain node with a node 100 then you can specify state 100 is specified a parameter with the name 100/order_param. The job in the node 100 then has access to the parameter order_param. In the other nodes this parameter This parameter will not be available at other nodes in the job chain.

• Substitution will be done for the order node parameter.
• If you have a A job chain node parameter with the same name then it will be overwritten by the order node parameter.
• You can use order Order node parameters if you did not define any can be used if job chain node parameters and therefore did not create a job chain configuration file.have not been defined and a job chain configuration file has not been created.

Here is the job chain with two nodes:

Image Added

The order defines the parameters for the job chain node.

Image Added

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.

A fix for this issue is planned - for more information see

Workaround for API & JITL Jobs

To activate the order node function please add the configuration monitor to the pre-processing element of the job

...

at the job node.

...

 Example for assigning a configuration monitor

...

Code Block
language xml
<job stop_on_error="no" order="yes" name="job2"> .... <monitor name="configuration_monitor" ordering="0"> <script language="java" java_class_path="" java_class="sos.scheduler.managed.configuration.ConfigurationOrderMonitor"/> </monitor> /job>

This job will be used in both job nodes of the sample job chain. Please consider the pre-processing:

 

Image Removed

Here is the job chain with two nodes:

 

Image Removed

The order defines the parameters for the job chain node.

 

Image Removed

 

Related Downloads

...

In the above example the same job is used at both nodes of the sample job chain. The configuration monitor is defined in JOE as shown in the next screenshot:

Image Added

Example showing job chain node parameters defined for the job chain

...

• 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/global_scheduler_global_vars.xml"/> </params>

• Restart the JobScheduler
• Open the JobScheduler Operating Center, JOC, in your browser using http://scheduler_host:scheduler_port
• Open the JOB CHAINS tab and enable "Show orders".
• Find the job chain samples/configuration/chain_a.
• Find the order my_order, open the order menu and choose "Show log".

...

State:second
       param1=10
       param2=xyz
       param4=xyz---def

Nothing special so far. The next section explains how these resulting parameters were configured.

...