CloverETL 4.9.0 (Milestone 1)

This is a milestone (early access) version.
For latest production release, please use the Recent Releases link box.

CloverETL 4.9.0 Milestone 1 brings a major architectural change under the hood of CloverETL Server, aimed at increased fault tolerance and stability in mission critical deployments.

With 4.9 we are splitting the Server code into two separate units. A "worker" runtime executes transformation graphs and jobflows and a core that manages all other functions of the Server (Server Console, user management, scheduler, data services, etc.).

By isolating job execution into a separate process of the host operating system, we are making the Server resilient against potential issues in individual jobs and we allow users more convenient control over resources the worker gets (e.g. user-friendly memory settings).

This new architecture is backwards compatible with previous CloverETL versions and does not require additional modules and licenses.


About this release:

This is a milestone release that we publish as a preview of the upcoming CloverETL 4.9 version. You can expect the production-ready release in March/April 2018 timeframe. Milestone versions are not recommended as a production upgrade. However, some clients successfully run applications using the milestone releases without trouble.


Released Feb 22, 2018
  • Milestone
Recent Releases
4.9.1 Aug 14, 2018
4.9.0 Jul 23, 2018
4.8.3 Jul 17, 2018
4.7.1 Nov 28, 2017
4.6.1 July 19, 2017
4.5.0 Mar 14, 2017

See all releases

New features in 4.9 Milestone 1


Increased Fault Tolerance in Server

CloverETL - Worker

Server code has been split into two separate units. A "worker" runtime executes transformation graphs and jobflows and a core that manages all other functions of the Server (Server Console, user management, scheduler, data services, etc.).

By isolating job execution into a separate process of the host operating system, we are making the Server resilient against potential issues in individual jobs and we allow users more convenient control over resources allocated to the worker (e.g. user-friendly memory settings).

This under-the-hood change is designed to have minimal impact on users. No changes to your projects and or package installation/licensing are required. You will notice new "Worker" panel under Monitoring section and new configuration options under Configuration/Setup but the impact on usage is minimal. See the updated installation instructions for more details.

This new architecture is backwards compatible with previous CloverETL versions and does not require additional modules and licenses.

Filtering Scheduling module

CloverETL - Schedules filter

For users who manage large numbers of schedules in the Server, we're introducing filtering and paging of the Scheduling module, allowing for quick access to individual scheduled jobs.

Compatibility Notes

Please pay close attention to Compatibility Notes when upgrading to 4.9 Milestone 1.


Installation/Upgrade Instructions for CloverETL 4.9 Milestone 1

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

Before You Upgrade

  • This is a milestone release. We recommend you install this version on a test Server first and use it as a preview of upcoming features and for development. Milestone releases are not supported for production use.

  • 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

  • New in 4.9: With the introduction of the Worker, you'll need to configure basic parameters: Worker Server URL and and memory settings in Configuration / Setup / Worker section.
  • 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.




Detailed list of improvements and fixes in 4.9

Server Robustness

Server is now split between two modules: a worker that handles execution of jobs and a "core" that takes care of all the other functions of the Server
Major New Feature 4.9.0-M1

Scheduling

You can now filter the Scheduling tab in Server + better performance for large numbers of schedules.
New feature CLO-11163 4.9.0-M1

Fixes

Increased performance when using global secure parameters
Improvement CLO-11441 4.9.0-M1

Compatibility

JNDI resources need separate configuration for worker
Compatibility CLO-12796 4.9.0-M1
ProfilerProbe cannot persist results in Worker
Compatibility CLO-12796 4.9.0-M1

Known Issues

CTL debugging does not work with Worker
Known Issue CLO-12778 4.9.0-M1
JMS event listener cannot pass non-serializable objects to worker
Known Issue CLO-12552 4.9.0-M1


ETL Developers (This item is most useful for developers; it either brings new functionality for transforming data or brings optimizations)

Administrators (This item is an improvement or feature that will help setup, install, administer and manage the application)

Support (This item helps staff supporting the production operation to identify potential problems or avoid such)