Base Configuration

By default, the Reporting Console does not require any configuration. It will assume that the CloverETL Server instance is reachable at http://localhost:8080/clover and internal Apache Derby database will be used to store profiling results. This section describes how to change these defaults.

To customize the settings of Reporting Console, create a new file called e.g. with following contents:

# Uncomment this line to change the address of CloverETL Server instance

# Uncomment this line to set node names and addresses of other CloverETL Cluster nodes (value format: "nodename1:url1;nodename2:url2;nodename3...")

# Uncomment these lines to change the location of profiling results database

# Uncomment these lines to configure the profiling results database connection
# as a JNDI DataSource. This DataSource has to be configured in application
# server or container.

Uncomment and change lines with settings you want to change.

Subsequently, place this config file anywhere on your disk. Finally, tell the Reporting Console application where to find this configuration file, by using command-line JVM system property when launching the web server:


Note that the Reporting Console will also always attempt to look for this file in the current working directory (see below).

Alternative ways of configuration

You can also configure the Reporting Console via system properties, similarly to how CloverETL Server can be configured. Prefix them with clover.profiler. prefix. E.g.:


The Reporting Console will also look for clover.profiler. properties within environment variables of your system.

The Reporting Console will attempt to read a configuration file named from the current working directory of the web application process.

Finally, context parameters (available for example in Apache Tomcat) are also read. Do not prefix those with the prefix mentioned above.