Customer Portal

Releases

CloverDX 5.5

Go to Downloads (5.5.2) Latest update March 17, 2020 Documentation

CloverDX 5.5 introduces Data Apps, a new simple interface for business users to interact with data jobs on the CloverDX Server. Additionally, we’ve added a new “support package” to simplify your interactions with CloverCARE support team, and we’ve significantly improved deployment automation.

New features in 5.5

Data Apps

Data Apps is a new front-end for interacting with data jobs aimed at empowering non-technical users. You can publish and share multiple Data Apps without forcing your users into the Server Console or into understanding the underlying implementation. Instead, they access the Server via a new Data Apps Catalog, and each app represents a task they need to accomplish - upload a new file for processing, get an updated report, execute a query, etc. 

Having standalone login page and appealing catalog of available Data Apps, the end users don’t need to know about the existence of backing CloverDX Server at all and they can focus on what matters the most. Custom report generators, analyzers and validators providing on demand data and analysis when they are needed, alongside with reprocessing applications triggering you custom data processing and much more can be available on a single click.

Support Package

The Support Package is a collection of information packed as a ZIP file useful when troubleshooting and investigating production incidents. It’s especially helpful for CloverCARE Support. 

Attaching the archive to support tickets can help expedite the resolution process by providing the support team with all the information typically needed in most support tickets at once. It is recommended to attach it to all tickets related to stability, connectivity or performance of the server.

The Support Package ZIP can be created fairly easy - by a single click at CloverDX Server UI.

Deployment Automation

Configuration XML file exported from CloverDX server can be used as a full backup of particular server because, from now on, it’s possible to override the configuration of the server by Import operation so that the server does not contain anything else but entities from imported configuration XML. In addition, sandbox properties can be exported and imported.

Bundling of configuration with jobs was introduced in 5.5. One can put XML configuration file at sandbox root. Such a configuration file is automatically imported when new sandbox is being created. This is especially helpful when the sandboxes are auto-discovered and auto-created during first start of server but, of course, can be beneficial when creating new sandbox on existing location.

Improved Listing of S3

Recursive S3 listing in ListFiles component was optimized so that it’s much faster than before. In order to decrease memory requirements, the listing is done in a streaming fashion.

Import CloverDX Project from URL

It’s easier than ever before to open a project at CloverDX Designer. The projects can be easily imported from URL. Just copy & paste or drag & drop the URL to CloverDX Designer and that’s it.

Improved Storing of Passwords

In order to improve security, salted hashes are used to store CloverDX user password in database.

In addition, passwords in JMS listeners and Send JMS message tasks are now encrypted using a master password and plain text passwords in imported configuration are encrypted using the master password.

Other Changes

  • Drop support for Firebird and external Derby
  • Drop support of IE 11 and Edge
  • MongoDBExecute component deprecated
  • Introduced support of JBoss EAP 7.2.2+ and JDK 11
  • Updated libs: POI, Jetty, xmlsec, bundled MongoDB driver

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

Fixes

Important: Fixed the decrease in performance of SpreadsheetDataWriter when used in stream mode 		CLO-18564 Fix
Fixed metadata extraction from XLS when formula was present 		CLO-18610 Fix
Trival: Fixed Server Console login page not showing the "Incorrect Login" error message on first run (when the "Activate Server" message is active) 		CLO-18475 Fix
March 17, 2020 Documentation Download CloverDX 5.5 5.5.2

Features & Improvements

Support for IBM Infosphere MDM 11.6 		CLO-15166 Improvement

Fixes

Clustered graph cannot be executed with max_running_concurrently=1 		CLO-18426 Fix
Forced release of runtime environment for jobs with enqueue_executions 		CLO-18375 Fix
Forced release of runtime environment for long running jobs 		CLO-18309 Fix
Using pre-signed key + HTTPS protocol in ListFiles results in File not found 		CLO-18280 Fix
Misrendered editors in server UI 		CLO-17879 Fix
IBM MDM database connections do not work 		CLO-18378 Fix
MDM MEMPUT component doesn't allow mapping to memverno field 		CLO-18269 Fix
February 13, 2020 Documentation Download CloverDX 5.5 5.5.1

Features & Improvements

Data Apps 		CLO-17523 Improvement
Allow user to create support package 		CLO-17357 Improvement
Option to overwrite existing configuration during configuration import 		CLO-17374 Improvement
Export/Import configuration should contain sandbox properties 		CLO-17372 Improvement
Import configuration per sandbox 		CLO-16851 Improvement
Export of sandbox configuration 		CLO-17631 Improvement
Import example project from web 		CLO-17911 Improvement
ListFiles: optimize recursive S3 listing 		CLO-17793 Improvement
ListFiles does not stream results 		CLO-17571 Improvement
Set execution label for jobs triggered by scheduler or listener 		CLO-17486 Improvement
Display execution label at execution history 		CLO-17485 Improvement
Do not resolve config properties placeholders against environment variables by default 		CLO-17597 Improvement
Lower memory requirements by limiting thread stack size 		CLO-17472 Improvement
XSLT Transformer error handling 		CLO-17406 Improvement
Add salts to encrypted password stored in Clover server 		CLO-11414 Improvement
Use master password as encryption key for Remote and JMS listeners passwords 		CLO-17358 Improvement
Auto-creation of LDAP/SAML user should perform strict validation of group existence 		CLO-17333 Improvement Compatibility
Update Setup LDAP to account for env variable syntax 		CLO-17208 Improvement
TableauWriter - Support long data type 		CLO-17180 Improvement
Allow user to dismiss warnings in the Server UI 		CLO-16473 Improvement
Remove default testing user 		CLO-12027 Improvement
Support running Clover on JBoss EAP 7.2.2+ and JDK 11 		CLO-17482 Improvement
Upgrade POI to 3.17 and code cleanup 		CLO-17596
Deprecate MongoDBExecute as it does not work on MongoDB 4.2 and newer 		CLO-17710
Update bundled MongoDB driver to 3.11 		CLO-17738
Upgrade xmlsec library due to security issue 		CLO-17508
Update Jetty container in the Server and in the Designer 		CLO-17414
Drop support of Edge browser 		CLO-17780 Compatibility
Drop support of IE11 		CLO-17543 Compatibility
Drop support of external Derby DB 		CLO-17350 Compatibility
Drop support for Firebird 		CLO-17346 Compatibility

Fixes

OpenSSH config file should be applied always 		CLO-17681 Fix
Entering and confirming HTTPConnector URL dialog escapes already escaped parameters 		CLO-17430 Fix
Wrong Endpoint URL for services behind proxy 		CLO-17330 Fix
SMB2: ListFiles does not return file names on Win10 shares 		CLO-17179 Fix
ListFiles does not return all files from S3 		CLO-17409 Fix
ListFiles returns isFile=true for non-existing HTTP file 		CLO-16967 Fix
JSONReader / JSONExtract should distinct between null values and empty strings 		CLO-10615 Fix Compatibility
S3 consistency issue in writers 		CLO-17364 Fix
Numbers in the monitoring graph squished together 		CLO-17187 Fix
CloverDX Server fails to start on Tomcat 9.0.29 		CLO-17940 Fix
CTL debugging doesn't work correctly in a jobflow 		CLO-16860 Fix
StringIndexOutofBoundsException error when exporting graph as HTML document 		CLO-17435 Fix
JSONExtract cannot load file starting with BOM character 		CLO-18112 Fix
Final dictionary content is not passed to parent job 		CLO-18113 Fix
December 17, 2019 Documentation Download CloverDX 5.5 5.5.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)