Skip to main content Skip to complementary content
Qlik Resources
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal
Loading SearchUnify's search If you need assistance with your product, please contact Qlik Support.
Qlik Customer Portal

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

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.

Before you begin

  • You must select the correct microservice or OSGi run profile for the Remote Engine in Talend Management Console when creating or editing the engine.

Procedure

  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. Optional: Click Edit in the top-right corner of the page to modify the task configuration.
    For more information, see Managing Routes and data services.
  5. Click Deploy in the top right corner to execute your task.
  6. To deploy the task only on a single Remote Engine in the cluster, click Deploy next to the deployment instance.

    When a task is deployed on the cluster for the first time, the deployment strategy always automatically switches to the Parallel strategy, regardless of your chosen strategy. For further information about different deployment strategies, see Deployment strategy.

    The Deploy and the Undeploy buttons become available only after first general parallel deployment in cluster.

Results

Your task deployment has started. You can monitor its status on the task details or Operations pages. To see all the deployment details and metrics, expand the current deployment.
Troubleshooting: If the Deploy button is grayed out, make sure that:
  • The Remote Engine is paired and available.
  • All Remote Engines in the cluster belong to the same version (v2.8.4 or above).
  • All Remote Engines in the cluster are paired and available.
Information noteTip: An engine status becomes unavailable if Talend Management Console does not receive engine's container statistics update, even when it is still receiving heartbeat signals from the engine. These updates confirm that the HTTPS connection to the message queue (AMQ) is active, enabling the engine to process task run lifecycle events.
For more information on engine health signals (heartbeat and container statistics update), see:

Did this page help you?

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

Leave your feedback here