Skip to main content Skip to complementary content

Installing Talend Component Server from the RPM repository

Install Talend Component Server with its default configuration using RPM.

Before you begin

  • Import the PGP key to validate the signature of the installation files. See Importing the PGP key.
  • Talend Component Server requires Java 8. You can use either Oracle Java or OpenJDK.
  • Make sure that the JAVA_HOME variable is correctly set to the Java home directory. For example: /usr/java/jdk1.8.0_181-amd64.
    Information noteTip: You can set it in the /root/.bashrc file by adding the following line to it: export JAVA_HOME=$(dirname $(dirname $(readlink -e /usr/bin/java))).

Procedure

  1. Create a file called talend.repo in the /etc/yum.repos.d directory, containing the following configuration:
    [talend-7.3.1]
    name=Talend 7.3.1
    baseurl='https://<user>:<password>@www.opensourceetl.net/rpms/talend/7.3.1/base/x86_64/'
    enabled=1
    gpgcheck=1
    gpgkey=http://www.opensourceetl.net/rpms/GPG-KEY-talend

    Credentials (user and password) are provided in the license email sent by Talend.

    Your repository is now ready for use.
  2. Install Talend Component Server.
    • To install the package with its default configuration, use the following command:
      sudo -E yum install talend-tcomp

      This command does not require any additional parameter. It installs the package and its dependencies with their default configuration in the default /opt/talend directory.

    • If the default parameters do not match your requirements install the package with custom parameters using the RPM command.

      For example, the following command installs the module in a specific directory:

      sudo -E rpm -i --prefix=<InstallPath> https://<user>:<password>@www.opensourceetl.net/rpms/talend/7.3.1/base/x86_64/talend-tcomp-7.3.1-202002191130.x86_64.rpm

      The list of configuration parameters is detailed in Talend Component Server RPM configuration parameters.

      Information noteNote: When installing the package with custom parameters, the dependencies are not installed. You need to install them beforehand.
    The package is now installed. You can start the service and use it.

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!