Deploying Route or data service tasks on a Remote Engine or cluster - Cloud

By scheduling its run on a Remote Engine or cluster, your Route or data service task will be executed in an on-premises secure runtime.

1. Open the Management page.
2. Go to the Tasks tab.
3. Select the task to deploy on a Remote Engine or cluster from the list.
   You can use the faceted search at the top of the page to filter the list for example by selecting the environment, workspace and task type.
   The task details page opens.
4. Click EDIT in the top-right corner of the page.
   The Edit task wizard opens.
5. Optional: Modify the task configuration if needed.
6. In the Engine section, select the execution runtime on which to deploy your task from the Engine drop-down list.

   Option	Description
   Remote Engine	Data services and Routes can only be executed on Remote Engines that are compatible with the used Studio version. For the compatibility matrix, see Artifact compatibility for Cloud Engine and Talend Remote Engine. Depending on the type of the task, the selected Remote Engine must have the corresponding run profile set either when the engine is created, or later in the Edit engine wizard accessible via the Engines > <RemoteEngineName> > path.
   Remote Engine cluster	All Remote Engines assigned to the cluster must be of the same version (v2.8.4 or above). Depending on the type of the task, the Remote Engines in the cluster must have the appropriate Microservice or Talend Runtime (OSGi) run profile set. The engines must also be compatible with the used artifact's version.

7. Optional: When deploying a microservice on a Remote Engine or cluster, you can select a run profile.

   You can choose a previously created run profile for the selected Remote Engine or cluster to set the JVM parameters for the task run.

   This feature is supported from Remote Engine 2.12.4 onwards.

8. In the Metric Path field, enter the metric path to be used at deployment time to retrieve metric data, for example, the number of requests at runtime.
   The default value is the artifact name, and we recommend to keep this value to see the metric data displayed on the Task Details page. If this field is empty, no metric information will be displayed on the page.

   Tip: You can add the project name to the artifact name, if artifacts with the same name exist in more than one project and are configured to run on the same Talend Remote Engine/Talend Runtime.
9. Optional: When deploying a microservice on a Remote Engine or cluster, you can run your task as another user by entering their username in the Run as impersonated user field.
   This feature is supported only if the Remote Engine is installed on Unix or similar environments.
   This feature is supported from Remote Engine 2.12.4 onwards.
   For more information about user impersonation, see the Talend Remote Engine User Guide.
10. When deploying a microservice, set the port assignment.

    Option	Description
    Automatic	The port on which the microservice instance(s) will run is defined by the system.
    Custom	You can set a static port number on which to run all instances of the microservice, making external load balancing easier.

11. If you have chosen to deploy the task on a cluster, select the deployment strategy.

    Option	Description
    Parallel	Deploy the tasks simultaneously to all the Remote Engines of the cluster.
    Rolling	Deploy the tasks one by one to the Remote Engines of the cluster.

12. Click Save draft.
    You can deploy the task from the Task Details page by clicking Deploy.