Version

    Chapter 17. List of Configuration Properties

    General Configuration Properties
    Worker - Configuration Properties
    Worker Health Related Properties
    Worker - JNDI Properties
    SSL properties for Worker
    Properties on Worker's command line
    Job Execution Properties

    Below you can find the configuration properties available in CloverDX Server. The properties can be configured using the Setup GUI or by directly editing one of the several configuration sources.

    In CloverDX Server UI, you can view the properties and their values in Configuration > CloverDX Info > Server Properties.

    Additional properties used for Cluster configuration can be found in Chapter 50, Cluster Configuration.

    [Important]Important

    Configuration property and system property are not the same. Configuration properties can be configured in Setup section or in cloverdx.properties file. System properties serve to configure the JVM. E.g. in Apache Tomcat, they are configured in bin/setenv.[bat|sh] file using -D prefix.

    General Configuration Properties

    Configuration file
    License
    Engine
    Sandboxes
    Database connection
    Job Queue
    Security
    SMTP
    Logging
    Thread Manager
    Archivator
    Properties resolver
    Data Services
    Data Apps
    Alerts and Notifications
    API
    JVM
    Misc

    Table 17.1. General configuration

    KeyDescriptionDefault Value
    Configuration
    clover.config.file Absolute path to location of a CloverDX Server configuration file /absolute/path/to/cloverServer.properties
    configuration.autoimport.file Absolute path to an XML file containing exported CloverDX Server configuration (users, schedulers, event listeners, data services, etc.). If the property is set and the target file exists, it is automatically imported during the first startup with an empty database. Any error during the import causes CloverDX Server startup to fail. The property is not set by default. empty
    clover.home

    By default, this property is commented out and has a dynamically computed value: path containing CloverETL value for pre 5.0 installations and CloverDX for 5.0 and newer installations.

    If defined by the user, value has a higher priority.

    The property can be overridden using:

    environment variable clover.clover.home

    context parameter <Parameter name="clover.home">

    or system property -Dclover.clover.home=

    ${user.data.home}/CloverETL or ${user.data.home}/CloverDX
    License
    license.file Absolute path to location of a CloverDX Server license file (license.dat)  
    license.context_names A comma-separated list of web-app contexts which may contain license. Each of them has to start with a slash! Works only on Apache Tomcat. /clover-license,/clover_license
    Engine
    engine.config.filelocation of a CloverDX engine configuration properties fileproperties file packed with CloverDX
    engine.plugins.additional.src This property may contain an absolute path to some "source" of additional CloverDX engine plugins. These plugins are not a substitute for plugins packed in WAR. "Source" may be a directory or a zip file. Both, a directory and a zip, must contain a subdirectory for each plugin. Changes in the directory or the ZIP file apply only when the server is restarted. For details see Chapter 40, Extensibility - CloverDX Engine Plugins. empty
    Sandboxes
    sandboxes.home

    This property is primarily intended to be used as a placeholder in the sandbox root path specification. So the sandbox path is specified with the placeholder and it's resolved to the real path just before it's used. The sandbox path may still be specified as an absolute path, but placeholder has some significant advantages:

    * sandbox definition may be exported/imported to another environment with a different directory structure

    * user creating sandboxes doesn't have to care about physical location on the filesystem

    * each node in Cluster environment may have a different "sandboxes.home" value, so the directory structure doesn't have to be identical

    For backward compatibility, the default value uses the content of the clover.home configuration property.

    ${clover.home}/sandboxes
    sandboxes.access.check.boundaries.enabled

    true | false If it is set to false, then the path relative to a sandbox root may point out of the sandbox. No file/folder outside of the sandbox is accessible by the relative path otherwise.

    true
    sandboxes.autoimport

    If enabled, the Server scans the ${sandboxes.home} directory during the first start with an empty database and imports all subdirectories as shared sandboxes. It skips hidden directories (e.g. .git).

    false
    Database connection
    datasource.type Set this explicitly to JNDI if you need CloverDX Server to connect to a DB using JNDI datasource. In such case, "datasource.jndiName" and "jdbc.dialect" parameters must be set properly. Possible values: JNDI | JDBC JDBC
    datasource.jndiName JNDI location of a DB DataSource. It is applied only if "datasource.type" is set to "JNDI". java:comp/env/jdbc/clover_server
    jdbc.driverClassName class name for JDBC driver name 
    jdbc.urlJDBC URL used by CloverDX Server to store data 
    jdbc.usernameJDBC database user name 
    jdbc.passwordJDBC database password 
    jdbc.dialecthibernate dialect to use in ORM 
    quartz.driverDelegateClass SQL dialect for quartz. Value is automatically derived from "jdbc.dialect" property value.  
    Job Queue
    jobqueue.enabled

    Enables/disables the job queue. See Job Queue for more details about job queue.

    true
    jobqueue.dataservice.enabled

    Enables/disables processing of Data Services by the job queue. By default Data Services are not processed by the job queue, see Job Queue Impact for more details.

    false
    jobqueue.systemCpuLimit

    System CPU load that is considered high and job queue will start enqueuing jobs, see Job Queue Load Metrics for more details. The value 0.85 means 85% system CPU load. This property can be used to tweak the CPU load threshold from which jobs will be enqueued.

    0.85
    jobqueue.coreHeapUsageLimit

    Usage of JVM heap memory in Server Core that is considered high and job queue will enter emergency mode, see Job Queue Emergency Mode for more details. The value 0.9 means 90% use of heap memory. This property can be used to tweak the Server Core heap memory usage threshold from which job queue will enter emergency mode.

    0.9
    jobqueue.workerHeapUsageLimit

    Usage of JVM heap memory in Worker that is considered high and job queue will enter emergency mode, see Job Queue Emergency Mode for more details. The value 0.9 means 90% use of heap memory. This property can be used to tweak the Worker heap memory usage threshold from which job queue will enter emergency mode.

    0.9
    jobqueue.maxQueueSize

    Maximum number of jobs that can be enqueued at one time - i.e. the maximum size of the queue. Each enqueued job consumes a small amount of memory, this property protects the CloverDX Server from running out of memory.

    100000
    jobqueue.checkInterval

    Time interval (in milliseconds) between each evaluation of job queue. This property defines how often the job queue processes enqueued jobs to be started, checks performance metrics etc. See Job Queue Algorithm for more details.

    100
    jobqueue.initialLoadStep

    The job queue starts enqueued jobs in batches, and load step defines the size of the batch (i.e. number of jobs started at the same time). The load step is automatically adjusted by the job queue, and the jobqueue.initialLoadStep property defines the initial value of the load step. See Job Queue Algorithm for more details.

    20
    jobqueue.minLoadStep

    The job queue starts enqueued jobs in batches, and load step defines the size of the batch (i.e. number of jobs started at the same time). The load step is automatically adjusted by the job queue, and the jobqueue.minLoadStep property defines the minimum value of the load step. See Job Queue Algorithm for more details.

    5
    jobqueue.maxLoadStep

    The job queue starts enqueued jobs in batches, and load step defines the size of the batch (i.e. number of jobs started at the same time). The load step is automatically adjusted by the job queue, and the jobqueue.maxLoadStep property defines the maximum value of the load step. See Job Queue Algorithm for more details.

    300
    Security
    openssh.config.file

    Specifies the location of the OpenSSH configuration file which allows you to define SSH access outside of CloverDX Server. The path to the file is ~/path/to/.ssh/ssh_config There is no default file; therefore, without proper specification, no configuration file is loaded.

     
    private.properties List of server properties which are used only by the CloverDX Server code. So these properties are not accessible outside of the ServerFacade. By default, there are all properties which may contain password in the list, so their values are not visible for web GUI users. The values are replaced by a single star "*". Changes in this list may cause unexpected behavior of some server API. jdbc.password, security.ldap.password, clover.smtp.password
    security.session.validitySession validity in milliseconds. When the request of logged-in user/client is detected, validity is automatically prolonged.14400000
    security.session.exchange.limitInterval for exchange of invalid tokens in milliseconds.360000
    security.default_domainDomain in which all new users are included. Stored in user's record in the database. Shouldn't be changed unless the "clover" must be white-labelled.clover
    security.basic_authentication.features_list

    List of features which are accessible using HTTP and which should be protected by Basic HTTP Authentication. The list has form of semicolon separated items; Each feature is specified by its servlet path.

    /request_processor;/simpleHttpApi;/launch;/launchIt;/downloadStorage;​/downloadFile;/uploadSandboxFile;/downloadLog;/webdav
    security.basic_authentication.realm

    Realm string for HTTP Basic Authentication.

    CloverDX Server
    security.digest_authentication.features_list

    List of features which are accessible using HTTP and which should be protected by HTTP Digest Authentication. The list has form of semi-colon separated items. Each feature is specified by its servlet path.

    Please keep in mind that HTTP Digest Authentication is feature added to the version 3.1. If you upgraded your older CloverDX Server distribution, users created before the upgrade cannot use the HTTP Digest Authentication until they reset their passwords. So when they reset their passwords (or the admin does it for them), they can use Digest Authentication as well as new users.

     
    security.digest_authentication.storeA1.enabled Switch whether the A1 Digest for HTTP Digest Authentication should be generated and stored or not. Since there is no CloverDX Server API using the HTTP Digest Authentication by default, it's recommended to keep it disabled. This option is not automatically enabled when any feature is specified in the security.digest_authentication.features_list property. false
    security.digest_authentication.realm Realm string for HTTP Digest Authentication. If it is changed, all users have to reset their passwords, otherwise they won't be able to access the server features protected by HTTP digest Authentication. CloverDX Server
    security.digest_authentication.nonce_validity Interval of validity for HTTP Digest Authentication specified in seconds. When the interval passes, server requires new authentication from the client. Most of the HTTP clients do it automatically. 300
    security.lockout.login.attempts The number of failed login attempts after which a next failed login attempt will lock the user. Set the value to 0 to disable the function. Since 4.8.0M1. 50
    security.lockout.reset.period Period of time in seconds during which the failed login attempts are counted. Since 4.8.0M1. 60
    security.lockout.unlock.period Period of time in seconds after which a successful login attempt will unlock the previously locked user. Since 4.8.0M1. 300
    security.csrf.protection.enabled

    Enable/disable protection of Simple HTTP API and REST API against CSRF attacks, enabled by default. The CSRF protection requires presence of the X-Requested-By header in the requests.

    For more details, see the section called “CSRF Protection”.

    true
    SMTP
    clover.smtp.transport.protocolSMTP server protocol. Possible values are "smtp" or "smtps".smtp
    clover.smtp.hostSMTP server hostname or IP address 
    clover.smtp.portSMTP server port 
    clover.smtp.authenticationtrue/false If it is false, username and password are ignored. 
    clover.smtp.usernameSMTP server username 
    clover.smtp.passwordSMTP server password 
    clover.smtp.additional.* Properties with the clover.smtp.additional. prefix are automatically added (without the prefix) to the Properties instance passed to the Mailer. May be useful for some protocol specific parameters. The prefix is removed. 
    Logging
    logging.project_nameUsed in log messages where it is necessary to name the product name.CloverDX
    logging.default_subdir Name of a default subdirectory for all server logs; it is relative to the path specified by system property "java.io.tmpdir". Don't specify as an absolute path, use properties which are intended for absolute path. cloverlogs
    logging.logger.performance.enabled Enables logging of informations about server performance, e.g. memory and CPU usage. The name of the output file is "performance.log". It is stored in the same directory as other CloverDX Server log files by default. See Performance Log for more details. true
    logging.logger.server_audit.enabled Enables logging of operations called on ServerFacade and JDBC proxy interfaces. The name of the output file is "server-audit.log". It is stored in the same directory as other CloverDX Server log files by default. The default logging level is DEBUG so it logs all operations which may process any change. false
    logging.logger.server_integration.enabled Enables logging of Designer-Server calls. The name of the output file is "server-integration.log". It is stored in the same directory as other CloverDX Server log files by default. The default logging level is INFO. Username is logged, if available. JDBC and CTL debugging is not logged. true
    launch.log.dir Location, where server should store launch requests logs. See Chapter 48, Launch Services for details. ${java.io.tmpdir}/[logging. default_subdir]/launch where ${java.io.tmpdir} is system property
    graph.logs_path Location, where server should store Graph run logs. See Chapter 19, Logging for details. ${java.io.tmpdir}/[logging. default_subdir]/graph where ${java.io.tmpdir} is system property
    logging.appender.jobs.pattern_layout Pattern of the jobs' log messages %d %-5p %-3X{runId} [%t] %m%n
    logging.appender.jobs.encodingEncoding of the jobs' log filesUTF-8
    logging.mem_appender.WORKER.pattern_layout

    Format of log that can be seen in Monitoring > Logs > Worker.

     
    logging.mem_appender.WORKER.size_limit

    Size of log that can be seen in Monitoring > Logs > Worker.

     
    Thread Manager
    threadManager.pool.corePoolSize

    Number of threads which are always active (running or idling). Related to a thread pool for processing server events.

    4
    threadManager.pool.queueCapacity

    Max size of the queue (FIFO) which contains tasks waiting for an available thread. Related to a thread pool for processing server events. For queueCapacity=0, there are no waiting tasks, each task is immediately executed in an available thread or in a new thread.

    0
    threadManager.pool.maxPoolSize

    Max number of active threads. If no thread from a core pool is available, the pool creates new threads up to "maxPoolSize" threads. If there are more concurrent tasks then maxPoolSize, thread manager refuses to execute it.

    8192
    threadManager.pool.allowCoreThreadTimeOut

    Switch for idling threads timeout. If true, the "corePoolSize" is ignored so all idling threads may be time-outed

    false
    threadManager.pool.keepAliveSeconds

    timeout for idling threads in seconds

    20
    Archivator
    task.archivator.batch_size Max number of records deleted in one batch. It is used for deleting of archived run records. 50
    task.archivator.archive_file_prefix Prefix of archive files created by the archivator. cloverArchive_
    Properties resolver
    properties_resolver.placeholders.server_props_list_default A list of properties from a subset of properties, that may be used as placeholders and shall be resolved if used in paths. The properties can be used if you define a path to the root of a sandbox, or to locations of local or partitioned sandboxes, or path to a script, or path in archiver job. Users are strongly discouraged from modification of the property. The property name changed since CloverDX 4.2, however the obsolete name is also still accepted to maintain backwards compatibility. clover.home, sandboxes.home, sandboxes.home.local, sandboxes.home.partitioned, user.data.home
    Data Services
    dataservice.invocation.record.max.age It sets the maximal age in minutes before the record is removed from the database. The default is 1440 min = 24 h. 1440
    dataservice.https.connector.session.timeout Used for Data Services jobs accessed through an HTTPS connector. It configures HTTP session inactivity timeout before the session is invalidated. The value is in minutes and its default is the same as HTTP session timeout for CloverDX Server web application. 50
    dataservice.cors.allowed Enables or disables CORS filter. true
    dataservice.access.control.allow.origin A comma separated list of origins that are allowed to access Data Service endpoints.  
    dataservice.access.control.allow.methods A comma separated list of HTTP methods that are allowed to access Data Service endpoints.  
    dataservice.access.control.allow.headers A comma separated list of HTTP request headers that are allowed to access Data Service endpoints.  
    dataservice.access.control.expose.headers A comma separated list of HTTP response headers that are allowed to be exposed on the client.  
    dataservice.access.control.allow.credentials A boolean indicating if the resource allows requests with credentials. false
    dataservice.access.control.max.age The number of seconds that preflight requests can be cached for by the client.  
    Data App
    dataapp.request.timeout Timeout for HTTP requests related to the Data App life-cycle such as login, retrieval of the model, etc. The value is in seconds. 30
    dataapp.execution.timeout Timeout for the execution of the Data App (call of the Data Service). The value is in seconds. 1800
    dataapp.branding.resourceFilePath Path to the branding resource ZIP file. See Branding of Data Apps.  
    dataapp.branding.useCache If true, contents of the branding ZIP file are cached in the memory of the CloverDX Server. If false, contents of the branding ZIP file are loaded from the disk every time they are needed. true
    dataapp.branding.clientCacheMaxAge Time period (in seconds) after which the branding resources expire on the client (web browser). Sent to the client as the max-age directive of the Cache-Control HTTP header. 604800
    Alerts and Notifications
    trigger.failure.ratio.min.record.count Used for failure indication of triggers (Schedule, Data Service endpoint or Event Listener) It represents the minimum number of invocations required to evaluate whether the percentage of failures is over the threshold. Ensures that during periods of low traffic the trigger does not switch to failing state. 3
    API
    launch.http_header_prefixPrefix of HTTP headers added by launch services to the HTTP response.X-cloveretl
    http.api.enabled

    Enables or disables simple HTTP API.

    If the HTTP API is disabled, there is no link to HTTP API operations in login page, the HTTP API tab in Launch Service that is accessible under Test button is not visible, and the HTTP API, the /clover/httpapi.jsp and HTTP API servlet are not accessible.

    Available since 4.8.0M1. See Simple HTTP API.

    true
    webDav.method.propfind.maxDepth

    Maximum depth for webDAV method PROPFIND. When the depth is not specified, the default is supposed to be infinite (according to the rfc2518), however it's necessary to set some limit, otherwise the webDav client might overload the server filesystem.

    Also if the depth value specified by webDAV client in the request is higher than the pre-configured max depth, only the pre-configured maximum is used.

    40
    rest.api.absoluteUrls

    Whether REST API returns absolute URLs to resources. By default it returns absolute URLs (e.g. http://example.com:8080/clover/api/rest/v1/dashboards/1/monitors/191) that contain the full hostname. Absolute URLs are easier to use, but in some cases they might not be correct, e.g. in case of connecting through a load balancer. In such case it is possible to set this property to false and the REST API will return relative URLs, e.g. /clover/api/rest/v1/dashboards/1/monitors/191.

    true
    JVM
    server.env.min_heap_memory Sets the required minimal heap memory threshold. If the configuration of CloverDX Server is set to less heap memory, a warning is displayed. Experienced users can change the default value to avoid the warning when running the server on a system with lower memory. The threshold is in megabytes. 900
    server.env.min_nonheap_memory Sets the required minimal non-heap memory threshold. If the configuration of CloverDX Server is set to less non-heap memory, a warning is displayed. Experienced users can change the default value to avoid the warning when running the server on a system with lower memory. The threshold is in megabytes. 256
    Miscellaneous
    temp.default_subdirName of a default subdirectory for server tmp files; it is relative to the path specified by system property "java.io.tmpdir".clovertmp
    graph.pass_event_params_to_graph_in_old_style Since 3.0. It is a switch for backwards compatibility of passing parameters to the graph executed by a graph event. In versions prior to 3.0, all parameters are passed to executed graph. Since 3.0, just specified parameters are passed. Please see Start a Graph for details. false
    clover.event.fileCheckMinInterval Interval of the timer, running file event listener checks (in milliseconds). See File Event Listeners (remote and local) for details. 1000
    clover.event.groovyCheckMinInterval

    The periodicity of Groovy checks for Groovy event listeners (in milliseconds).

    1000
    clover.inDevelopment

    Displays/hides the debug window.

    false
    cluster.node.sendinfo.stats.interval

    The maximum time interval (in hours) for which the data in Performance Tab is recorded.

    Note: longer time intervals increase Server memory consumption and may increase latency when using Server GUI.

    24
    launchservices.visible Display Launch Services in the main menu in Server UI. Can be true or false. false
    task.jms.callback.timeout A JMS Message Listener property. Sets the time (in milliseconds) for which a JMS message listener waits for a triggered task to finish. After this time, the listener continues in processing the next message from the source queue/topic. 3600000 (1 hour)
    webGui.instance.color

    Sets the background color of the Instance Indicator.

    Possible values are: green, blue, yellow and red. If a wrong value is set, the color is inherited from the GUI's header.

    For the changes to take effect, you must log out and then back in the Server.

     
    webGui.instance.label

    Sets the label of the Instance Indicator. Note that too long label will be cropped in the GUI.

    For the changes to take effect, you must log out and then back in the Server.

     
    autoapply.sys.db.patches

    Value of the property is a version number. If the version of CloverDX Server you are upgrading to is equal or less than the version, database patching will be started automatically. Otherwise a user approval is required. Example autoapply_sys_db_patches=5.7 or autoapply.sys.db.patches=99.9..

     
    operations.dashboard.refreshing.interval

    How often the Operations Dashboard refreshes its content, in milliseconds.

    3000
    operations.dashboard.request.timeout

    Timeout for HTTP requests from the Operations Dashboard to the REST API, in milliseconds.

    30000

    Worker - Configuration Properties

    Table 17.2. Server - Worker configuration

    KeyDescriptionDefault Value
    worker.initialWorkers

    Enable/disable the Worker. To enable Worker, set to 1 (this is the default). To disable Worker and run all jobs in Core Server, set to 0.

    Starting more than one Worker is currently (in 4.9.0) not supported.

    1
    worker.portRange

    Port range used for communication between Server Core and Worker and between Workers on different Cluster nodes. Communication between Server Core and Worker is done on localhost. Workers on different Cluster nodes communicate directly with each other over these ports - in Cluster setup, this port range should be open in firewall for other Cluster nodes.

    This property can be easily configured in the Worker tab of Setup.

    worker.portRange should contain at least 5 ports for 1 node (depending on other options, a node takes at most 5 ports from the range). We recommend to use portRange of at least 10 ports to avoid possible problems with occupied ports after restart of Worker.

    If more Cluster nodes run on the same machine, make sure that there are enough free ports for Workers of all Cluster nodes on the machine. The default configuration of worker.portRange is sufficient for that.

    10500-10600
    worker.connectTimeout

    Timeout for connection initialization between Worker and Server Core, in both directions. The timeout is in milliseconds.

    This setting can be useful when handling communication issues between Server Core and Worker, typically under high load you might want to increase the timeout.

    60000
    worker.readTimeout

    Read timeout for communication requests between Worker and Server Core, in both directions. If a request is not completely served before reaching this limit, the connection is terminated. The timeout is in milliseconds.

    This setting can be useful when handling communication issues between Server Core and Worker, typically under high load you might want to increase the timeout.

    600000
    worker.classpath

    A directory with additional .jar files to be added to the Worker's classpath. The .jar files would typically be libraries used by graphs (e.g. JDBC drivers for database connections) or JDBC drivers used in JNDI connections defined in Worker (see Worker - JNDI Properties).

    The Worker's classpath is separate from Server Core (i.e. application container classpath). Any libraries needed by jobs executed on Worker need to be added on the Worker's classpath.

    For backward compatibility, the default value uses the content of the clover.home configuration property.

    The property can contain paths to multiple directories. The separator between the directories can be a colon (on Linux and Mac) or semicolon (Linux, Mac and Windows), e.g.:

    worker.classpath=/home/clover/worker-lib;/opt/worker-lib-2

    Some basic wildcards are supported: directory-* and directory-?.

    ${clover.home}/worker-lib
    worker.maxHeapSize

    The maximum Java heap size of Worker in MB, it will be translated to the -Xmx option for the Worker's JVM. Jobs executed in the Worker require heap memory based on their complexity, dataset size, etc.

    See our recommendations for heap sizes of Worker and Server Core.

    This property can be easily configured in the Worker tab of Setup.

    Setting to 0 uses Java default heap size (automatically determined by Java). This setting is not recommended for production usage.

    0
    worker.initHeapSize

    The initial Java heap size of Worker in MB, it will be translated to the -Xms option for the Worker's JVM. We recommend to set this to the same value as worker.maxHeapSize

    This property can be easily configured in the Worker tab of Setup.

    Setting to 0 uses Java default initial heap size (automatically determined by Java). This setting is not recommended for production usage.

    0
    worker.jvmOptions

    Adds Java command line options for the Worker's JVM. This property is useful to tweak the configuration of the Worker's JVM, e.g. to tune garbage collector settings. These command line options override default options of the JVM.

    For example to enable parallel garbage collector: -XX:+UseParallelGC.

    See Additional Diagnostic Tools section for useful options for troubleshooting and debugging Worker.

    This property can be easily configured in the Worker tab of Setup.

     
    worker.enableDebug Remote Java debugging of Worker, enables JDWP. Enabling this allows you to connect a Java debugger remotely to the running Worker process, to debug your Java transformations, investigate issues, etc. The port used by the debugger is determined dynamically and can be seen in the Worker section of the Monitoring or Setup page. false
    worker.inheritSystemProperties

    Sets whether system Java properties are inherited from the Server Core process to the Worker process. We automatically inherit some system properties to simplify the Worker configuration.

    For the list of system Java properties inherited from the Server Core to Worker, see properties passed from Server Core if worker.inheritSystemProperties is true.

    This functionality is enabled by default. Use this property to disable this behavior in case some of the inherited properties would cause issues.

    true
    worker.javaExecutable

    Absolute path to the Java binary for Worker process, e.g. /user/local/java/bin/java.

    Use this property if you need to use a specific Java binary for running the Worker.

    Note: Make sure that Worker uses the same major Java version as the Server Core (e.g. Java 11). Using different major Java versions is not supported.

    Value is automatically determined based on $JAVA_HOME environment variable.

    Worker Health Related Properties

    Below is a list of properties defining timeouts and limits related to the Worker's health.

    [Warning]For Expert Users Only

    These properties are for expert users only. Default values should be sufficient. Modification of the values could conceal the real cause of the problem; therefore, we strongly discourage users from changing the values.

    Table 17.3. General configuration

    KeyDescriptionDefault Value
    worker.health.heartbeatTimeoutTime before Worker is pronounced unresponsive because of a missing heartbeat (in milliseconds).120000
    worker.health.workerToCoreTimeoutTime before Worker is pronounced unresponsive because it is not sending any information to Server Core (in milliseconds).60000
    worker.health.coreToWorkerTimeoutTime before Worker is pronounced unresponsive because all requests are failing (i.e. throwing exceptions) (in milliseconds).60000
    worker.health.coreToWorkerErrorThresholdNumber of requests in a row which must fail to pronounce Worker unresponsive (amount of failures).30
    worker.heartbeat.connectTimeout Timeout for connection initialization from Worker to Server Core. Connection is used to send Worker heartbeat. The timeout is in milliseconds. 5000
    worker.heartbeat.readTimeout Read timeout for communication requests from Worker to Server Core. Connection is used to send Worker heartbeat. The timeout is in milliseconds. 5000

    Worker - JNDI Properties

    The Worker has its own JNDI pool separate from the application container JNDI pool. If your jobs use JNDI resources (to obtain JDBC or JMS connections), you have to configure the Worker's JNDI pool and its resources.

    The worker JNDI properties must be configured using the clover.properties configuration file. Libraries used by the JNDI resources must be added to the Worker's classpath, see worker.classpath.

    It is possible to define multiple datasources pointing to different databases or JMS queues, see examples below. The datasources are indexed in configuration, their properties have suffix [0], [1], etc. Even a single datasource must have the [0] index.

    JDBC Datasources

    Worker uses the Apache DBCP2 pool for its JNDI functionality. Any DBCP2 configuration attribute is supported, see DBCP attributes. The only mandatory properties are jndiName and url.

    See table below for basic JNDI properties.

    You can monitor the state of the datasources via JMX. See Additional Diagnostic Tools for details on how to enable JMX on Worker. Then you can connect to the Worker's JMX interface with tools like jconsole and monitor the JNDI datasources, e.g. for the number of currently open connections. The related MBeans are under the Tomcat/DataSource/localhost///javax.sql.DataSource path:

    MBean for a JNDI datasource in jconsole

    Figure 17.1. MBean for a JNDI datasource in jconsole


    Table 17.4. Properties for JDBC JNDI Resources in Worker

    KeyDescriptionExample
    worker.jndi.datasource[0].jndiName The name of the JNDI datasource. Mandatory. jdbc/database_name
    worker.jndi.datasource[0].url The JDBC connection URL. Mandatory. jdbc:postgresql://hostname:5432/database_name
    worker.jndi.datasource[0].username The user name for a database connection. clover
    worker.jndi.datasource[0].password The password for a database connection. The password value can be encrypted using the secure configuration tool, see Secure Configuration Properties. clover
    worker.jndi.datasource[0].driverClassName The database driver classname. The database driver must be on the Worker classpath, see worker.classpath. org.postgresql.Driver
    worker.jndi.datasource[0].maxIdle The maximum number of idle database connections in a pool. Set to -1 for no limit. 10
    worker.jndi.datasource[0].maxTotal The maximum number of database connections in a pool. Set to -1 for no limit. 20
    worker.jndi.datasource[0].maxWaitMillis The maximum time Worker waits for a database connection to become available. In milliseconds, set to -1 for no limit. 30000
    worker.jndi.datasource[0].defaultReadOnly If a connection is used both for reading and writing from and to the database set the property defaultReadOnly to false. Otherwise the connection reused from a pool could refuse to execute SQL statement writing data.  
    worker.jndi.datasource[0].dbcpAttribute Any DBCP2 attribute, e.g. worker.jndi.datasource[0].initSQL. See DBCP attributes.  

    The following example shows configuration of two JDBC Datasources.

    worker.jndi.datasource[0].jndiName=jdbc/postgresql_finance
    worker.jndi.datasource[0].url=jdbc:postgresql://finance.example.com:5432/finance
    worker.jndi.datasource[0].maxIdle=5
    worker.jndi.datasource[0].maxTotal=10
    worker.jndi.datasource[0].maxWaitMillis=-1
    worker.jndi.datasource[0].username=finance_user
    worker.jndi.datasource[0].password=conf#eCflGDlDtKSJjh9VyDlRh7IftAbI/vsH
    worker.jndi.datasource[1].defaultReadOnly=false
    worker.jndi.datasource[0].driverClassName=org.postgresql.Driver
    
    worker.jndi.datasource[1].jndiName=jdbc/MysqlDB
    worker.jndi.datasource[1].url=jdbc:mysql://marketing.example.com:3306/marketing?useUnicode=true&amp;characterEncoding=utf8
    worker.jndi.datasource[1].maxIdle=10
    worker.jndi.datasource[1].maxTotal=20
    worker.jndi.datasource[1].maxWaitMillis=-1
    worker.jndi.datasource[1].username=marketing_user
    worker.jndi.datasource[1].password=conf#JWsMa2okg7Dq2gtLBM84sE==
    worker.jndi.datasource[1].defaultReadOnly=false
    worker.jndi.datasource[1].driverClassName=com.mysql.jdbc.Driver

    JMS Connections

    Worker can use any JMS broker to define JMS connections in JNDI. Any JMS broker configuration attribute is supported. The mandatory properties are jndiName, factory and type. See table below for basic JNDI properties for JMS resources.

    Table 17.5. Properties for JMS JNDI Resources in Worker

    KeyDescriptionExample
    worker.jndi.jms[0].jndiName The name of the JNDI JMS resource. Mandatory. jms/jms_queue
    worker.jndi.jms[0].factory Factory class for creating the JMS resource. This is JMS broker specific. Mandatory. org.apache.activemq.jndi.JNDIReferenceFactory
    worker.jndi.jms[0].type Implementation class of the JMS resource. This is JMS broker specific. Mandatory. org.apache.activemq.command.ActiveMQQueue
    worker.jndi.jms[0].jmsProperty Configuration property for the JMS resource. Any configuration property supported by the JMS broker can be used. worker.jndi.jms[0].brokerUrl.

    The following example shows configuration of several JMS resources.

    worker.jndi.jms[0].jndiName=jms/CloverConnectionFactory
    worker.jndi.jms[0].type=org.apache.activemq.ActiveMQConnectionFactory
    worker.jndi.jms[0].factory=org.apache.activemq.jndi.JNDIReferenceFactory
    worker.jndi.jms[0].brokerUrl=tcp://localhost:61616?jms.prefetchPolicy.queuePrefetch=1
    worker.jndi.jms[0].brokerName=LocalActiveMQBroker
    
    worker.jndi.jms[1].jndiName=jms/CloverQueue
    worker.jndi.jms[1].type=org.apache.activemq.command.ActiveMQQueue
    worker.jndi.jms[1].factory=org.apache.activemq.jndi.JNDIReferenceFactory
    worker.jndi.jms[1].physicalName=TestQueue
    

    Worker - SSL Properties

    In Cluster, Workers of each node communicate with each other directly for increased performance. This communication is used to transport data of Cluster remote edges in Clustered jobs between the nodes. For increased security, it is possible to use SSL for the remote edge communication.

    SSL communication between Workers needs to be enabled and configured separately from SSL of the application container that runs Server Core. The worker.ssl.enabled property is used to enable/disable SSL. If a Cluster node's "self" URL is using HTTPS, we automatically set the property to true. Configuration of SSL consists of setting paths and passwords of KeyStore and TrustStore, see the table below for details.

    Note that if the standard SSL related system properties (javax.net.ssl.keyStore, javax.net.ssl.keyStorePassword, javax.net.ssl.keyAlias, javax.net.ssl.trustStore and javax.net.ssl.trustStorePassword) are used to configure KeyStore/TrustStore for the Server Core, they are propagated to Worker; therefore, their respective worker.ssl properties do not need to be configured. The properties containing passwords to the keystore and truststore files are encrypted before adding to Worker's command line. To avoid having the encrypted password properties on Worker's command line completely, you may also specify path to a file which will be created on Worker's start and these encrypted passwords will be stored in it (via the worker.ssl.passwordFile property).

    Recommended steps to enable SSL for inter-worker communication are:

    • Enable SSL for each Cluster node, via the application container settings. Configure TrustStore and KeyStore via the standard javax.net.ssl.* properties.

    • Set cluster.http.url for each node to point to its own HTTPS URL

    • Check that communication between Cluster nodes over SSL works and that the nodes can correctly see each other. The Monitoring page of Server Console should show the whole Cluster group and its nodes correctly.

    • Worker should automatically inherit the above SSL configuration.

    • Run a Clustered job on Worker

    Table 17.6. Properties for SSL communication in Worker

    KeyDescriptionExample
    worker.ssl.enabled

    Enables or disables an SSL connection for Worker. Note that if the Server runs on HTTPS, SSL is enabled automatically; however, this property has a higher priority.

    true/false
    worker.ssl.keyStoreAbsolute path to the KeyStore file.path/to/keyStore.file
    worker.ssl.keyStorePassword The KeyStore password. 
    worker.ssl.keyAlias

    The alias of the key in keyStore. Optional - the property does not have to be specified if there is only one key in the KeyStore.

     
    worker.ssl.passwordFile The absolute path to a file containing encrypted keystore and truststore passwords for Worker. Optional: by default this is not set, and the keystore and trusstore passwords are passed to Worker as command line arguments with encrypted values. Use this property to avoid having the encrypted passwords on Worker command line, but instead passed via the file.  
    worker.ssl.port The port for SSL communication with Worker. The property is configured automatically and the value is set from worker.portRange.  
    cluster.ssl.disableCertificateValidation Disables validation of certificates in HTTPS connections of remote edges. Disabling the validation affects jobs run on both Worker and Server Core. true/false

    Properties on Worker's Command Line

    To ensure proper functionality of CloverDX Worker, there is a number of parameters which can appear on its command line. These can be hard-coded, passed from the configuration file, propagated from Server Core or added manually for a specific purpose, see the list below.

    Note that the list does not include internal system parameters not configurable by the user.

    Table 17.7. List of Properties on Worker's Command Line

    PropertyNote
    Passed from Server Core if worker.inheritSystemProperties is true
    -Djavax.net.ssl.​trustStorePassword

    Standard SSL related properties.

    Values of the properties containing passwords are encrypted.

    javax.net.ssl.keyStore is passed only if javax.net.ssl.keyStorePassword is not empty.

    See also SSL properties for Worker.

    -Djavax.net.ssl.​keyStorePassword
    -Djavax.net.ssl.keyStore
    -Djavax.net.ssl.trustStore
    -Djavax.net.ssl.keyAlias
    -Djava.library.pathStandard Java properties
    -Djava.io.tmpdir
    -Dhttps.protocols
    -XX:MaxMetaspaceSize
    -Djava.rmi.server.hostname
    -Dfile.encodingThe charset for file contents.
    -DsocksProxyHost

    Properties for proxy configuration.

    The properties with * are passed for http, https and ftp.

    -DsocksProxyPort
    -DsocksProxyVersion
    -Djava.net.socks.username
    -Djava.net.socks.password
    -Djava.net.useSystemProxies
    -D*.proxyHost
    -D*.proxyPort
    -D*.proxyUser
    -D*.proxyPassword
    -D*.nonProxyHosts
    -Duser.timezone 
    -Duser.language 
    -Duser.region 
    -Duser.country 
    -Duser.variant 
    Hard-coded Properties
    -Djdk.nio.maxCachedBufferSizeLimits the memory used by the temporary buffer cache. Prevents memory leaks.
    -XssLimits the maximum stack size of application threads. Reduces memory requirements.
    Added for Java 8
    -XX:+UseG1GC Setting G1 garbage collector as default for Java 8. See garbage collector for Worker.
    Added for Java 9 and Newer
    --add-opens=java.base/java.langParameters for suppressing illegal reflective access warning.
    --add-opens=java.base/java.util
    --add-exports=java.xml/com.sun.org.apache.xerces.internal.parsers
    --add-opens=java.rmi/sun.rmi.transport
    --add-exports=java.base/sun.security.provider 
    --add-exports=java.security.jgss/sun.security.krb5 
    Added from config.properties/clover.properties
    -Xms*mFrom the worker.initHeapSize property; * is the property value.
    -Xmx*mFrom the worker.maxHeapSize property; * is the property value.
    -agentlib:jdwp=transport=dt_socket,server=y,address=*,suspend=n

    From the worker.enableDebug property; * is a dynamically determined port used by the debugger. The port can be seen in the Worker section of the Monitoring or Setup page.

    -Dworker.ssl.passwordFile

    The absolute path to a file containing encrypted keystore and truststore passwords for Worker. See also SSL properties for Worker.

    -Dsecurity.config_properties.encryptor.providerClassName Encryption provider and algorithm for secure parameters. See Secure parameters configuration.
    -Dsecurity.config_properties.encryptor.algorithm
    Added if SSL is enabled (see worker.ssl.enabled)
    -Dworker.ssl.portThe port for SSL communication with Worker is taken from the port range set by the worker.portRange property.
    Added from config.properties/clover.properties if SSL is enabled (see worker.ssl.enabled)
    -Dworker.ssl.keyStore

    Worker-specific SSL configuration properties.

    Values of the properties containing passwords are encrypted.

    If the standard SSL properties are used (see above), the Worker-specific properties don't have to be configured. See also SSL properties for Worker.

    -Dworker.ssl.​keyStorePassword
    -Dworker.ssl.keyAlias
    -Dworker.ssl.trustStore
    -Dworker.ssl.trustStorePassword

    Job Execution Properties

    Table 17.8. Defaults for job execution configuration - see Execution Properties for details

    KeyDescriptionDefault Value
    executor.tracking_interval An interval in milliseconds for scanning of a current status of a running graph. The shorter interval, the bigger log file. 2000
    executor.log_levelLog level of graph runs. TRACE | DEBUG | INFO | WARN | ERRORINFO
    executor.max_job_tree_depth Defines maximal depth of the job execution tree, e.g. for recursive job it defines the maximal level of recursion (counting from root job). 32
    executor.max_running_concurrently Amount of graph instances which may exist (or run) concurrently. 0 means no limits. 0
    executor.classpath Classpath for transformation/processor classes used in the graph. Directory [Sandbox_root]/trans/ does not have to be listed here, since it is automatically added to a graph run classpath.  
    executor.skip_check_config Disables check of graph configuration. Increases performance of a graph execution; however, it may be useful during graph development. true
    executor.verbose_mode If true, more descriptive logs of graph runs are generated. true
    executor.use_jmx If true, the graph executor registers JMX mBean of the running graph. true
    executor.debug_mode If true, edges with enabled debug store data into files in debug directory. false

    List of all properties

    clover.event.fileCheckMinInterval
    clover.event.fileCheckMinInterval
    clover.inDevelopment
    clover.smtp.additional.*
    clover.smtp.authentication
    clover.smtp.host
    clover.smtp.password
    clover.smtp.port
    clover.smtp.transport.protocol
    clover.smtp.username
    config.file
    clover.home
    dataservice.invocation.record.max.age
    dataservice.https.connector.session.timeout
    dataservice.cors.allowed
    dataservice.access.control.allow.origin
    dataservice.access.control.allow.methods
    dataservice.access.control.allow.headers
    dataservice.access.control.expose.headers
    dataservice.access.control.allow.credentials
    dataservice.access.control.max.age
    dataapp.request.timeout
    dataapp.execution.timeout
    dataapp.branding.resourceFilePath
    dataapp.branding.useCache
    dataapp.branding.clientCacheMaxAge
    datasource.type
    datasource.jndiName
    engine.config.file
    engine.plugins.additional.src
    executor.classpath
    executor.debug_mode
    executor.log_level
    executor.max_job_tree_depth
    executor.max_running_concurrently
    executor.skip_check_config
    executor.tracking.interval
    executor.use_jmx
    executor.verbose_mode
    graph.logs_path
    graph.pass_event_params_to_graph_in_old_style
    http.api.enabled
    jdbc.dialect
    jdbc.driverClassName
    jdbc.password
    jdbc.url
    jdbc.username
    jobqueue.enabled
    jobqueue.dataservice.enabled
    jobqueue.systemCpuLimit
    jobqueue.coreHeapUsageLimit
    jobqueue.workerHeapUsageLimit
    jobqueue.maxQueueSize
    jobqueue.checkInterval
    jobqueue.initialLoadStep
    jobqueue.minLoadStep
    jobqueue.maxLoadStep
    launch.http_header_prefix
    launch.log.dir
    launchservices.visible
    license.context_names
    license.file
    logging.appender.jobs.encoding
    logging-appender-jobs-pattern_layout
    logging.default_subdir
    logging.logger.server_audit.enabled
    logging.logger.server_integration.enabled
    logging.mem_appender.WORKER.pattern_layout
    logging.mem_appender.WORKER.size_limit
    logging.project_name
    operations.dashboard.refreshing.interval
    operations.dashboard.request.timeout
    private.properties
    properties_resolver.placeholders.server_props_list_default
    quartz.driverDelegateClass
    rest.api.absoluteUrls
    sandboxes.access.check.boundaries.enabled
    sandboxes.home
    sandboxes.autoimport
    security.basic_authentication.features_list
    security.basic_authentication.realm
    security.default_domain
    security.digest_authentication.features_list
    security.digest_authentication.nonce_validity
    security.digest_authentication.realm
    security.digest_authentication.storeA1.enabled
    security.lockout.login.attempts
    security.lockout.reset.period
    security.lockout.unlock.period
    security.csrf.protection.enabled
    security.session.exchange.limit
    security.session.validity
    server.env.min_heap_memory
    server.env.min_nonheap_memory
    task.archivator.archive_file_prefix
    task.archivator.batch_size
    task.jms.callback.timeout
    temp.default_subdir
    threadManager.pool.allowCoreThreadTimeOut
    threadManager.pool.corePoolSize
    threadManager.pool.keepAliveSeconds
    threadManager.pool.maxPoolSize
    threadManager.pool.queueCapacity
    trigger.failure.ratio.min.record.count
    webDav.method.propfind.maxDepth
    worker.classpath
    worker.enableDebug
    worker.inheritSystemProperties
    worker.initHeapSize
    worker.javaExecutable
    worker.jvmOptions
    worker.maxHeapSize
    worker.portRange
    worker.connectTimeout
    worker.readTimeout
    worker.initialWorkers
    worker.health.heartbeatTimeout
    worker.health.workerToCoreTimeout
    worker.health.coreToWorkerTimeout
    worker.health.coreToWorkerErrorThreshold
    worker.heartbeat.connectTimeout
    worker.heartbeat.readTimeout
    worker.jndi.datasource[0].url
    worker.jndi.datasource[0].maxIdle
    worker.jndi.datasource[0].maxTotal
    worker.jndi.datasource[0].maxWaitMillis
    worker.jndi.datasource[0].defaultReadOnly
    worker.jndi.datasource[0].username
    worker.jndi.datasource[0].password
    worker.jndi.datasource[0].driverClassName
    worker.jndi.datasource[0].jndiName
    worker.jndi.jms[0].jndiName
    worker.jndi.jms[0].factory
    worker.jndi.jms[0].type
    worker.jndi.jms[0].jmsProperty
    worker.ssl.enabled
    worker.ssl.keyStore
    worker.ssl.keyStorePassword
    worker.ssl.keyAlias
    cluster.ssl.disableCertificateValidation