Graph config properties

Each graph may have set of config properties, which are applied during graph execution. Properties are editable in web GUI section "sandboxes". Select graph and go to tab "Config properties".

The same config properties are editable even for each sandbox. Values specified for sandbox are applied for each graph in the sandbox, but with lower priority then config properties specified for graph.

If neither sandbox or graph have config properties specified, defaults from main server configuration are applied. (See Chapter 16, Configuration for details)

In addition, it is possible to specify additional graph parameters, which can be used as placeholders in graph XML. Please keep in mind, that these placeholders are resolved during loading and parsing of XML file, thus such graph couldn't be pooled.

Table 3.4. Graph config parameters

Property nameDefault valueDescription
tracking_interval2000Interval in ms for sampling nodes status in running graph.
max_running_concurrentlyunlimitedMax number of concurrently running instances of this graph.
enqueue_executionsfalseBoolean value. If it is true, executions above max_running_concurrently are enqueued, if it is false executions above max_running_concurrently fail.
log_levelINFOLog4j log level for this graph executions. (ALL | TRACE | DEBUG | INFO | WARN | ERROR | FATAL) For lower levels (ALL, TRACE or DEBUG), also root logger level must be set to lower level. Root logger log level is INFO by default, thus graph run log does not contain more detail messages then INFO event if graph config parameter "log_level" is set properly. See Chapter 19, Logging for details about log4j configuration.
max_graph_instance_age0Time interval in ms which specifies how long may graph instance last in server's cache. 0 means that graph is initialized and released for each execution. Graph cannot be stored in the pool and reused in some cases (graph uses placeholders using dynamically specified parameters)
classpath List of paths or jar files which contain external classes used in the graph (transformations, generators, JMS processors). Separator is specified by Engine property "DEFAULT_PATH_SEPARATOR_REGEX". Path must always end with slash character "/". Server automatically adds "trans" subdirectory of graphs's sandbox.
skip_check_configdefault value is taken from engine propertySwitch which specifies whether check config must be performed before graph execution.
password Password for decoding of encoded DB connection passwords.
verbose_modetrueIf true, more descriptive logs of graph runs are generated.
use_jmxtrueIf true, graph executor registers jmx mBean of running graph.
debug_modefalseIf true, edges with enabled debug store data into files in debug directory. See property "graph.debug_path"

Graph config properties

Figure 3.9. Graph config properties