Skip to main content Skip to complementary content

Configuring the JVM for your Talend JobServer (optional)

Talend JobServer allows you to choose another JVM than the one used by default to run your Jobs.

About this task

For example, you can configure Talend JobServer to start with Java 17 and execute Jobs with Java 11.

To achieve the same results with Talend JobServer installed as a service, see Installing Talend JobServer as a service on systemd-based Linux systems.

Procedure

  1. If not done yet, add the path to your Java 11 instance to your PATH environment variable.
  2. Open a command-line terminal and execute the java -version command.
    You should see Java 11 printed, indicating that any Java process starts by default using the Java 11 executable defined in the PATH.
  3. If not done yet, add the path to your Java 17 instance to your JAVA_HOME environment variable.
  4. Go to the directory where Talend JobServer is installed, and open the start_rs.sh file to edit it.
  5. Change MY_JAVA=java to MY_JAVA=$JAVA_HOME/bin/java, ensuring that your Talend JobServer starts with Java 17 defined in JAVA_HOME.
  6. Repeat this operation in the stop_rs.sh file.

Results

The next time you launch Talend JobServer, it will use Java 17 to start and Java 11 to execute Jobs.
Information noteNote: Alternatively, you can use the Job launcher path parameter to define a Java instance to use, though this is not recommended due to its lack of portability. To do this,

  1. Go to the directory <root>/conf/, where <root> is the Talend JobServer path, and open the TalendJobServer.properties file to edit it.

  2. In the line dedicated to the Job launcher path, add the path to your Java executable after the equal sign. 
    # Set the executable path of the binary which will run the job, for example: /usr/bin/java/java or "c:\\Program Files\\Java\\bin\\java.exe"
org.talend.remote.jobserver.commons.config.JobServerConfiguration.JOB_LAUNCHER_PATH=/usr/bin/java/java

    The use of quotes is only necessary when your path contains spaces, as shown in the capture. Otherwise, enter the path without quotes.

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