ConfigurationMonitor

The configuration monitor is a preprocessor java class that implements the spooler_process_before api method. It does the following:

Reading parameters from a configuration file
The name of the configuration file is the <job_chain_name>.config.xml
The parameters are only available for the node they are defined for.
The values of the parameters can contain patterns to identify values that are to be substituted
The default pattern is ${param}

Since 1.11.0 a new implemetation for the configuration monitor have been introduced. The new implementation is much faster than the old one. It is compatible for the standard use of the monitor.

Feature	since 1.11	old implementation
Name of the implentation class	`com.sos.jitl.jobchainnodeparameter.monitor.JobchainNodeSubstituteMonitor`	`sos.scheduler.managed.configuration.ConfigurationOrderMonitor`
Multi substitution	yes	yes
Substitution source	Environment variables Task paramters global scheduler parameters node parameters System properties	Environment variables Task paramters global scheduler parameters node parameters file content (with file_content:)
Substitution patterns	${param} %param%	${param}
Integration with JOE	JOE uses the new class name when inserting a configuration monitor from the favourite list if never bevor a configuration monitor has been used. If JOE has been updated from an older version and already a configuration monitor has been assigned JOE uses the old implementation You can change this behaviour in the configuration file $scheduler_data/config/scheduler_editor.ini `monitor_favorite_java_configuration_monitor=com.sos.jitl.jobchainnodeparameter.monitor.JobchainNodeSubstituteMonitor`	JOE uses the old class name when inserting a configuration monitor from the favourite list See in the configuration file $scheduler_data/config/scheduler_editor.ini `monitor_favorite_java_configuration_monitor=com.sos.jitl.jobchainnodeparameter.monitor.JobchainNodeSubstituteMonitor`
Configuration file name	The default configuration file name is <job_chain>.config.xml Then name of the file can be change by using the parameter `configurationMonitor_configuration_file`	The default configuration file name is <job_chain>.config.xml Then name of the file can be change by using the parameter `configurationMonitor_configuration_file` With a naming convention there can be different configuration file to be described

Substitution algorithmism	Uses implentation of org.apache.commons.lang3.text.StrSubstitutor	Uses Code from SOS.
Parameter for configuraiton Path	configurationMonitor_configuration_path Default: folder where the job chain is located	ConfigurationBaseMonitor.configuration_path Default: folder where the job chain is located
Parameter for configuration file	configurationMonitor_configuration_file Default: <job_chain>.config.xml	ConfigurationBaseMonitor.configuration_file Default: <job_chain>.config.xml
Use with Agents	The first job of the job chain must run on the master and must have the configuration monitor	The first job of the job chain must run on the master and must have the configuration monitor
Attribute name in elemen <job_chain>	The attribute name in the element <job_chain> in the configuration file is not considered	The value of the attribute name in the element <job_chain> in the configuration file must be the same as the name of the job chain that uses this configuration file
Parameter scheduler_order_additional_envvars	Not implemented

Space shortcuts

Page tree