Adding a Data service task in a Dynamic Engine environment

Data service tasks are executable integration processes that contain a service published from Talend Studio.

Data services cannot be scheduled or added to plans. This type of service runs until it is explicitly undeployed by an operator.

Before you begin

You have installed a Dynamic Engine and its environment using Helm. For more information, see Helm deployment.
You must have the Editor (Author) permission on the space where the task is located to create or edit a task and manage its configuration.
You must have the Operator (Execute) permission on the space where the task is located to manage the run configuration.

Open the Management page.
Go to the Tasks tab.
Select the Dynamic Engine environment using the Environments filter at the top of the page.
Click Create new then Task.

In the Artifact step, select the Data service artifact type.
Select the artifact from the list.
Select the version of the artifact to be used in the task.
Select the space.
Enter a name.
By default, the task name is the name of the artifact from which it is created.

Tasks must have a unique name within a space.
Optional: Add a tag and a description for your task.
Click Continue to go to the next step.

These steps appear depending on the artifact configuration.

Optional: In the Parameters step, enter the value for the parameters of the data service.
In this step, when the Show order as in Studio toggle is disabled, you can only set the values to parameters you have defined with the parameter_ prefix in Talend Studio.

Information noteNote: Use \\ instead of \ when the value could be interpreted as a special character, for example, \t.
Optional: In the Advanced parameters step, enter the values for the parameters you have defined in Talend Studio without prefixes, and connection_ parameters that are not defined in the data service.
This section is available when the Show order as in Studio toggle is disabled. Otherwise, all parameters are in the Parameters step.

Use \\ instead of \ when the value could be interpreted as a special character, for example, \t.
Click Continue to go to the next step.

These steps appear depending on the artifact configuration.

Optional: In the Studio connections step, select the appropriate connection from the dropdown list.
You can also create a new connection based on the parameters already defined in the artifact.
Optional: In the Studio resources step, select the appropriate resource to use in the task.
Click Continue to go to the next step.

Your task is ready to be processed in the selected Dynamic Engine environment by the processing services set up in that environment.

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!