This document guides you through the steps that are needed to update an existing KNIME Server installation from version 4.6 to 4.7 or apply a bugfix for version 4.7. You will find a complete guide to installing KNIME Server in the KNIME Server Quickstart Installation Guide, and a complete description of all configuration options in the KNIME Server Administration Guide. If you have any questions or need assistance with the update process, please contact your dedicated KNIME support specialist.



  • This guide assumes you already have either KNIME Server 4.6.x or KNIME Server 4.7.x running.

    A recent update of Java to version 8u272 will cause KNIME Server installations to no longer be able to connect to a secured LDAP authentication system. we recommend not updating the Java installation to version 8u272 on your KNIME Server. If you have already done this, we suggest you revert it. If you run into any issues or need further information please contact the KNIME support team at support@knime.com.

Client & RMI

  • KNIME Analytics Platform clients need at least KNIME ServerSpace 4.0 otherwise it will not be able to talk to the server.

  • KNIME Server 4.7 requires at least KNIME Analytics Platform 3.6 as RMI workflow executor with the corresponding KNIME Executor Connector version 4.7 on the server side.

  • New KNIME WebPortal features are available with any supported web browser.


Even though all the data on the server should be preserved during the update it is highly recommended to create a backup of all important data (see KNIME Server Administration Guide for backup information).

Application server

Before performing an update, make a backup of <tomee-folder>/conf/Catalina/localhost/knime.xml. The name of the file might be different if the .war file had a different name (e.g. com.knime.enterprise.server.xml)


  1. Download the updated war file com.knime.enterprise.server_4.7.x.war from the download page. If updating from 4.4 or lower, then you will also need to download the supplementary knime-tomcat.jar.

  2. Stop TomEE.

  3. Delete the existing folder <tomee-folder>/webapps/knime (or similar if the .war file had a different name).

  4. Copy the new com.knime.enterprise.server_4.7.x.war over the existing war file (usually <tomee-folder>/webapps/knime.war). Please note that it needs to be the same file name as this is what is referred to as context in the application.

  5. Check if the knime.xml file that you backed up before still exists. If not copy the backup to the previous location.

  6. Copy the downloaded file knime-tomcat.jar to <tomee-folder>/lib

  7. Follow the steps below on updating the KNIME Server Executor, specifically watch out to merge changes to the knime.ini in the workflow repository (<server repository>/config/knime.ini), if any.

  8. Start TomEE.

Note that it is not possible to run multiple KNIME Server instances in one TomEE installation.

KNIME Server Executor

You must update the KNIME Server Executor to at least version 3.5 and the "KNIME Executor connector" to version 4.7.

If possible, start the executor installation in graphical mode (using the correct installation user!). If you have internet access, go to File → Update KNIME… and it will suggest updating to the new version. Follow the steps in the wizard. If you don’t have direct internet access, you must download the zipped update sites from the commercial downloads page (where you also found this update guide). Then register the ZIP files in File → Preferences → Install/Update → Available Software Sites and go to File → Update KNIME…

If you cannot start the graphical user interface, you can use the update-rmi.sh script that is in the root of the executor installation. Call the script on the command line and provide a list of update sites that contain the new versions of the installed extensions and all installed extension will be updated (given that an update is available):

./update-rmi.sh http://update.knime.org/analytics-platform/3.6,\

If you get error messages when executing update-rmi.sh about missing "installable units", make sure that you have provided all necessary update sites.

If you have the KNIME Big Data Connectors and/or KNIME Spark Executor extensions installed, then the update script of 3.4 will not find updates because the extensions were renamed when we open-sourced them. However, once you have updated all other extension using the above command, the updated version of the update script will be able to find the renamed extensions. Just run the above command a second time.

Preference file and knime.ini file

Make sure the preference file is proper and merge your changes from the old knime.ini file to the new knime.ini file!

Installing a new KNIME Server Executor

You can also install a completely new KNIME Server Executor instead of updating an existing executor. To install KNIME Analytics Platform 3.6 from scratch you will need to run it as the user that owns the Installation.

Once logged in as the correct user, install KNIME Analytics Platform together with all the extensions needed for the workflows that will be executed on the server. Also install all "KNIME Server-Side Extensions" from the KNIME.com update site (you may need to enable this update site in the KNIME preferences under "Available Update Sites"). If you use the KNIME WebPortal, also install the KNIME Report Designer extensions.

If this installation will also be used by end-users (as a local desktop application), be sure to install the "KNIME ServerSpace" from the same KNIME.com update site.

Set relevant preferences in KNIME and export to <server repository>/config/preferences.epf.

Similarly, be sure to copy your new knime.ini file (from the KNIME Analytics Platform installation folder) to your server repository (<server repository>/config/knime-rmi.ini).

Please refer to the KNIME Server Administration Guide for more details about installing a KNIME Server Executor.

After installation, you need to point the KNIME Server to the new installation location. If you have a symbolic link on a Linux system that is used to start the KNIME Server Executor, simply remove this link and re-define it pointing to the new installation folder. If you do not have a symbolic link, you need to change the value of the com.knime.server.executor.knime_exe configuration option.

KNIME Server license

The KNIME Server license continues working with the new server. If you haven’t received a license file or if it is not working correctly, please contact KNIME or your dedicated KNIME support partner.