Deployments on KNIME Business Hub Guide

The Weather Data Dashboard is a data application designed to provide users with insightful visualizations and analysis of synthetic weather data.

This user-friendly app generates synthetic weather data for various parameters, including Date and time, Sunlight Duration (minutes/hour), Rain Probability, Relative Humidity, and Temperature (°C). It presents this data in an intuitive dashboard featuring dynamic graphs (Line Plot and Bar Chart), a table view, and a Date Filter widget.

Upon successful execution of the installation workflow, you will find the Weather Data App conveniently located within the Data App folder of the newly created space. After successfully creating the version, proceed by clicking the "Deploy" button, which becomes enabled once there is at least one version of the item.

A panel will appear, facilitating the configuration of essential deployment details. Here, you can specify information, such as selecting a deployment name and description, choosing an execution context, and categorizing the data app on the DataApps Portal.

Once the Data App has been successfully created, you can access it via the "Deployments" page within your team’s workspace. To share the Data App with other users, follow these steps:

Upon completing these actions, the added users will gain visibility and access to the Data App within the Data App Portal, organized under the assigned category. For more comprehensive details regarding the Data Apps Portal, please refer to the provided documentation.

Now that the Data App has been successfully deployed, you have two convenient methods for execution:

This workflow details the creation of a captivating and interactive game data app that engages users in a flag-guessing challenge.

In this app, users are presented with flags from different nations, and their task is to identify the nation to which each flag belongs correctly.

After a series of flag guessing rounds, a score is computed, and users are offered the opportunity to submit their scores. This engaging and educational app combines entertainment with data collection.

Furthermore, this workflow includes various tips and tricks that aid in the creation of high-quality data apps that deliver an exceptional user experience.

To create a data app deployment for this workflow, you need to follow the steps outlined in the previous section, Creating a Data App Deployment.

The workflow is an automated solution designed to generate synthetic weather data on a weekly basis and store it in a designated folder named "Data."

It generates synthetic weather data for various parameters, including Date and time, Sunlight Duration (minutes/hour), Rain Probability, Relative Humidity, and Temperature (°C).

By scheduling this workflow, you ensure a steady supply of weather data without manual intervention.

Data is saved in .csv format after each execution.

By using a schedule, users can specify a time for workflows to run automatically, eliminating the need for manual intervention.

We offer various options for specifying when the workflow will run. For instance, you can configure the workflow to run every seven days from the current date and continue running for a year.

Clicking on "Set Schedule Details" provides additional capabilities, allowing you to include or exclude specific months or days, as well as specifying precise execution timeframes.

You can always edit the schedule by accessing it on the "Deployment" page.

To achieve the goal of integrating the service into other workflows, data apps, or clients, we will showcase the use of two workflows in this demonstration.

The first workflow, named "Prime Number," will be deployed as a service. Simultaneously, the "Prime Number Data App" will invoke this workflow during its execution to retrieve information about the prompted prime number.

To initiate the service deployment process, click the "Deploy" button and select "Create Service."

The configuration process only necessitates a few specified parameters, such as the deployment name, execution context, and version selection if multiple versions are available.

After the deployment has been created, you can open it and read the API specifications for invoking the service on the Deployments page within the Hub team.

It’s crucial to remember that the deployment ID is key information for making REST API calls to the specific deployment.

It is important to configure access permissions for the service; otherwise, users may be unable to access it. To accomplish this, you can click on "Manage access" and add all the users who require access to the service. Alternatively, you can choose to permit access for any signed-in user. This is the same procedure to grant access to a data app.

Once the Service deployment has been created, you can proceed to run the Prime Number Data App, which can also be deployed. This data app requires the Deployment ID as input to fetch the service for invocation. Once the Service has been successfully connected to the data app, you can proceed to the next page.

This straightforward data app demonstrates how the user interface collects input, sends it to the service, and receives the determination of whether the number is prime or not in response.

This workflow outlines the process of using the Integrated Deployment extension to create a brand-new production workflow that can be deployed as a service.

The workflow retrieves data from the data area and conducts essential preprocessing tasks. Thanks to the Integrated Deployment Extension, these preprocessing steps are encapsulated and replicated within a production workflow, making them readily available for external use when deployed as a REST endpoint. The resulting production workflow is saved within the "Production Folder (Integrated Deployment)" which is located at the same level as the original workflow.

The goal is to create a deployable service that can effectively process a data table when it’s invoked correctly.

To start, execute the "ETL and Integrated Deployment" workflow. You will observe that the Workflow Writer node will save the relevant portion of this workflow in the Production Folder.

The Workflow Writer node is configured to use the Workflow Service nodes as input and output.

If you want to process a new table using this ETL workflow, once you’ve created a Service Deployment for the "Data_Transformation_wf," the most straightforward approach is to utilize the Call Workflow Service node along with the KNIME Hub Authenticator node.

Open the "Send a data table to the Service Deployment" workflow directly on the Hub, then browse the available deployments and select the one that’s connected to the ETL workflow generated using Integrated Deployment.

After making your selection, you should click the "Adjust node ports" button to create the input port that sends the data.

This KNIME workflow is designed to automate the creation of item versions when a file is added, modified, or updated to a designated space on KNIME Business Hub.

It leverages the power of KNIME’s automation capabilities to streamline the process of managing and versioning files within a shared space. The workflow is made to be deployed on KNIME Business Hub and is triggered whenever a new file is uploaded to the space where the workflow is stored.

The container Input (Repository Event) conveys information about the new file to the workflow. These parameters are then utilized to automatically generate a version of the file by means of the Version Creator node.

To initiate the service deployment process, click the "Deploy" button and select "Create Trigger."

In addition to the standard deployment parameters like name and execution context, the critical aspect here is to specify the type of event that serves as the trigger for the workflow. These events can encompass actions such as file addition, deletion, update, or the creation of a new version for any data file. Furthermore, users have the option to specify a sub-path within the chosen target space.

With these settings in place, a version will be automatically created each time there is a modification or a new upload within the KNIME Business Hub Deployment Examples space.