Chapter 5. Upgrading Server to Newer Version

General Notes on Upgrade

Upgrade Prerequisites

Upgrade Instructions

  1. Suspend all sandboxes, wait for running graphs to finish processing

  2. Shutdown CloverETL Server application (or all servers, if they run in cluster mode)

  3. Backup existing CloverETL database schema (if any changes to the database schema are necessary, the new server will automatically make them when you start it for the first time)

  4. Backup existing CloverETL web application archive (clover.war) & license files (on all nodes)

  5. Backup existing CloverETL sandboxes (on all nodes)

  6. Re-deploy the CloverETL Server web application. Instructions how to do that are application server dependent - see Enterprise Server for installation details on all supported application servers. After you re-deploy, your new server will be configured based on the previous version's configuration.

  7. Replace old license files by the valid one (or you can later use web GUI form to upload new license). The license file is shipped as a text containing a unique set of characters. If you:

    • received the new license as a file (*.dat), then simply use it as new license file.

    • have been sent the licence text e.g inside an e-mail, then copy the license contents (i.e. all text between Company and END LICENSE) into a new file called clover-license.dat. Next, overwrite the old license file with the new one or upload it in the web GUI.

    See Installation of CloverETL Server License for details on license installation.

  8. Start CloverETL Server application (on all nodes)

  9. Review that contents of all tabs in CloverETL Server Console, especially scheduling and event listeners looks OK.

  10. Update graphs to be compatible with the particular version of CloverETL Server (this should be prepared and tested in advance)

  11. Resume the test sandbox and run a test graph to verify functionality

  12. Resume all sandboxes

Rollback Instructions

  1. Shutdown CloverETL Server application

  2. Restore CloverETL Server web application (clover.war) & license files (on all nodes)

  3. Restore CloverETL Server database schema

  4. Restore CloverETL sandboxes (on all nodes)

  5. Start CloverETL Server application (on all nodes)

  6. Resume the test sandbox and run a test graph to verify functionality

  7. Resume all sandboxes


Evaluation Version - a mere upgrade of your license is not sufficient. When moving from evaluation to enterprise server, you should not use the default configuration and database. Instead, take some time to configure Clover Server so that it best fits your production environment.