Customer Portal

Releases

CloverETL 4.7

Go to Downloads (4.7.1) Latest update November 27, 2017

CloverETL 4.7 brings Data Services that allow you to publish transformations to applications as APIs. With Data Services you can publish a transformation graph as a (REST) API endpoint. That means you can create smart data sources or data targets that process data on-the-fly and make either data, or business logic or a combination of both, available to applications on-demand.

 

New features in 4.7

Data Services—Publish data and transformations as API

We're introducing a new Data Service REST job, a data transformation that can be published as a REST API endpoint on CloverETL Server.

While transformations are traditionally executed by a scheduler or event trigger, Data Services jobs introduce user-defined API endpoints on CloverETL Server that applications can use to get data processed by underlying transformations on-demand.

How to Start With Data Services (video) 

Compatibility note—Launch Services: Data Services feature is planned to replace Launch Services in the long-term. However, Data Services are not (currently) compatible with Launch Services—we're implementing Data Services from the ground up. Launch Services will remain fully supported in version 4.7. However, we recommend users of Launch Services to become aware of Data Services. There's no rush now. We will announce the replacement plans in more detail well ahead, giving current Launch Services users plenty of time to plan and implement the switch.

Contact Us—If you're interested in learning more about Data Services and how it can support your current or planned use of Launch Services/REST API, please contact us through our dedicated Data Services contact form. Our engineers will be able to answer your questions and will be more than happy to show you the new feature and its potential.

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.6 to 4.7). If you're on our maintenance program, we automatically renew the keys for you. Just go to the download area 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

  • Upgrading from milestone: Please note that CloverETL Server 4.7.0-Milestone 1 cannot be upgraded to production version of 4.7.0. Please perform clean install instead. However, you can continue using your projects and sandboxes.
  • 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.6 to 4.7) and we automatically renew the keys for you. Just go to the download area again and copy/paste the license key from there.
Release Compatibility/Upgrade notes, Features & Fixes Published Download

Data Services UI Improvements

Improved context menu for Publish and Unpublish actions 		Improvement CLO-11893 4.7.1
Added information window to help deploy and use Data Services Examples 		Improvement CLO-11965 4.7.1
Added an option to remove Data Services Examples 		Improvement CLO-11886 4.7.1

Fixes

Fixed: When multiple output ports were used in a Data Service, data from first output port would get replicated to second and subsequent ports. 		Fix CLO-11902 4.7.1
Data Services testing page no longer asks for logging again. 		Fix CLO-11876 4.7.1
Fixed memory leak in Groovy script (in Event Listeners) 		Fix CLO-11793 4.7.1
Fixed URL encoding of colon ':' in File URL. Now %3A properly works as an alternative to ':'. 		Fix CLO-11849 4.7.1

Compatibility

Updated Server All-in-one bundle with Tomcat 8.0.47 		Compatibility New CLO-11923 4.7.1
November 27, 2017 Download CloverETL 4.7 4.7.1

Data Services

Major new feature. With Data Services you can combine data and transformations into "smart data endpoints" that you can publish on CloverETL Server as REST API endpoints. This way you can expose a piece of shared data logic implemented as a CloverETL graph or give applications an on-demand access to data that's transformed on-the-fly to meet their requirements. 		Major New Feature CLO-11103 4.7.0

Designer Improvements

Graphs are now validated immediately after making changes to component attributes, not just after saving them. 		Improvement CLO-10784 4.7.0-M1

Connectors

SMBv2 and SMBv3 are now supported. Please make sure you follow the instructions on 		Improvement CLO-11209 4.7.0-M2
JNDI access from CustomJavaComponent. See 		New Feature CLO-11405 4.7.0-M2

Additional Features

We expanded dynamic metadata to support virtually any data type (e.g. arrays) by converting it to CloverETL "string" field. There's a new option called "ignoreUnknownTypes". Set it to "true" and CloverETL will create corresponding "string" fields for all columns with unknown data types. Read more in 		New Feature CLO-11740 4.7.0

Fixes

A File Listener watching S3 no longer returns an error "S3 URL does not contain valid keys". 		Compatibility Fix CLO-9981 4.7.0
Fixed: ConcurrentModificationException error when modifying "list" or "map" dictionary entries in one component (e.g. in Reformat) and having Success component in the same phase as the component that modifies the entries. 		Fix CLO-11697 4.7.0
Fixed CopyFiles failing when "Overwrite" was set to "update" 		Fix CLO-11678 4.7.0
Fixed SMB2 not working on WebLogic 12 in CloverETL 4.7.0-M2 		Fix CLO-11636 4.7.0
Fixed issues with some XML namespace declarations (xml:lang) disappearing after saving a mapping in XMLWriter. 		Fix CLO-11398 4.7.0
Fixed missing icon error in Error Log of Designer on Mac OS X 		Fix CLO-11601 4.7.0
Fixed missing edge record counts in subgraph when it's executed for the first time. 		Fix CLO-5139 4.7.0
Fixed Validator Lookup rule not working with DBLookup 		Fix CLO-11488 4.7.0-M2
FlatFileReader now correctly fails when a requested file doesn't exist in archive 		Fix CLO-11350 4.7.0-M2

Compatibility

Data Services feature is planned to replace Launch Services in the long-term. However, Data Services are not compatible with Launch Service. We're building Data Services from the ground up. Launch Services remain fully supported in version 4.7. However, we recommend affected users to become aware of Data Services and their capabilities. There's no rush now, we will announce the replacement plans in more details well ahead, giving current Launch Services users plenty of time to plan and implement the switch. If you're interested in learning more about Data Services and how it can support your current or planned use of Launch Services/REST API, please contact us through our dedicated Data Services contact form. Our engineers will be able to answer your questions and will be more than happy to show you the new feature and its potential.we will announce the replacement plans in more details well ahead, giving current Launch Services users plenty of time to plan and implement the switch. If you're interested in learning more about Data Services and how it can support your current use of Launch Services, feel free to contact us on a dedicated Data Services contact form, our engineers will contact you shortly. 		4.7.0-M1
A File Listener watching S3 no longer returns an error "S3 URL does not contain valid keys". 		Compatibility Fix CLO-9981 4.7.0
Server internal database schema updated. Server will automatically upgrade its database upon restart. 		Compatibility New CLO-11353 4.7.0-M2
Internal cleanup: Removed cloveretl.binutils and unused binaries from cloveretl.bulkloader 		Compatibility Cleanup CLO-11508 4.7.0-M2
Upgrading from milestone: Please note that CloverETL Server 4.7.0-Milestone 1 cannot be upgraded to production version of 4.7.0. Please perform clean install instead. However, you can continue using your projects and sandboxes. 		Compatibility 4.7.0

Known Issues

Fixed known limitations from Milestone 1. See issue codes for more details. 		Fixed CLO-11240 CLO-11247 CLO-11309 4.7.0
October 09, 2017 Download CloverETL 4.7 4.7.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)