Customer Portal

CloverDX 5.4 continues to improve containerized deployment and brings support for orchestrated architectures (e.g. Kubernetes). For the support staff, we’ve looked at improvements in incident diagnostic and robustness.

New features in 5.4


Introduction of Docker in the previous release was the first piece of a bigger puzzle of the containerized architectures. In this version we’ve added support for an orchestration layer, namely Kubernetes.

We’ve prepared a sample architecture (available here) that contains everything you’ll need to take the first steps — CloverDX itself, a database, an API gateway and monitoring tools — all packed into a fully operational end-to-end integration platform that you can further extends to your needs.

Robustness, Diagnostics & Performance log

We’ve been pushing CloverDX to be your platform of choice for ever more complex scenarios. With this release we’re introducing yet another set of improvements in Server maintenance:

  • Executions History can now display a much larger execution hierarchy without slowdowns in the UI

  • Archivator runs much faster with fewer system resources

  • Server now stores JVM’s garbage collector logs for later diagnostics

  • We’ve added a brand new “performance” log that shows utilization of resources such as CPU, memory, GC and threads 

These changes give you finer control and diagnostic options for large tasks involving complex transformation processes and large volumes of data.

User management improvements

CloverDX is now able to automatically create new users who successfully authenticate over LDAP and SAML. This means you can now fully manage your user base outside of CloverDX without the need to explicitly add or remove users in the Server Console.

New SSH/SFTP keys and configuration management

Security is a concern for all of us and this time we’ve looked at key management, also in line with container deployment and orchestration.

CloverDX now support OpenSSH configuration files natively so that you can store secrets in a safe location and better manage their lifecycle.

Metadata and CTL code editor - The daily life of an ETL developer

The dynamic SQL Metadata Editor (introduced in 5.3) now shows a useful preview.

The CTL (Transform) Editor shows more information about function parameters in the code assist dropdown. We believe both of these changes will help you work much faster.


Other changes

  • Added support for Tableau .hyper format

  • Automatic configuration import during startup

  • Create/upload of individual files in Sandboxes module

To help you install or upgrade to this version, we've prepared a simple checklist:

Before You Upgrade

  • Be sure to check the "Compatibility" notes for ALL intermediary releases. We mark all changes that can potentially alter the function of your existing transformations with a "Compatibility" label. Typically, you can safely ignore most of them, as we try hard to keep as much backwards compatibility as possible. There's a comprehensive list of all releases that will help you get the information quickly.
  • Upgrade Designer and Server together. We always release Designer and Server together under a single version. It's highly recommended to upgrade Server and all Designers at the same time. Although using different versions of Designer to connect to Server might work, it is not generally supported.
  • There are no incremental patches. We don't release incremental patches. Every upgrade is in fact a full installation that, if installed over the older version, will automatically update whatever is necessary in your workspaces, sandboxes, and Server databases as needed, no user data will get overwritten.
  • Don't forget to backup. Although none of the above upgrade steps requires explicit backup, we recommend you always back up your work. The upgrade will keep all your transformations, jobflows, and configurations safe. However, as a good word of advice, it never hurts to have a backup.

Designer Upgrade

  • Download the latest version by logging into your customer account. If you lost your credentials or no longer have access there, click here to recover your password or contact our CloverCARE Support.
  • Install the new version of Designer. You can install Designer over your existing installation. The process will automatically clean up the old version. Don't worry, you will NOT lose your workspaces, graphs, and transformations. However, if you installed some additional plugins to Designer (Eclipse plugins) you might need to reinstall them. Eclipse should automatically help you do that. When you start the application, point it to your existing workspace directory. With some major releases, we may notify you about upgrading the workspace to the latest version. In such cases, you won't be able to use the workspace with previous versions—be sure to upgrade ALL Designers at once if you're sharing the workspace.
  • Activate the product on first start. You will need a new key as we issue new license keys for every new major version (e.g. from 4.9 to 5.0). If you're on our maintenance program, we automatically renew the keys for you. Just go to the License Keys again and copy/paste the license keys from there. If you can't find the latest keys, please contact us to renew your product maintenance.

Server Upgrade

  • Download the latest version by logging into your customer account. You'll find Server in the same list as Designer downloads. If you no longer have access there, click here to recover your password or contact our CloverCARE Support.
  • Plan for downtime. Upgrading Server requires downtime, so plan your upgrades in advance. If you're running multiple environments, upgrade the non-production installation first and run all your tests there first.
  • Follow our step-by-step Server Upgrade Guide. We've prepared detailed instructions on how to properly shut down Server and install a new one. Server will upgrade its database and sandboxes from any previous version automatically.
  • Activate the product on the login screen of Server Console. Server requires new license keys with every major version (e.g. from 4.9 to 5.0) and we automatically renew the keys for you. Just go to the License Keys again and copy/paste the license key from there.


Release Compatibility/Upgrade notes, Features & Fixes Published Download

Features & Improvements

Periodic logging of performance metrics
CLO-17383 Improvement
Log system information on Core and Worker startup
CLO-17275 Improvement
Performance optimisation of Execution Hierarchy tree
CLO-17199 Improvement
Support environment variables in configuration import
CLO-17049 Improvement
Automatically import configuration during server init
CLO-16849 Improvement
EmailSender timeouts attributes
CLO-17198 Improvement
Support multiple tables in Tableau .hyper extract
CLO-17020 Improvement
Support Tableu SPATIAL data type
CLO-17047 Improvement
Sending User-Agent Header in HTTP(S) Requests
CLO-16971 Improvement
Enable GC logging by default in worker
CLO-16832 Improvement
Add "Upload file" and "Create file" actions to Sandboxes context menu
CLO-17031 Improvement
SQL Query Metadata Preview
CLO-16642 Improvement
SQL Query editor - browse DB and query assistant
CLO-16640 Improvement
Ability to show metadata when editing CTL code
CLO-16403 Improvement
Remove default webapps from our Tomcat package
CLO-13595 Improvement
Support parsing of OpenSSH config file
CLO-12766 Improvement
First time login using LDAP/SAML should create a new clover user account
CLO-8336 Improvement


PostgreSQLBulkWriter Omits Milliseconds when Loading Data
CLO-17232 Fix
Unresponsive cluster node makes server UI very slow
CLO-17158 Fix
DBJoin does not reset output records before transform()
CLO-17058 Fix
Protocol smb2 is not able to connect to URLs without credentials
CLO-16834 Fix
Typo in name of JMS graph parameter (JMS_MSG_DESTIONATION)
CLO-16576 Fix
Resizing SQL Query Editor Window does not Affect Size of Query Field
CLO-17206 Fix
September 19, 2019 Documentation Download CloverDX 5.4 5.4.0
  • For Developers (Improvements most useful for developers bringing new functionality or optimizations in data transformation and orchestration)
  • For Administrators (Improvements or features that will help setup, install, administer and manage the platform)
  • For Support (Helps staff supporting the production environment to identify and escalate potential problems or avoid such)
  • For Security (Improvements and changes relevant to security focused staff – sys admins and developers alike)