Deploying Route or Data Service tasks on a Talend Remote Engine or cluster
By scheduling its run on a Talend 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 Talend Remote Engine in Talend Management Console when creating or editing the engine.
Information noteTip: If you are deploying tasks built with Java 21 compliance level on Talend Remote Engine,
ensure Java 21 is configured for artifact execution. For configuration details, see
Configuring Java versions to run Jobs or Microservices.
Procedure
Results
Troubleshooting: If the Deploy
button is grayed out, make sure that:
- The Talend Remote Engine is paired and available.
- All Talend Remote Engines in the cluster belong to the same version (v2.8.4 or above).
- All Talend 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:
- For Linux: Monitoring Remote Engine health
- For Windows: Monitoring Remote Engine health