Skip to main content Skip to complementary content

Installing the Remote Engine automatically

Use the installer to automatically install Talend Remote Engine.

Before you begin

If Security-Enhanced Linux (SELinux) is activated before you run the installer, it might prevent the installation of some applications. You should temporarily deactivate SELinux by running the following command: setenforce Permissive. SELinux will reactivate automatically after the next reboot.

About this task

The installer provides a default wizard to guide you through the installation process. However, in some scenarios, such as running the installer with SSH, the wizard is not available, and the console is used instead. Regardless of the method used, the same configuration setup is prompted.

Procedure

  1. Run the installer file as root user.
    Information noteTroubleshooting: If you do not run the Remote Engine installer as a root user on Ubuntu 14.04, you may get the following error:
    Unable to start JVM: No such file or directory
  2. Select the region of your Talend Cloud account.
    The region is reflected in your Talend Cloud URL following this pattern: <region>.cloud.talend.com. For example, if your URL is http://us.cloud.talend.com, you must select AWS - USA East as your region.
    More information in Accessing Talend Cloud applications with a list of the URLs to use for each data center.
  3. Paste the Remote Engine Key generated in Talend Management Console when you create the Remote Engine into the Preauthorized key box.
  4. Optional: Select the Use HTTP proxy checkbox and enter the server and port details.
  5. Optional: Select the Use Proxy Authentication checkbox and enter the user credentials.
  6. Optional: For Talend Remote Engine v2.13 and onwards, select the Java for Job/Microservice execution (Java 8/11/17) checkbox and in the JAVA_HOME field, enter the path to the home folder of the Java instance to be used for executions, for example, C:\Java\jdk-20.
    • When you select this option, the engine uses the specified Java instance to run Jobs or Microservices. However, note that this configuration does not impact the requirements for the startup of the engine, for which Java 17 is still required.
    • If you leave this checkbox clear, the default Java 17 version is used for executions.

    Whether you specify a Java instance or leave the default one, you can always specify a different Java version after the installation. To do this, follow these steps.

  7. Optional: Select the Install as a system service checkbox to make Remote Engine a service of your system.

    If you skip this option, you can still install your engine as a system service later by following Setting up Remote Engine service manually.

  8. Optional: When installing the engine as a system service, define a username and a group name for it, or skip this step to use the default ones: talenduser and talendgroup.
    This talenduser is the default username to use Remote Engine, whether or not you install it as a system service.
  9. Finish the installation by following the steps in the wizard.

Results

As mentioned above, during the installation of the Remote Engine, the talenduser username is created. You must start and stop the engine with that user.

Note that in the end of the installation, your engine is automatically paired with Talend Management Console.

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