Service Deployment Creator

This Node Is Deprecated — This version of the node has been replaced with a new and improved version. The old version is kept for backwards-compatibility, but for all new workflows we suggest to use the version linked below.
Go to Suggested ReplacementService Deployment Creator

Due to changes in the Hub API, space versioning is no longer supported and has been replaced by file versioning. Please use the new "Service Deployment Creator" node instead.

Creates a new REST service deployment for the selected workflow. A REST Service deployment for workflows makes a workflow executable as a web service. The workflow should be already located in a Hub Space where it can be accessed via the Workflow location panel.

The user can select the deployment name, execution context, and space version if the selected workflow is valid.

Options

Settings

Workflow location
The path to the workflow you want to deploy. Use the "Browse..." button to select. The selected path can be set via a path flow variable or exported to a path flow variable.
Space version
Specifies which version of the workflow to deploy.
  • Use version of input connection: If chosen, the Space version selected in the Space Connector connected to the input port is used.
  • Always use latest version: If chosen, the workflow is deployed in the most recent Space version. A deployment can not be created with unversioned changes of a workflow. To deploy your changes, create a Space version first, e.g., using the Space Version Creator node or select the Version check box in the Space Connector node.
Deployment
A text field for selecting the deployment name. This is a mandatory field.

If a deployment with the given name already exists, the node can either

  • Fail: the execution will abort and no deployment will be created or updated.
  • Update: the existing deployment will be updated to serve the selected workflow.

Execution context
The execution context of the deployment defines for instance the installed extensions, available credentials, and the pool from which computation resources are used when the service is invoked.

Input Ports

Icon
The connection to the KNIME Hub Space that contains the workflow to deploy as a service. The service will become available on the selected KNIME Hub.

Output Ports

Icon
The service endpoint address and the deployment id as flow variables.

Popular Predecessors

Popular Successors

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.

Installation

To use this node in KNIME, install the extension KNIME Hub Additional Connectivity (Labs) from the below update site following our NodePit Product and Node Installation Guide:

v5.3

A zipped version of the software site can be downloaded here.

Plugin provider: KNIME AG, Zurich, Switzerland
Plugin version: 5.3.3.v202410162057
On NodePit since: 2024-07-09
Last update: 2024-11-15
Tags: Deprecated
KNIME versions: Since v4.7

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

Try NodePit Runner!