CloverDX creates new classloaders when necessary to load a class in runtime. For example, a Reformat component with a Java transformation has to create a new classloader to load the class. It is worth noting that classloaders for JDBC drivers are not re-created. Classloader cache is used to avoid PermGen out of memory errors (some JDBC drivers automatically register themselves to DriverManager, which can cause that the classloader cannot be released by the garbage collector). This behavior can be inconvenient, for example if you want to share POJO between components. For example, a Reformat component creates an object (from a jar file on runtime classpath) and stores it into a dictionary. Another Reformat component recovers the object from the dictionary and attempts to cast the object to the expected class. ClassCastException is thrown due different classloaders used in the Reformat components. Using this flag you can force Clover Server to re-use classloader when possible.

List of paths or jar files which contain external classes used in the job file (transformations, generators, JMS processors). All specified resources will be added to the runtime classpath of the transformation job. All CloverDX Engine libraries and libraries on application-server's classpath are automatically on the classpath. Separator is specified by the Engine property DEFAULT_PATH_SEPARATOR_REGEX. The directory path must always end with a slash character "/"; otherwise, ClassLoader doesn't recognize it is a directory. Server always automatically adds trans subdirectory of job's sandbox, so it doesn't have to be added explicitly.

List of paths or jar files which contain external classes used in the job file (transformations, generators, JMS processors) and related libraries for their compilation. Please note, that libraries on application-server's classpath are not included automatically. Separator is specified by the Engine property DEFAULT_PATH_SEPARATOR_REGEX. The directory path must always end with a slash character "/"; otherwise, ClassLoader doesn't recognize it is a directory. Server always automatically adds a SANDBOX_ROOT/trans/ directory and all JARs in the SANDBOX_ROOT/lib/ directory, so they don't have to be added explicitly.

If true, edges with debug enabled will store data into files in a debug directory.

Without explicit setting, running of a graph from Designer with server integration would set the debug_mode to true. On the other hand, running of a graph from the server console sets the debug_mode to false.

If true, the system will remove temporary files produced during previous finished runs of the respective job.

This property is useful together with enabled debug mode ensuring that obsolete debug files from previous runs of a job are removed from temp space. This property is set to true by default when executing job using Designer-Server integration.

Boolean value.

If true, executions above max_running_concurrently are enqueued,

if false, executions above max_running_concurrently fail.

Log4j 2 log level for this graph executions. (ALL | TRACE | DEBUG | INFO | WARN | ERROR | FATAL). For lower levels (ALL, TRACE or DEBUG), root logger level must be set to lower level, as well. Root logger log level is INFO by default, thus a transformation run log does not contain more detail messages then INFO event if the job configuration parameter log_level is set properly. For details about Log4j 2 configuration, see Chapter 17, Logging.

The maximum number of concurrently running instances of this transformation. In Cluster environment, the limit is per node.

If true, the context URL of a running job will be a local file: URL. Otherwise, a sandbox: URL will be used.

Set to false to enforce execution in Server Core. Can be set per file or per sandbox.