Version

    System requirements

    Hardware requirements

    This section outlines the hardware requirements for deploying CloverDX Server in standalone and cluster configurations.

    Standalone Server environment

    The following table shows hardware requirements for standalone CloverDX Server environments.

    Table 4. Hardware requirements
    Hardware Minimum Recommended

    RAM

    8 GB

    32 GB

    Processors

    2 cores [1]

    8 cores [1]

    Disk space (installation)

    2 GB

    Disk space (temp space)

    > 25 GB [2]

    Disk space (data)

    > 50 GB [2]
    1

    A CPU core in this context is a logical core. Most modern processors use simultaneous multi-threading (called Hyper-Threading by Intel) and the number of logical cores is double the number of physical cores. See CPU recommendations below for more information.
    2

    Minimum value, the disk space requirements depends on data and the processes you run on CloverDX Server.
    Server cluster environment

    The hardware requirements for standalone Server environments also apply to individual Server nodes in a cluster. When setting up a cluster, ensure that all cluster nodes have the same hardware configuration and each node has at least 50 GB of disk space reserved for shared sandboxes. Additionally, keep in mind that the total number of CPUs specified in the Server license represents the combined total of logical CPUs across all server nodes.

    CPU recommendations

    Non-production environments with low job volumes or no resource-demanding tasks can often suffice with a minimum of 2 logical CPU cores. This configuration can provide adequate performance for development, testing, or staging purposes.

    However, for production environments or those handling heavy workloads, 8 logical CPU cores are generally recommended as a baseline. This configuration offers more processing power, allowing for efficient execution of demanding tasks and maintaining optimal system performance.

    It’s important to note that these are general guidelines. The ideal number of CPU cores can vary significantly based on specific factors such as:

    • Job complexity: The nature and resource requirements of the tasks being processed.

    • Workload intensity: The volume and frequency of jobs.

    • Other system resources: The availability of memory, storage, and network bandwidth.

    To determine the optimal number of CPU cores for your environment, carefully evaluate your specific needs and consider factors such as performance benchmarks, historical data, and future projections. Consulting with system experts or using performance monitoring tools can also provide valuable insights.

    Note that your CloverDX Server license includes information regarding the maximum number of CPU cores that the Server can utilize. This licensing restriction is an additional factor to consider when determining the appropriate number of CPU cores for your deployment. Please refer to your licensing agreement for specific details or reach out to your account manager for further information.

    Software requirements

    CloverDX Server requires a compatible operating system, an application server, Java Development Kit (JDK) and a database to run. Together, these requirements are called a stack. Not every combination of the supported vendors or software product version are supported by CloverDX Server. This section provides details about the supported configurations of software dependencies for CloverDX Server.

    At the same time, CloverDX Server can be deployed in different circumstances - either as a production instance, as a test/non-production instance, or as an evaluation instance. Production instances must follow the software stacks as described below to ensure full support and maximum stability of the platform.

    Using unsupported configurations may lead to unexpected behavior, errors, or instability within your CloverDX deployment. Adhering to the officially supported stacks and database versions ensures a reliable and functional CloverDX environment.

    Note that CloverDX Server requires a Java Development Kit (JDK) to run. JRE is not supported.
    Production deployment
    1. Operating system

    Pick any of the systems listed below (recommended option in bold).

    Operating system

    Red Hat Enterprise Linux 8

    Red Hat CentOS 7

    Ubuntu 20 LTS and 22 LTS
    2. Application server and JDK combinations

    Pick an application server and JDK combination (recommended option in bold). Only these specific combinations (options 1, 2, 3) are officially supported. Other application server or JDK combinations may not function correctly or may not be compatible with the CloverDX platform.

    Table 5. Supported application server and JDK combinations
    Option Application server JDK version and provider

    Option 1

    Apache Tomcat 9 (64 bit)

    Eclipse Temurin JDK 11 or 17 HotSpot 64-bit (formerly AdoptOpenJDK)

    Option 2

    VMware tc Server Standard 4.1 (with Tomcat 9.0 runtime)

    BellSoft Liberica JDK 11 64-bit

    Option 3

    Red Hat JBoss Web Server 5.4

    Red Hat OpenJDK 17 64-bit

    When using Apache Tomcat as your application server, you can use Eclipse Temurin JDK 11. This may be useful if you require Java 11 compatibility for some reason (e.g., legacy 3rd party drivers or libraries). However, we recommend always using Java 17 if you can, as it is more secure and has higher performance.
    3. System database

    A system database stores CloverDX Server’s configuration and variety of logs. You can pick any of the databases mentioned in the list below (recommended option in bold). We support only the listed major version for each database below, but you can pick a different minor/bugfix version of each. We use the exact version listed in our test environment.

    Database provider Supported major version Version used in internal tests

    PostgreSQL

    15

    15.5

    MySQL

    8

    8.0.25

    Oracle

    23

    23.4.0

    MS SQL Server

    2022

    16.0.4105.2

    DB2

    11

    11.5.7.0

    As you can see from the above, the preferred stack to use is RHEL + Apache Tomcat + Temurin JDK 17 + PostgreSQL 15. This stack uses mostly open-source components and is therefore simple to install and run.

    The other stacks use commercial components which come with their own support policies. Ensure that you understand those policies before selecting any of the commercial stacks.

    Non-production deployment

    For your non-production deployments, you should generally follow the same configuration as for your production instances. This will ensure maximum compatibility between your instances which is especially important during promotion of code from dev/test environments to your production.

    Same technology requirements hold for non-production deployments as for production deployments. Usually, the non-production instances are smaller (e.g., 4 cores instead of 8) or do not have as high redundancy (e.g., 2-node cluster instead of 4).

    Evaluation deployment

    Evaluation deployments are useful when you are trying new version of CloverDX Server to try a new feature, when evaluating CloverDX platform for the first time or during trainings etc.

    To make the evaluation as simple as possible, we offer one more way of installing the CloverDX Server - you can use it without external system database. In such case, CloverDX Server will use its own instance of Apache Derby database.

    Additionally, evaluation instances can also be installed on operating systems Microsoft Windows 10 (64-bit), Microsoft Windows 11 (64-bit) or macOS 13 (Ventura) and newer.

    To make the installation as easy as possible, we offer a "bundle" which contains Apache Tomcat with already deployed CloverDX Server instance which is configured to use embedded Derby instance as its system database.

    Supported web browsers for CloverDX Console

    CloverDX Server Console is a web interface that can be used to manage and monitor CloverDX Server instances. It is a web app and requires the following browsers to run (recommended option in bold):

    • Google Chrome (latest)

    • Mozilla Firefox (latest)

    Using any other recent browser (e.g., Microsoft Edge or Apple Safari) should work but is not supported or recommended.