KNIME Business Hub User Guide

Download PDF

Introduction

KNIME Business Hub is a customer-managed KNIME Hub instance. Once you have a license for it and proceed with installation you will have access to Hub resources and will be able to customize specific features, as well as give access to these resources to your employees, organize them into Teams and give them the ability to manage specific resources.

Once you have access to a KNIME Businsess Hub instance available at your company, you can use KNIME Business Hub to perform a number of tasks such as:

collaborate with your colleagues,
test execution of workflows,
create and share data apps, schedules, and API services
keep track of changes with versioning.

This guide provides information on how to use KNIME Business Hub from a user perspective.

To install and administrate a KNIME Business Hub instance please refer instead to the following guides:

Connect to KNIME Business Hub

You can use a standard web browser to connect to your KNIME Business Hub instance, once you are provided with the address (URL) and your access credentials - username and password.

After providing them you will be able to access to the home page of the KNIME Hub.

Figure 1. A KNIME Business Hub instance home page

Now you can use the search functionality by typing your search terms into the search bar. The search will show results among all the Hub items that are available to you, based on your role and the items permissions.

Your user will be assigned to one or more teams so that you will be able to work on projects together with your colleagues.

Connect to KNIME Business Hub from KNIME Analytics Platform

To connect to KNIME Business Hub from KNIME Analytics Platform you have to first add its mount point to the KNIME Explorer.

KNIME Explorer

The KNIME Explorer, on the left-hand side of KNIME Analytics Platform, is the point of interaction with all the mount points available.

By default the KNIME Explorer displays:

The LOCAL mount point, which has access to the chosen workspace, a folder on your local system
The EXAMPLES Server where a number of example workflows made available by KNIME are stored
The KNIME Hub mount point where you can connect to your profile on the KNIME Community Hub and have access to your spaces

From here you can also access a KNIME Business Hub instance, by adding the Hub mount point.

For a detailed guide to the functionalities of the KNIME Explorer please refer to the KNIME Explorer section of the KNIME Workbench Guide.

Setup a mount point

Go to the KNIME Explorer window and click the preferences button in the toolbar as shown in Figure 2.

Figure 2. The Preferences button of the KNIME Explorer toolbar

In the preferences window click New… to add the new Hub mount point. In the Select New Content window, shown in Figure 3, select KNIME Hub and insert the Hub address.

Figure 3. Select New Content window to add a new KNIME Hub mount point

In the Mount ID field the name of the mount point will be automatically filled. Finally click OK and Apply and Close.

Now a new mount point is available in the KNIME Explorer, as shown in Figure 4.

Figure 4. A KNIME Hub mount point in the KNIME Explorer

Open the KNIME Hub mount point in the explorer and double-click Double-click to connect to KNIME Hub. You will be prompted to insert your access credentials.

Now you will see all the spaces that you have access to and you can upload workflows, components or data files from your local workspace to the KNIME Hub instance.

Here you can perform different types of operations on:

Spaces: you can create a new space, change the name or delete an existing space. When you create a space you will choose under which team you are part of to create the space, and if you want to create a public or a private space. You can also open the space page on KNIME Hub or copy the link to the space. To do this right-click the space from the KNIME Explorer and select the desired option from the context menu that opens.
Items:
- Upload items to your team KNIME Hub spaces, download, move, delete, or rename your items. More information about this functionality is provided in the next section.
- Open workflows as local copy or on KNIME Hub, or copy their URL. To do so right-click the desired item and select the options from the context menu.
- Create workflow groups, which are subfolders that you can use to organize your items in the space. To do so right-click the space and select New Workflow Group… from the context menu.

KNIME Hub view in KNIME Analytics Platform

A KNIME Hub view is also available in KNIME Analytics Platform. It is simply an integrated browser in the KNIME Analytics Platform workbench so you can use KNIME Hub in the panel as you would do in an external browser window. Enter your search query, hit enter, and then drag & drop nodes, components, workflows, or extensions to the workbench of KNIME Analytics Platform. If you have multiple KNIME Hub mount points (for example KNIME Community Hub and your KNIME Business Hub instance mount point) you can change the one you want to see by clicking the dropdown arrow icon on the top right corner of the KNIME Hub view and select the KNIME Hub instance from the dropdown menu.

Figure 5. KNIME Hub view in KNIME Analytics Platform

Search items in KNIME Hub

Insert a keyword in the search bar to search among the following items:

Nodes
Components
Workflows
Extensions

Press Enter to visualize the results.

You will see a list of all the search results in tiles, with:

An icon indicating if they are nodes, components, workflows or extensions
The title
Tags, when available
A preview of the description, when available
The owner icon for workflows, and extensions
The icon, for nodes and components

On top of the search results list, you can filter the results to list only nodes, components, workflows, and extensions, by clicking the respective tab, shown in Figure 6.

Figure 6. The KNIME Hub search results

Click on a search result to access the relative page.

Nodes

On the node page you will find:

The node function, name, and tags
The node owner
The node drag & drop element: You can drag & drop the element into the Workflow Editor of KNIME Analytics Platform to use the node directly to build a workflow or a component. See the Drag & drop section for more details on this feature.
The node likes and a link icon to copy the node short link.

For each node you can also find:

An Overview with a description of the node functionality
Node details where you can see information about Input and Output node ports, a description of the additional Options, and, when available, the Views that the node is able to produce
In the section Extension, you can see the node extension and the extension owner
Finally, in the section Related workflows & nodes you are provided with:
- Workflows that are available on KNIME Hub and that contain the node
- When available, the Outgoing nodes, that are the most popular nodes to follow the node when building a workflow.

Figure 7. A node page on KNIME Hub

Components

Since components really are KNIME nodes that you create which bundle functionality, have their own configuration dialog and their own composite views, also in the component page you will find similar information as for nodes.

The component name and last edit date
The component owner
The component drag & drop element: You can drag & drop the element into the Workflow Editor of KNIME Analytics Platform to use the component directly to build a workflow. See the Drag & drop section for more details on this feature.
The component likes, the count of downloads, and a link icon to copy the component short link.

For each component you can also find:

An Overview with a description of the component functionality, when provided by the component owner
Component details where you can see information about Input and Output component ports, a description of the additional Options, and, when available, the Views that the component is able to produce
In the section Used extensions & nodes you can see the component extensions and nodes.
Finally, in the section Related workflows you are provided with Workflows that are available on KNIME Hub and that contain the component.

Workflows

A workflow page typically has multiple useful information about the workflow such as:

The workflow title, tags and last edit date
The space owner where the workflow is contained and, if different from the space owner, the workflow developer
The workflow drag & drop element: You can drag & drop the element into a selected mount point in the KNIME Explorer of KNIME Analytics Platform. This will prompt an Import window which allows you to import the workflow into the mount point. See the Drag & drop section for more details on this feature.
The workflow likes, the count of downloads, and a link icon to copy the workflow short link.

For each workflow you can also find:

An Overview with a description of the workflow when provided by the workflow developer
External resources links to external resources such as KNIME blog posts, KNIME documentation, or any other interesting link that the workflow developer might want to provide
In the section Used extensions & nodes you can see the you can see the workflow extensions and nodes, and the KNIME Analytics Platform that has been used to create the workflow

Extensions

Extensions are collection of nodes that provide additional functionality such as access to and processing of complex data types, the use of advanced algorithms, as well as the use of scripting nodes, and so on.

KNIME Extensions are developed and maintained by KNIME, allowing you to access open source projects and add their functionality to your KNIME workflows. Community Extensions instead include functionality specific to various industries and domains. Some of these community extensions are classified as Trusted Community Extensions, which have been tested for backward compatibility and compliance with the KNIME usage model and quality standards, and Experimental Community Extensions, which come directly from the labs of our community developers. Finally, also Partner Extensions are available which provide additional capabilities offered and maintained by our partners.

All these Extensions are available on KNIME Hub.

An extension page typically has multiple useful information about the extension such as:

The extension name and owner, version of the extension
The extension drag & drop element: You can drag & drop the element into the Workflow Editor of KNIME Analytics Platform. If the extension is not already installed this will prompt an Install Extension window which allows you to install the extension. See the Drag & drop section for more details on this feature.
The extension likes, and a link icon to copy the extension short link.

For each extension you can also find:

An Overview with a description of the extension when provided
Included nodes with a list of all the nodes that are part of the extension and that will be available once the extension is installed
In the section Related workflows, you are provided with Workflows that are available on KNIME Hub and that contain the nodes that are part of the extension
Finally, in the section Legal & update site, you can have legal information about the copyright and the update site information, with the type of the extension, version number, and the link to the update site.

Drag & drop

You can drag & drop nodes, components, extensions, and workflows from KNIME Hub to import them into KNIME Analytics Platform and use them right away to build your own workflow, install KNIME Extensions, and execute uploaded workflow into your local installation.

Node and components: You can drag & drop a node or a component from KNIME Hub into your Workflow Editor in KNIME Analytics Platform. In case the node is part of an Extension that is not yet installed into your local installation of KNIME Analytics Platform or in case nodes that are part of extensions that are not yet installed are contained in the component, you will be asked if you want KNIME Analytics Platform to search and install the missing extension(s), as shown in Figure 8.

Figure 8. Drag & drop a node from KNIME Hub to KNIME Analytics Platform and install missing extension
Extensions: You can drag & drop a specific extension into the Workflow Editor. KNIME Analytics Platform will search and install it. In order to be able to install the extension the extension’s update site that is indicated at the end of the extension page in the section Legal & update site must be activated in KNIME Analytics Platform.

Teams

A team is a group of users on KNIME Hub that work together on shared projects. Specific Hub resources can be owned by a team (e.g. spaces and the contained workflows, files, or components) so that the team members will have access to these resources.

The team can own public or private spaces. For more details see the section Team owned spaces.

The items that are stored in a team’s public space will be accessible by everyone and be presented as search results when searching on KNIME Hub. Only team members will have upload rights to the public spaces of the team. Only the team members instead have read access to the items that are stored in a team’s private space. This will then allow KNIME Hub users that are part of a team to collaborate privately on a project.

Create a team

Teams are firstly created by the KNIME Hub Global Administrator. The global admin will assign a user the role of team admin as well allocate resources to that team. The team admin will be able to start adding team members and create execution contexts that can be used by the team.

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

Administrator. A team administrator can:
Member. A team member can:
- View the team page, with members list and spaces
- Create, modify, and delete public and private spaces
- Upload/download items to/from public and private spaces
- Delete items from public and private spaces

The team creator is automatically assigned 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.

Team owned spaces

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

Team owned public spaces: The items that are stored in a team’s public space will be accessible by everyone and be presented as search results when searching on KNIME Hub. Only team members will have upload rights to the public spaces of the team.
Team owned private spaces: Only the team members instead have read access to the items that are stored in a team’s private space. This will then allow KNIME Hub users that are part of a team to collaborate privately on a project.

You can create a new space by going to the team’s profile. To do so click your profile icon on the top right corner of KNIME Hub. 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.

You can also 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 three vertical dots as shown in the image below.

Figure 9. Change visibility or delete an existing team owned space

Manage space access

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

Figure 10. Open the Manage space access side panel

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

Figure 11. Manage the access to a space

Manage team members

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

Figure 12. Select a team to go to the team’s profile page

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.

Figure 13. The team’s profile page

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

Figure 14. Manage team members

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

From here a team admin can change the role 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.

Figure 15. Manage team members roles

Then click Save changes button to apply your changes.

Add members to a team

To add a new member enter the user name of the users that you want to add to the team in the corresponding field in the Manage Team Members panel then click Save changes button to apply your changes.

In case you added more users than allowed by your license you will be notified with a message. Please remove the exceeding users or purchase more users.

Delete members from a team

To delete a member go to the Manage Team Members panel and click the bin icon for the user you want to delete. Then click the Save changes button to apply your changes.

Upload items to KNIME Hub

Once you have added the KNIME Business Hub mount point and you are connected to your KNIME Hub account from KNIME Analytics Platform you can upload the desired items to your KNIME Hub spaces.

You can upload workflows, components or files to any of your team owned spaces by:

Dragging & dropping the item from your local mount point to the desired location in the KNIME Hub mount point, or by
Right-clicking the item from KNIME Explorer and selecting Upload to Server or Hub from the context menu. A window will open where you will be able to select the location where you want to upload your workflow or component.

Figure 16. Upload a local item to your KNIME Hub mount point

Please notice that if the items are uploaded to a public space they will be available to everyone, hence be very careful with the data and information (e.g. credentials) you share.

Move items within KNIME Hub

You can move items that you uploaded to KNIME Hub to a new location within the space that contains the item or to a different space that you have access to. To do this you need to be connected to the KNIME Hub mount point on KNIME Analytics Platform. You can then move the items within KNIME Hub just by dragging the item in the KNIME Explorer.

Delete items from KNIME Hub

You can also delete items that you uploaded to KNIME Hub.

To do so you can:

Connect to KNIME Hub mount point on KNIME Analytics Platform. Right-click the item you want to delete and select Delete… from the context menu
From KNIME Hub, sign in with your account and go to the item you want to delete. Click the three dots on the top right of the page and select Delete workflow.

Figure 17. Delete a workflow from KNIME Hub

Download items from KNIME Hub

You can of course also download items from KNIME Hub to use them in your local KNIME Analytics Platform installation. You can do this either from the KNIME Explorer by drag&drop or copy paste the workflow from the KNIME Hub mount point to your LOCAL mount point or you can also download the workflow from KNIME Hub in the browser. To do so go to the specific workflow or component you want to download on KNIME Hub and click the download button .

The file will be saved on your local machine and then you can import it to your KNIME Analytics Platform, by going to File → Import KNIME Workflow… and selecting the file you want to import.

Versioning

When uploading items to a space on KNIME Hub you will be able to keep track of the changes of the space.

You can also create versions of the space so that you can go back to a specific saved version at any point in time in the future to download the content of the space as in a specific version.

Once a version of the space is created new changes to the space will show up as unversioned changes.

Create a version of a space

Go to the space you want to create a version of and click Space history.

Figure 18. Versioning of a space

A panel on the right opens where you can see all the versions already created and all the unversioned changes of the space since the last version was created.

Click Create version to create a new version and give the version a name.

Navigate and download a space version

In the Space history panel click the three dots for the version you want to navigate to and click Show version. You will be redirected to the space in that specific version.

Figure 19. Show a version of a space

Now you can download the whole space or a subset of it.

On KNIME Business Hub the space is the entity that is versioning but is also possible to go back to a specific version of a workflow that was part of the space history. When navigating back to that workflow’s version the whole space’s version will be shown.

Go to a specific workflow and click Workflow history to see the space’s versions that have been created and that contain the workflow.

Figure 20. Show the versions of a workflow

Delete a space version

In the History panel click the three dots for the version you want to navigate to and click Delete. Only Team administrators can delete a space version.

Figure 21. Delete a version of a space

Execution of workflows on KNIME Hub

You can execute workflows on KNIME Hub. In order to do so the team you are a member of needs to have an execution context assigned to.

A team can own multiple execution contexts which are dedicated execution resources with configured execution settings.

Execution contexts

An execution context provides dedicated execution resources with configured execution settings for the execution and deployment of workflows on KNIME Hub.

They operate using a selected custom executor image, which defines custom hardware and KNIME Analytics Platform configuration for the deployments.

Execution contexts are owned and managed by the teams.

A default Execution Context can be assigned to a space. It is possible to create as many execution contexts as necessary. They can be used for specific deployments, for example in a development, testing, production configuration.

Execution contexts can be created by the team admin once the Docker image of the executor is available. The latter is maintained by the global Hub admin.

Create a new execution context

The team admin can create a new execution context.

To do so go to the team profile page and click Settings in the menu on the left.

Here you will see all the available Execution resources of your team, you can see how many vCores are available and in use for each execution context, the version of the executor, its memory usage and CPU load.

To create a new execution context for your team click the yellow + button on the right.

Figure 22. An overview of the execution resources available to your team

In the side panel that opens you can define your execution context.

Figure 23. Create a new execution context

Here you can specify:

Name: is the name of the execution context

Docker image: is the name of the Docker image of the executor that you can obtain from your KNIME Hub Global Administrator.

Public Docker executor images are made available by KNIME which correspond to the full builds of KNIME Executor versions 4.7.x.

The currently available executor images have the following docker image name:

registry.hub.knime.com/knime/knime-full:r-4.7.0 registry.hub.knime.com/knime/knime-full:r-4.7.1-119

Blacklisted nodes: is a list of nodes that should be blocked by the Executor. You need to provide the full name of the node factory. You can get the factory name from the Hub itself by looking for the node. The last part of the URL is the node factory name. For example the Java Snippet node can be found at the following URL: https://hub.knime.com/knime/extensions/org.knime.features.javasnippet/latest/org.knime.base.node.jsnippet.JavaSnippetNodeFactory and org.knime.base.node.jsnippet.JavaSnippetNodeFactory i its factory name. Another way to determine the factory names of the nodes you want to block is to create a workflow with all nodes that should be blacklisted. After saving the workflow you are able to access the settings.xml of each node under <knime-workspace>/<workflow>/<node>/settings.xml. The factory name can be found in the entry with key "factory".
Number of executors: is the number of executors that the execution context has assigned
Number of vCores per executor: is the number of vCPUs per executor
RAM per executor (GB): is the amount of RAM per executor in GB

Edit an existing execution context

As a team admin you can also edit an existing execution context.

From the Execution resources overview page you can click the three dots of the execution context you want to modify and select Edit from the menu that opens

Figure 24. Edit an existing execution context

You can change the parameters and configurations in the left side panel that opens.

Delete an execution context

As a team administrator you can delete an existing execution context.

This is right now available only via REST API call. You first have to create an application password and then use the credentials in the basic authentication when performing the REST API calls. To create an application password follow the instructions in the Application passwords section.

First, obtain the <team_ID of the team you are administrator of by the following GET request:

GET api.<base-url/accounts/identity

You will find the <team_ID> in the body response under teams:

...
    "teams": [
        {
            "id": "account:team:<team_ID>",
            "name": "<team_name>",
            ...
        }
    ]
...

Then you will need to get the execution context ID. This can be obtained using the following GET request to the endpoint:
```
GET api.<base-url>/execution-contexts/account:team:<team_ID>
```
From the response select the execution context that you want to delete and copy the execution context under "id".
Then you will need to first disable the execution context you want to delete. First, delete the jobs associated to the execution context then proceed with disabling it. To disable an execution context you can use the following PUT call to the endpoint:
```
PUT api.<base-url>/execution-contexts/<EC_ID>
```
Where <EC_ID> is the execution context ID from step 1.

You will need to use the following body:
```
{
  "isDisabled": true
}
```
Then you can delete the execution context with a DELETE call to the endpoint:
```
DELETE api.<base-url>/execution-contexts/<EC_ID>
```

In case you get a 400 code response you need to delete the deployments attached to the execution context and disable it as indicated at step 2.

Ad hoc execution

When a team owned space is provided with an execution context it is possible to execute the workflows that are uploaded to that space.

If you want to have a one time execution of a workflow you uploaded to a space, for example to test it, you can go to the workflow page on KNIME Hub and click Run.

Figure 25. Ad hoc execution of a workflow on KNIME Hub

A side panel opens where you can:

If multiple execution contexts for the current space are available, select the execution context you want to use - otherwise the default execution context associated to that space will be used
Enable workflow actions: You can choose if a notification via e-mail will be sent On failure or On success. You can also Add more actions and notify multiple e-mails on different conditions.

Figure 26. Ad hoc execution configuration panel

Then click Run and the workflow will be executed.

Please notice that an ad hoc execution will always be performed on the current version of the workflow from which the Run is initiated. This means that if you run a workflow from a state that is not part of any version of the space the execution will be performed on the latest state. To run an ad hoc execution of a workflow from a different space version go to the desired space version and click Run. The execution will be performed on the workflow state that is save in that specific space version.

Figure 27. Ad hoc execution of a workflow from a specific space version

Finally, you can see an overview of all the ad hoc execution jobs that have been performed on a specific workflow by selecting Ad hoc executions from the menu on the right in the workflow page.

Data Apps, schedules and API services

After a workflow is uploaded to KNIME Hub different type of deployments can be created.

You can create:

Data Apps: Data Apps provide a user interface to perform scalable and shareable data operations, such as visualization, data import, export, and preview.
Schedules: A workflow can be scheduled to run at specific times and perform specific actions based on the result of each execution.
API services: A workflow can be deployed as a REST endpoint and therefore called by external services.

To create a new deployment of a workflow that you uploaded to one of your team’s spaces you first need to have created at least one version of the space where the workflow is saved. After you create a version of the space go to the workflow page and click Deploy.

Figure 28. Create a new deployment for a workflow on KNIME Hub

In the menu that opens you can select which kind of deployment you want to create.

Data Apps

Select Create data app if you want to create a data app to interact with the workflow via a user interface.

In the right panel that opens you will be able to choose a Deployment name, select the space version you want to deploy, select the execution context you want to use, and check Enable workflow actions if you want to enable sending an e-mail upon success or failure of the execution of the deployment you will create.

Figure 29. Create a data app deployment for a workflow on KNIME Hub

Under Advanced settings click Set to change the advanced settings of the deployment. Here you can configure the options regarding:

Job lifecycle: such as deciding when to discard a job, the maximum time a job will stay in memory, the job life time, or the options for timeout
Additional settings such as report timeouts, CPU and RAM requirements and so on

Notice that you can get additional information on the different fields by hovering over it with the cursor.

The values in the fields related to time need the format:

PT, which stands for Period of Time
the amount of time, made of a number and a letter D, H, M and S for days, hours, minutes and seconds.

For example, PT1H means a period of time of 1 hour, PT168H means a period of time of 168 hours (which is equivalent of 7 days).

Schedule

Select Create schedule if you want to create a scheduled execution that will run your workflow automatically at selected times.

In the right panel that opens you will be able to choose a Deployment name, space version you want to deploy, select the execution context you want to use, define when the workflow should be executed, and check Enable workflow actions if you want to enable sending an e-mail upon success of failure of the execution of the deployment you will create.

Figure 30. Create a schedule deployment for a workflow on KNIME Hub

In the Schedule options section you can set up date and time of the Initial execution. When selecting the check box Repeat every you can also decide when the execution will be repeated, such as every minute, or every 2 hours and so on. You can also define if and when the schedule will end, and you can decide to Skip execution if previous job is still running.

Figure 31. Define the options of the scheduling

Under Advanced settings you can set the number of execution retries and you can choose to reset the workflow before it is executed. Finally you can click Set to change the advanced settings of the deployment.

Here you can configure the options regarding:

Job lifecycle: such as deciding when to discard a job, the maximum time a job will stay in memory, the job life time, or the options for timeout
Additional settings such as report timeouts, CPU and RAM requirements and so on

Notice that you can get additional information on the different fields by hovering over it with the cursor.

The values in the fields related to time need the format:

PT, which stands for Period of Time
the amount of time, made of a number and a letter D, H, M and S for days, hours, minutes and seconds.

For example, PT1H means a period of time of 1 hour, PT168H means a period of time of 168 hours (which is equivalent of 7 days).

Service

Select Create service if you want to create a service to use the workflow as an API endpoint.

Figure 32. Create a service deployment for a workflow on KNIME Hub

Under Advanced settings click Set to change the advanced settings of the deployment. Here you can configure the options regarding:

Job lifecycle: such as deciding when to discard a job, the maximum time a job will stay in memory, the job life time, or the options for timeout
Additional settings such as report timeouts, CPU and RAM requirements and so on

Notice that you can get additional information on the different fields by hovering over it with the cursor.

The values in the fields related to time need the format:

PT, which stands for Period of Time
the amount of time, made of a number and a letter D, H, M and S for days, hours, minutes and seconds.

For example, PT1H means a period of time of 1 hour, PT168H means a period of time of 168 hours (which is equivalent of 7 days).

Application passwords

Application passwords can be used to provide authentication when using the KNIME Hub REST API, for example when executing deployed REST services. To create a new application password you can go to your profile page and select Settings → Application passwords from the menu on the left.

Click + Create application password and a side panel will show.

Here you can give a name in order to keep track of the application password purpose. Then click Apply. The ID and the password will be shown only once. You can copy them and use it as username and password in the base authentication when you want to execute a deployed REST service.

Figure 33. Application passwords

From this page you can also click the three dots button and click Delete from the menu that opens, in order to delete a specific application password.

Managing deployments

Select Deployments from the menu on the right in the workflow page to see a list of the deployments that have been created for a specific workflow.

Figure 34. A list of all the deployments created for a specific workflow

To see all the deployments that were created under a specific team go to that team page and select Deployments from the menu on the left.

Figure 35. A list of all the deployments created by a team

By clicking the three points menu at the end of the corresponding deployment row you can perform the following actions:

Run/Open
Manage access
Discard

Run a Data App deployment

Once you have create a Data App deployment you can go to see the list of Deployments for the specific workflow, click the three dots on the row corresponding to the deployment you want to execute, and click Run/Open.

Figure 36. Execute a deployed data app

Change status of a schedule deployment

Also from the list of deployments available for a workflow or for the team, you can activate or deactivate a schedule. To do so click the toggle in the Status column.

Open a service deployment

When a service deployment is created a REST API endpoint is created. By selecting Run/Open the definition of the endpoint opens.

Manage access to a deployment

You can select Manage access from the menu that opens when clicking on the three dots. This opens a side panel where you can add the name of the user you want to share the deployment with.

It is also possible to share the deployment with users that are not members of your team. They will be able to see the deployments shared with them in their profile in the Shared with me section. This can also be accessed from the Business portal.

Discard a deployment

You can discard a deployment from the deployments list by clicking the three dots in the corresponding row and selecting Discard from the menu.

Figure 37. Discard a created deployment

Business portal

You can access the business portal by going to the address:

https://apps.<base-url>

where <base-url> is the usual address of the KNIME Business Hub instance.

This page is available to every registered user. Consumers, for example, can access to this page to see all the data apps that have been shared with them, execute them at any time, interact with the workflow via a user interface, without the need to build a workflow or even know what happens under the hood.

To share a deployment with someone follow the instructions in the Manage access to a deployment section.

Known issues and compatibility

Please be aware that the compatibility of the following nodes and functionalities with KNIME Business Hub is still under development and it will full compatibility will be available soon.

File Chooser Widget node
Molecule Sketcher Widget node does not support custom widgets such as MarvinJS
Setting job lifecycle defaults for execution contexts is only possible right now via REST API