KNIME Server to KNIME Hub Migration Guide

A team is a group of users on KNIME Hub that work together on shared projects. A Team will own specific Hub resources, to which the Team members will have access.

When users are migrated to the Hub one or more teams (depending on the type of license or your KNIME Business Hub) are created and users are assigned to a team and they are assigned a role:

When migrating by using the migration workflow you will migrate items from KNIME Server to KNIME Hub, under a specific team. For this reason, you will need to access the KNIME Business Hub using a user that has assigned team administrator role for the specific team.

The basic concept that is the core of the KNIME Hub operations is the space. A space is a collection of items used to organize components, workflows and files belonging to a project.

Spaces are created for organizing a team’s work around a specific project or domain. Spaces are owned by a team and members of the teams have access to the spaces by default. The permissions can then be defined for each group or user.

The roles and permissions assigned to the team members or to the single users can then be assigned by the team admins.

During the migration process we recommend to transfer folders on the Server into a space on the Hub. Using the migration workflow described in the following sections you will be able to select one or multiple folders from the Server and to move their content (workflows, components and data files) to one or more spaces.

Spaces also will have a default execution context assigned which is the condition necessary for the workflows contained in the space to be executed. During the migration process via the migration workflow you are able to assign an already created execution context to the created spaces. Please note that if you want to migrate the schedule deployments of workflows as explained in the section Deployments, you will need to have assigned an execution context to the space.

On KNIME Business Hub the concept of a version is introduced. A version is a snapshot in time of an item on Business Hub.

An item version history is available to the team members as a list of all the versions that have been created of a specific item.

When using the migration workflow snapshots can be transferred to the Hub as workflows. They will be located in a separate backup folder in the appropriate space and contain the date and comment of the snapshot in their name for later identification.

On KNIME Server, when a workflow was uploaded to the Server it was automatically also possible to execute the workflow as a data app via the KNIME WebPortal, to schedule the execution of the workflows via the KNIME Analytics Platform and to use the workflow as a service to be called either by another workflow or by an external tool.

With KNIME Business Hub, the upload of a workflow to a space on the Hub needs to be followed by the creation of a version and then the creation of the desired deployment.

There are different types of deployments on KNIME Business Hub:

Since it is not possible to detect a priori whether a workflow is deployed as a data app or is executed as a service on KNIME Server, the migration process will need a manual step where the versions are created and the workflows are deployed as data apps or services.

Scheduled workflows instead can be migrated together with their scheduled jobs. Migrating scheduled executions from Server to Hub means that the same workflow will be scheduled on the Hub with the same configuration as on the Server.

By default, those schedules are only created and configured but not enabled. It is recommended to check that a workflow still executes successfully on the Hub before enabling it manually on the Hub. However, if desired, you can also select the option "Enable active schedules on Hub" when performing the migration via the migration workflow. If this option is selected schedules that were enabled on the Server will immediately be enabled on the Hub as well.

Note that “Call Workflow” and “Save Report” actions as well as configured credentials cannot be migrated to the Hub. They require manual configuration.

With this migration method, the files and folders from the Server that you select are migrated to a single space on the Hub. This space can be either one that already exists or a new one.

With this migration method, you can select several folders on the Server to migrate to the Hub. The content of each selected folder will be transferred to a space on the Hub that has the same name as the folder. If a space does not already exist, it will be created automatically.

Clicking the “Analyze” button is optional and gives insights into the selected folders and files, such as the number of workflows and scheduled executions.