List of Properties

Table 16.1. General configuration

keydescriptiondefault
config.filelocation of CloverETL Server configuration file[working_dir]/ cloverServer.properties
license.filelocation of CloverETL Server licence file (license.dat) 
engine.config.filelocation of CloverETL engine configuration properties fileproperties file packed with CloverETL
private.propertiesList of server properties which are used only by CloverETL 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. Basically it means, that their values are not visible for web GUI users. Values are replaced by single star "*". Changes in this list may cause unexpected behavior of some server API.jdbc.password,executor.password,security.ldap.password,clover.smtp.password
engine.plugins.srcThis property may contain absolute path to some "source" of additional CloverETL engine plugins. These plugins are not a substitute for plugins packed in WAR. "Source" may be directory or zip file. Both directory and zip must contain subdirectory for each plugin. Changes in the directory or the ZIP file apply only when the server is restarted. For details see section "Extensibility - engine plugins". empty
datasource.typeSet this explicitly to JNDI if you need CloverETL Server to connect to DB using JNDI datasource. In such case, parameters "datasource.jndiName" and "jdbc.dialect" must be set properly. Possible values: JNDI | JDBCJDBC
datasource.jndiNameJNDI location of DB DataSource. It is applied only if "datasource.type" is set to "JNDI".java:comp/env/jdbc/clover_server
jdbc.driverClassNameclass name for jdbc driver name 
jdbc.urljdbc url used by CloverETL Server to store data 
jdbc.usernamejdbc database user name 
jdbc.passwordjdbc database user name 
jdbc.dialecthibernate dialect to use in ORM 
quartz.driverDelegateClassSQL dialect for quartz. Value is automatically derived from "jdbc.dialect" property value. 
security_enabledtrue | false If it is set to false, then no authentication is required and anyone has admin privileges.true
security.default_domainDomain which all new users are included in. Stored in user's record in the database. Shouldn't be changed unless the "clover" must be white-labelled.clover
security.basic_authentication.features_listSemi-colon separated list of features which are accessible using HTTP and which should be protected by Basic HTTP Authentication. Each feature is specified by its servlet path./request_processor;/simpleHttpApi;/launch;/launchIt;/downloadStorage;/downloadFile;/uploadSandboxFile;/downloadLog
security.basic_authentication.realmRealm string for HTTP Basic Authentication.CloverETL Server
security.digest_authentication.features_listSemi-colon separated list of features which are accessible using HTTP and which should be protected by HTTP Digest Authentication. 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 CloverETL 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. /webdav
security.digest_authentication.realmRealm string for HTTP Digest Authentication. If it is changed, all users have to reset their passwords, otherwise they won't be able to access to the server features protected by HTTP digest Authentication.CloverETL Server
security.digest_authentication.nonce_validityInterval 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
clover.event.fileCheckMinIntervalInterval of file checkes (in milliseconds) See Chapter 10, File event listeners for details.1000
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 
logging.project_nameused in log messages where it is neccessary to name the product nameCloverETL
logging.default_subdirname of default subdirectory for all server logs; it is relative to the path specified by system property "java.io.tmpdir". Don't specify absolute path, use properties which are intended for absolute path.cloverlogs
launch.log.dirLocation, where server should store launch requests logs. See Launch Services section for details.${java.io.tmpdir}/[logging.default_subdir]/launch where ${java.io.tmpdir} is system property
graph.logs_pathLocation, where server should store Graph run logs. See Logging section for details.${java.io.tmpdir}/[logging.default_subdir]/graph where ${java.io.tmpdir} is system property
temp.default_subdirName of default subdirectory for server tmp files; it is relative to the path specified by system property "java.io.tmpdir".clovertmp
graph.debug_pathLocation, where server should store Graph debug info.${java.io.tmpdir}/[temp.default_subdir]/debug where ${java.io.tmpdir} is system property
graph.dictionary_pathLocation, where server should store graph dictionary temporary files.${java.io.tmpdir}/[temp.default_subdir]/dictionary where ${java.io.tmpdir} is system property
graph.pass_event_params_to_graph_in_old_styleSince 3.0. It is switch for backwards compatibility of passing parameters to the graph executed by graph event. In version prior to 3.0 all params has been passed to executed graph. Since 3.0 just specified parameters are passed. Please see Task - Execution of Graph for details.false
threadManager.pool.corePoolSizeNumber of threads which are always active (running or idling). Related to thread pool for processing server events.4
threadManager.pool.queueCapacityMax size of the queue(FIFO) which contains tasks waiting for thread. Related to thread pool for processing server events. It means, that there won't be more then "queueCapacity" waiting tasks. i.e. queueCapacity=0 - no waiting tasks, each task is immediatelly executed in available thread or in new thread. queueCapacity=1024 - up to 1024 tasks may be waiting in the queue for available thread from "corePoolSize".12
threadManager.pool.maxPoolSizeMax number of active threads. If no thread from core pool is available and queue capacity is exceeded, pool creates new threads up to "maxPoolSize" threads. If there are more concurrent tasks then maxPoolSize, thread manager refuses to execute it. Thus keep queueCapacity or maxPoolSize big enough.1024
task.archivator.batch_sizeMax number of records deleted in one batch. It is used for deleting of archived run records.50
launch.http_header_prefixPrefix of HTTP headers added by launch services to the HTTP response.X-cloveretl
task.archivator.archive_file_prefixPrefix of archive files created by archivator.cloverArchive_
license.context_namesComma separated list of web-app contexts which may contain license. Each of them has to start with slash! Works only on Apache Tomcat./clover-license,/clover_license
license.display_headerSwitch which specifies whether display license header in server web GUI or not.false

Table 16.2. Defaults for graph execution configuration - see section Graph config properties for details

keydescriptiondefault
executor.tracking_intervalInterval in milliseconds for scanning current status of running graph. The shorter interval, the bigger log file.2000
executor.log_levelLog level of graph runs. TRACE | DEBUG | INFO | WARN | ERRORINFO
executor.max_running_concurrentlyAmount of graph instances which may exist(or run) concurrently. 0 means no limits0
executor.max_graph_instance_ageInterval in milliseconds. Specifies how long graph instance can be idling before it is released from memory. 0 means no limits. This property has been renamed since 2.8. Original name was executor.maxGraphInstanceAge0
executor.classpathClasspath 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 graph run classpath. 
executor.skip_check_configDisables check of graph configuration. Increases performance of graph execution, however may be useful during graph development.true
executor.passwordPassword for decoding of encoded DB connection passwords. 
executor.verbose_modeIf true, more descriptive logs of graph runs are generated.true
executor.use_jmxIf true, graph executor registers jmx mBean of running graph.true
executor.debug_modeIf true, edges with enabled debug store data into files in debug directory. See property "graph.debug_path"false

See "Clustering" section for more properties.