Skip to main content Skip to complementary content

Installing the Remote Engine automatically

Use the installer to automatically install and configure 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. Temporarily deactivate SELinux by running the following command: setenforce Permissive.

SELinux will automatically reactivate after the next reboot.

About this task

The installer provides a default wizard to guide you through the installation process. However, in scenarios where the wizard is not available, such as when running the installer with SSH, the console is used instead. Both methods prompt you for the same configuration settings.

Procedure

  1. Run the installer file as the 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 us.cloud.talend.com, 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.

    Example

    Wizard step showing fields or options for configuring the Remote Engine pairing key, Java instance, and system service installation
  4. 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.

  5. 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.
  6. Optional: For Talend Remote Engine v2.13.9 and onwards, select the Separate Java for non Java 17 compliant job/microservices (Java 8/11) checkbox to configure a separate Java instance to execute artifacts requiring Java 8 or 11. Then in the JAVA_HOME field, enter the path to that Java instance, for example, C:\Java\jdk-11.
    The installer automatically activates the JVM adaptive mode for the engine by setting the org.talend.execution.JAVA_17_PATH property with the default Java instance for engine startup.
    • When the checkbox is selected, the installer additionally sets org.talend.execution.JAVA_8_PATH or org.talend.execution.JAVA_11_PATH in the <RE_installation>/etc/system.properties file, depending on the Java instance specified in the JAVA_HOME field.
    • If you leave this checkbox clear, the default Java 17 version is always used for executions.

    You can always change the configuration after the installation by modifying the <RE_installation>/etc/system.properties file. To do this, follow these steps.

  7. Optional: Select the Use HTTP proxy checkbox and enter the server and port details.
  8. Optional: Select the Use Proxy Authentication checkbox and enter the user credentials.

    Example

    Wizard step showing checkboxes and input fields for configuring Proxy settings, SSH access, and SSL communication for Remote Engine
  9. Optional: Select the Set strong password for default SSH user checkbox to automatically create a strong password for SSH communication with Talend Remote Engine. Otherwise, tadmin is used.

    For further information about how SSH is configured for your engine, see Changing the auto-generated default SSH password.

  10. Optional: Select the Use SSL for JobServer communication checkbox to automatically secure the communication between Talend Remote Engine and its JobServer.

    For further information about how SSL is set up for Talend Remote Engine, see Enabling SSL communication for your Remote Engine.

  11. 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. Use this user to start and stop the engine.

Note that at 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!