Configuring CloverDX Server
CloverDX Server needs to know the location of profiling results database and the location (URL) of the Reporting Console.
By default, CloverDX Server is configured to connect to the default profiling results database
that is automatically launched by Reporting Console.
If you wish to store the profiling results into a different database,
you need to configure both the Reporting Console (
and CloverDX Server (
clover.properties) at the same time.
Settings of both use the same format.
Just as for Reporting Console, use this set of properties in CloverDX Server configuration, for example:
datasource.profiler.jdbcSpecific=MYSQL datasource.profiler.primary.type=JDBC datasource.profiler.primary.jdbc.driverClassName=com.mysql.jdbc.Driver datasource.profiler.primary.jdbc.url=jdbc:mysql://localhost:3306/profiler datasource.profiler.primary.jdbc.username=clover datasource.profiler.primary.jdbc.password=
To configure different than default location of Reporting Console,
the default value is
Table 6.1. Data Profiler connection pool settings
|datasource.profiler.pool.initialSize||The initial number of connections that are created when the pool is started.||1|
|datasource.profiler.pool.maxActive||The maximum number of active connections that can be allocated from this pool at the same time.||50|
|datasource.profiler.pool.maxWait||The maximum number of milliseconds that the pool will wait (when there are no available connections) for a connection to be returned before throwing an exception.||30000|
|datasource.profiler.pool.minIdle||The minimum number of established connections that should be kept in the pool at all times. Idle connections are checked periodically and connections that been idle for longer than minEvictableIdleTimeMillis will be released.||0|
|datasource.profiler.pool.maxIdle||The maximum number of connections that should be kept in the pool at all times.||2|
|datasource.profiler.pool.minEvictableIdleTimeMillis||The minimum amount of time an object may sit idle in the pool before it is eligible for eviction.||20000|
|datasource.profiler.pool.jmxEnabled||Register the pool with JMX or not.||true|
|datasource.profiler.pool.timeBetweenEvictionRunsMillis||The number of milliseconds to sleep between runs of the idle connection validation/cleaner thread. This value should not be set under 1 second. It dictates how often we check for idle, abandoned connections, and how often we validate idle connections.||10000|
|datasource.profiler.pool.removeAbandoned||Flag to remove abandoned connections if they exceed the removeAbandonedTimeout. If set to true a connection is considered abandoned and eligible for removal if it has been in use longer than the removeAbandonedTimeout. Not recommended for Data Profiler as it uses connections with long life span.||false|
|datasource.profiler.pool.removeAbandonedTimeout||Timeout in seconds before an abandoned(in use) connection can be removed. Not used when removeAbandoned is set to false.||240|