Chapter 6. System Requirements
The following table shows hardware requirements for CloverDX Server and CloverDX Cluster.
Table 6.1. Hardware requirements
|RAM||8 GB (recommended 64 GB)||8 GB (recommended 64 GB)|
|Processors||16 cores||8 cores [a]|
|Disk space (installation)||1 GB||1 GB|
|Disk space (tempspace)||> 25 GB [b]||> 25 GB [b]|
|Disk space (data)||> 50 GB [b]||> 50 GB [b]|
|Disk space (shared) [c]||-||> 50 GB [b]|
[a] This may vary depending on total number of nodes and cores in license.
[b] Minimum value, the disk space depends on data.
[c] Disk space for shared sandboxes is required only for CloverDX Cluster.
CloverDX Server is compatible with Windows and Unix-based systems, as well as with other systems supporting Java (Mac OS X, IBM System, etc.).
CloverDX Server supports:
Mozilla Firefox (latest)
Google Chrome (latest)
Since version 5.5, we no longer support Internet Explorer 11.
Java Virtual Machine
Oracle JDK 8, or AdoptOpenJDK 11, 64 bit, HotSpot JVM
IBM SDK 8 (for IBM WebSphere only)
CloverDX Server requires Java Development Kit (JDK) to run. We do not recommend using Java Runtime Environment (JRE) only, since compilation of some CloverDX Server's transformations requires JDK to function properly.
Since the version 5.2, we no longer support Oracle JDK 9. Also note that we do not support Oracle JDK 10 and OpenJDK 8, or AdoptOpenJDK 8.
Application Servers Compatibility
Table 6.2. Compatibility Matrix
|CloverDX 5.0 and 5.1||CloverDX 5.2 and newer|
|Application Server||Oracle JDK 8||Oracle JDK 9||Oracle JDK 8||AdoptOpenJDK Java 11|
|Pivotal tc Server Standard (3.2.14, Tomcat 8.5)|
|WebLogic Server 12cR2 (12.2.1)|
|JBoss EAP 7.1|
|JBoss EAP 7.2||[a]|
[a] JDK 11 is supported only with JBoss EAP 7.2.2 and above; previous versions do not support multi-Release JARs (e.g. Log4j 2).
We support Oracle JDK 8 and AdoptOpenJDK 11 on particular supported application server only if the application server itself officially supports it.
We support the following database servers. The officially supported versions, we are testing against, are in parentheses.
The evaluation version uses an embedded Apache Derby database for evaluation purposes. We do not support using the Derby database in production environment. Instead you can choose one of several supported database servers.