The Apache Derby embedded DB is used with a default CloverETL Server installation. It uses the working directory as a storage directory for data persistence by default. This may be a problem on some systems. In case of any problems with connecting to Derby DB, we recommend you configure a connection to external DB or at least specify the Derby home directory:

Set the derby.system.home system property to set path which is accessible for application server. You can specify this system property with this JVM execution parameter:

-Dderby.system.home=[derby_DB_files_root]

If you use a properties file for configuration, specify these parameters: jdbc.driverClassName, jdbc.url, jdbc.username, jdbc.password, jdbc.dialect. For example:

jdbc.driverClassName=org.apache.derby.jdbc.EmbeddedDriver
jdbc.url=jdbc:derby:databases/cloverDb;create=true
jdbc.username=
jdbc.password=
jdbc.dialect=com.cloveretl.server.dbschema.DerbyDialect

Take a closer look at the jdbc.url parameter. The databases/cloverDb part means a subdirectory for DB data. This subdirectory will be created in the directory which is set as derby.system.home (or in the working directory if derby.system.home is not set). You may change the default value databases/cloverDb.

A Derby JDBC 4 compliant driver is bundled with CloverETL Server, thus there is no need to add it on the classpath.

	Note
	Continue with:  Encrypted JNDI or CloverETL Server Activation