Skip to main content Skip to complementary content

Deploying multiple Remote Engines

Sometimes you may need to deploy and run more than one Remote Engine instance on a single server for short term development and testing.

A Remote Engine needs to access Job task dependencies such as the Job artifacts, the logs and the working folders stored in a folder called TalendJobServersFiles. Ensure that each Remote Engine instance has its separate TalendJobServersFiles folder, because sharing this folder across those instances could lead to random Job execution failures and cleaning issues.

About this task

Talend provides Karaf configuration scripts that automate the deployment of maximum two Remote Engine instances on the same server with different set of non-conflicting ports and parameters. These scripts are executed within the Talend Remote Engine instances and thus supported by all platforms compatible with Talend Remote Engines.

Procedure

  1. Stop your existing Remote Engine and its service if they are running.
  2. Create your second Remote Engine in Talend Management Console.
  3. Download and unzip or install the second instance of the Remote Engine into a separate folder.
    The installer starts the service automatically. You have to stop it manually after the installation process is over.
  4. Navigate to the bin folder of the second Remote Engine's installation directory and execute the karaf.bat file.
  5. In the Karaf console, run the source scripts/configureC1.sh script.
    Screenshot of the script to run in Karaf console.
  6. Shut down Karaf.
  7. Pair the second Remote Engine with your Talend Cloud account.
  8. Start both Remote Engines from their respective installation folders by running the trun.bat file.

Results

You are able to execute Tasks on both Remote Engines without conflicts.

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