Chapter 16. System Database Configuration
- Embedded Apache Derby
- Microsoft SQL Server
- JNDI Configuration and Encryption
The CloverDX Server license, as well as user's information, event listeners and other services, are saved in a database. For stability and performance reasons, the default Apache Derby database is not supported for production environment, it is supported for evaluation purposes with Tomcat 9 application container only; therefore, you should choose one of the supported DB systems.
Since CloverDX Server stores important data in a database, you should create a system database and set up a working connection before you activate the Server with license and configure it.
For details on how to set up a connection to an external system database, see the list of examples below. The examples contain details on creating databases in DB systems supported by CloverDX Server and configuring a working connection between the database and the Server.
It is possible to specify common JDBC DB connection properties (see below) or a JNDI location of DB Datasource.
In a Clustered deployment, at least one node in the Cluster must have a DB connection configured. Other nodes may have their own direct connection (to the same DB), or may use another node as a proxy for persistent operations; however, the scheduler is active only on nodes with a direct connection. For more information about the feature, see Part VII, “Cluster”.
Setting up a CloverDX Server's System Database
Create a database
Choose one of the supported database systems and create a database dedicated to CloverDX Server. Add a user/role for Clover and grant it required rights/privileges.
Configure common JDBC connection properties
Some JDBC connection properties are common for all supported database systems. If you use a properties file for configuration, specify these properties:
jdbc.driverClassName Class name for JDBC driver name. jdbc.url JDBC URL used by CloverDX Server to store data. jdbc.username JDBC database username. jdbc.password JDBC database password. jdbc.dialect Hibernate dialect to use in Object-relational mapping (ORM).
Add a JDBC 4 compliant driver on the classpath.
As the last step, add a JDBC 4 compliant driver on the classpath. A JDBC Driver which doesn't meet JDBC 4 won't work properly.
Below is a list of examples of individual database systems configurations.