Team Plan on KNIME Community Hub Guide

To create a team, you need to subscribe to a Team plan. To do so, sign in with your KNIME Hub account and navigate to Pricing in the top right corner of the page, or go to KNIME Hub pricing page. Here you can proceed with the subscription to the Team plan.

You will be asked to provide the details of the account and your payment information. Then, you can choose your subscription plan. You can choose how much disk storage and how many users you would like to purchase. The basic plan consists of 30GB of disk storage and a total of 3 users. Please note that the subscription will be automatically renewed every month if not canceled, and that users and disk storage can be adjusted later. Your usage will be prorated for the next billing cycle. To change or cancel your subscription, follow the instructions in the section Manage team subscription.

Once you have successfully purchased a team, you can assign it a name and start adding members to your team. The number of members that can be added to the team is limited to the number of users that you purchased.

There are two types of roles a user can be assigned when part of a team:

The team creator is automatically assigned the administrator role and can promote any of the team members to administrators. In order to do so, please follow the instructions in the section Manage team members.

A team can own an unlimited number of both public and private spaces.

You can create a new space by going to the team’s profile. To do so, click your profile icon in the top right corner of KNIME Hub and select your team. In the tile Create new space, click Private space to create a private space for your team, or Public space to create a public space. You can then change the name of the space, or add a description. You can change or add these also later by going to the relative space page and clicking the space name or Add description button to add a description for the space.

Furthermore, you can change the visibility of the space from private to public and vice versa, or delete the space. To do so, from the space page, click the icon, as shown in the image below.

You can also manage the access to a specific space. To do so, navigate to the space and click the icon.

In the Manage space access side panel that opens, you can add other team members. You can change the rights they have on the items in the space - e.g. you can grant them Edit rights or View rights for this space.

Click the icon to inspect the individual team members and their rights separately.

You can manage your team by going to the team’s profile. To do so, click your profile icon in the top right corner of KNIME Hub.

In the dropdown menu that opens, you will see your teams. Select the team you want to manage to go to the corresponding team’s profile page.

Here, you can click the Manage team button to open the Manage members side panel, as shown in the image below.

You will see here a list of the team members and their assigned roles.

From here, a team admin can change the roles of the team members. To do so, click the drop down arrow close to the name and select the roles you want to assign to each user.

Then click the Save changes button to apply your changes.

On the team’s profile page, you can also change the name of the team. To do so, double-click the name of the team under the team logo on the left side of the page.

Insert the new name, and click the button to confirm.

On the team’s profile page, hover over the team profile icon and click on Upload new to select an image from your local computer.

You can manage your subscription on the Subscription page. On the team’s profile page, select Subscription on the side menu to access it.

Here you can:

*Show the cost breakdown: Click Show cost breakdown to see the amount to be paid for your Team plan and the consumed credits for execution.

You can manage the execution context of your team by navigating to your team overview page and selecting Execution resources from the menu on the left.

Here, among other things, you can edit the execution context settings, disable or delete your execution context, or show the details of the CPU usage, the jobs that are running on the execution context and so on.

To do so select the appropriate option in the menu that opens when clicking in the tile of the execution context.

To monitor your execution consumption and projected costs, you can go to your subscription page.

Go to your team page and select Subscription from the menu on the left.

Once the execution context is set up you can run and schedule the workflows that are uploaded to your team’s spaces on KNIME Community Hub. Navigate to a workflow in one of your team’s spaces, you will see a Run button and a Deploy button.

Click Run to simply execute the current workflow directly in the browser. The latest version of your workflow will be executed, or you can select which version of the workflow you want to run. In the side panel that opens you can also enable the workflow actions, for example allowing the system to send you an email when the chose condition is met.

A new tab will open where the result of the workflow execution will be shown. If your workflow is a data app you will be able to interact with its user interface. To know more about how to build a data app refer to the KNIME Data Apps Beginners Guide.

To see all the ad hoc jobs created for a workflow navigate to the workflow page and select Ad hoc jobs from the right side menu.

A schedule allows you to set up a workflow to run automatically at selected times.

To create a schedule deployment of your workflow navigate to a workflow in one of your team’s spaces. In order to be able to create a schedule deployment you need to have created at least one version of your workflow. To know more about versioning read the Versioning section of this guide. Once you have your stable version of the workflow, create a version (click Versions → Create version). Now you can click the button Deploy and select Create schedule.

This will open a side panel where you can set up the schedule deployment.

Here you can select a name for your schedule deployment and which version of the workflow you want to schedule for execution.

In the section Schedule options you can define when the workflow should be executed:

Every time a workflow is executed a job is created on KNIME Hub.

To see the list of all the jobs that are saved in memory for the ad hoc execution of a specific workflow go to the workflow page and on the right side menu click Ad hoc jobs.

To see the list of all the jobs that are saved in memory for each of the deployments created for a specific workflow, go to the workflow page and on the right side menu click Deployments. You can expand each deployment with the icon on the left of the deployment.

Also you can go to your team page and find a list of all deployments created within your team. Also here you can click the icon corresponding to a specific deployment to see all its jobs.

On each job you can click the icon on the right of the corresponding job line in the list and perform the following operations:

All the extensions developed by KNIME are available to run workflows on KNIME Community Hub.

This includes the following extensions:

Refer to the KNIME Google Cloud Integration User Guide to know how to create an API Key and to learn more about the general usage of the Google Authenticator node.

To access data from Google Cloud the first step when building your workflow is to use a Google Authenticator node. One of the possibilities is then to use the API Key authentication method. When using the API Key authentication method in the Google Authenticator node, the API key file will need to be stored somewhere where it is accessible to the node in order for the execution to be successful.
For example, if your folder structure on the KNIME Community Hub (KCH) looks something like the one below, meaning that your API Key file is stored in the following path:

then, you can access the API key using either one of the following paths in the Google Authenticator node configuration dialog.

In order to have access to data on Google BigQuery, the first step is to authenticate with Google, using the Google Authenticator node as described above. Then you can connect to Google BigQuery using the Google BigQuery Connector node.

However, due to license restrictions, you first need to install the latest version of the Google Big Query JDBC driver, which you can download here.

Once you have downloaded the driver, extract it into a directory and register it in your KNIME Analytics Platform as described here.

When registering the driver make sure to use bigquery_154 as ID and bigquery as the database type of the driver since it needs to match with the ID of the driver in the Community Hub Executor. So your driver registration dialog should look like this, where C:\KNIME\JDBC\BigQuery\SimbaJDBCDriverforGoogleBigQuery42_1.5.4.1008 is the directory that contains all the JAR files.

Refer to the KNIME Azure Integration User Guide for setting up the Azure integration with KNIME.

To access data from Azure, the first step when building your workflow is to use a Microsoft Authenticator node.

When configuring the node, select Azure Storage Shared Key as authentication type.

Enter the Storage Account Name and Shared/Access key and connect to Azure.

The credentials could be stored inside the node, which is not recommended, or passed to the node using the Credentials Configuration node. This will allow the team admin to pass the credentials while deploying the workflow, as shown in the below snapshot.

Once authenticated, use Azure Data Lake Storage Gen2 Connector or Azure Blob Storage Connector nodes and select the working directory from where you want to access the data.

Enter the file name in the respective file reader node and read the file.

Refer to the KNIME Snowflake Extension Guide for setting up Snowflake with KNIME.

To access data from Snowflake, the first step when building your workflow is to use a Snowflake Connector node.

The credentials could be stored inside the node, which is not recommended, or passed to the node using the Credentials Configuration node. This will allow the team admin to pass the credentials while deploying the workflow.