There are several sources of configuration properties. If property isn't set, application default is used.

Warning: Do not combine sources specified below. Configuration becomes confusing and maintenance will be much more difficult.

Context Parameters (Available on Apache Tomcat)

Some application servers allows to set context parameters without modification of WAR file. This way of configuration is possible and recommended for Tomcat.

Example for Apache Tomcat

On Tomcat it is possible to specify context parameters in context configuration file. [tomcat_home]/conf/Catalina/localhost/clover.xml which is created automatically just after deployment of CloverETL Server web application.

You can specify property by adding this element:

<Parameter name="[propertyName]" value="[propertyValue]" override="false" />

Environment Properties

Set system environment property with prefix clover. , i.e. (clover.config.file)

Properties File on default Location

Source is common properties file (text file with key-value pairs):

[property-key]=[property-value]

By default CloverETL tries to find config file [workingDir]/cloverServer.properties.

Properties File on specified Location

The same as above, but properties file is not loaded from default location, because its location is specified by environment property clover_config_file or clover.config.file. This is recommended way of configuration if context parameters cannot be set in application server.

Modification of Context Parameters in web.xml

Unzip clover.war and modify file WEB-INF/web.xml, add this code:

<context-param>
  <param-name>[property-name]</param-name>
  <param-value>[property-value]</param-value>
</context-param>

This way isn't recommended, but it may take place when none of above ways is possible.

Priorities of config Sources

Configuration sources have these priorities: