Page History

...

An additional substitution mechanism for jobs running in a job chain is provided by the sos.scheduler.managed.configuration.ConfigurationOrderMonitor preprocessing Java class that is added as a Monitor to jobs:.

Scope of substitution

This Java class implements the following steps:

...

• If a task parameter value is to be substituted by the Configuration Monitor then the value has to be quoted with a backslash to prevent its substitution by the JobScheduler
  • Example: a value \${param}
• With the parameter setting scheduler.order.keep_order_content_on_reschedule=true the values will be substituted only in the first run.
• When using node parameters then the Configuration Monitor has to be assigned to the job
  • JOE will assign the Configuration Monitor automatically when configuring a node parameter in a job chain
  • Should no substitution be performed then please check if the Configuration Monitor is assigned to the job. Otherwise assign parameters individually by using JOE.

Handling of substitution up to release 1.10

• Performance of parameter subsitution is an issue:
  • 10 node parameter: 4s
  • 20 node parameter: 6s

Handling of substitution starting with release 1.11

• Performance of parameter substitution is restored to a normal range:
  • 20 node parameters <= 2s

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-276

Substitution of parameter values by JITL Jobs that extend the JobSchedulerJobAdapter base class

...

This article describes the substitution mechanisms for JITL Jobs that extend the JobSchedulerJobAdapter base class.

Scope of substitution

Substitution is carried out for:

...

Note: Substitution applies exclusively to the current job run. This means that the values of the parameters will be unchanged after the execution of the job. If you have an order parameter param_x whose value is value is ${param_y} and there are two steps in the job chain, the value of param_x after the execution of the first node will still be value is ${param_y}

Handling of substitution up to release 1.10

• Parameters with the name param  and scheduler_param_param will be handled as being identical.
• Parameters with the name param_plus_any_understrikes and paramplusanyunderstrikes will be handled as being identical.

Handling of substitution starting with release 1.11

• No alias parameters as up to release 1.10 are supported.

• Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-276

List of special parameters

...