Icon

KNIME Server to KNIME Hub Migration

This workflow guides you through the steps to migrate workflows, components, datafiles, snapshots, and schedules from KNIME Server to KNIME Hub. The items will be migrated to spaces in a given Team on KNIME Hub.

This workflow is expected to be executed in the KNIME WebPortal on KNIME Server.

URL: Documentation https://docs.knime.com/latest/migration_server_to_hub_guide/index.html

Copy Data to KNIME Hub...and create schedules.This process usually takes the longest. ConnectionThe loop is to ensure that a connection is not needed foreach team KNIME Server Meta DataDownload all data and decide where it needs to be put. KNIME Server to KNIME Hub MigrationData App to be executed in the WebPortal of KNIME Server Wrap up... or migrate to another Team. Prepare Logs for downloading. Info if Connection is not working... otherwise the data app will say "Execution Finished Successfully" Can't proceed due to invalid settings or errors... otherwise the data app will say "Execution Finished Successfully".Schedues can only be migrated with an attached Execution Contextand if the number of schedules limit is not reached. Compatible with Source: • KNIME Server 4.15.8 and above with Executors Versions 4.6.5Destination: • Business Hub 1.12 and above • Community Hub Team planon errortop: itemsbot: schedulesfor connectionConnection not sucessfulcollect errors...Log fileExecution Context missingfor connectionon errorredo e.g. toanother team,different settings, ...use the same connectionfor multiple teamsConfigure Server andHub Connections (#1) Copy items toKNIME Hub (#4) Active BranchInverter (#29) Team MigrationSummary (#1491) Team, Space, and DataSelection (#1552) MigrationFine-tuning (#1641) Table Row toVariable (#1643) Source DataAnalysis (#1644) Workflow ApplicationHeader (#1691) Migrate Schedules(#1781) Concatenate (#1782) Wrap up Migration(#1783) Workflow ApplicationHeader (#1784) Table Row toVariable (#1785) Active BranchInverter (#1786) Variable ConditionLoop End (#1789) Generic LoopStart (#1790) Copy Data to KNIME Hub...and create schedules.This process usually takes the longest. ConnectionThe loop is to ensure that a connection is not needed foreach team KNIME Server Meta DataDownload all data and decide where it needs to be put. KNIME Server to KNIME Hub MigrationData App to be executed in the WebPortal of KNIME Server Wrap up... or migrate to another Team. Prepare Logs for downloading. Info if Connection is not working... otherwise the data app will say "Execution Finished Successfully" Can't proceed due to invalid settings or errors... otherwise the data app will say "Execution Finished Successfully".Schedues can only be migrated with an attached Execution Contextand if the number of schedules limit is not reached. Compatible with Source: • KNIME Server 4.15.8 and above with Executors Versions 4.6.5Destination: • Business Hub 1.12 and above • Community Hub Team planon errortop: itemsbot: schedulesfor connectionConnection not sucessfulcollect errors...Log fileExecution Context missingfor connectionon errorredo e.g. toanother team,different settings, ...use the same connectionfor multiple teamsConfigure Server andHub Connections (#1) Copy items toKNIME Hub (#4) Active BranchInverter (#29) Team MigrationSummary (#1491) Team, Space, and DataSelection (#1552) MigrationFine-tuning (#1641) Table Row toVariable (#1643) Source DataAnalysis (#1644) Workflow ApplicationHeader (#1691) Migrate Schedules(#1781) Concatenate (#1782) Wrap up Migration(#1783) Workflow ApplicationHeader (#1784) Table Row toVariable (#1785) Active BranchInverter (#1786) Variable ConditionLoop End (#1789) Generic LoopStart (#1790)

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: knime
Created at: 2023-01-26
On NodePit since: 2023-03-04
Last update: 2025-03-29
Created with KNIME version: v5.4.3
Tags: MigrationKNIME ServerKNIME HubWorkflow Application

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!