Skip to main content Skip to complementary content

Installing Talend JobServer as a service on Windows

Before you begin

To configure the Talend JobServer parameters that are passed to the Java application, you must edit the last lines of the jsl_static64.ini file. This file indicates the path to different files, such as configuration files, .jar files, and Java libraries.
To do so, edit the parameters as shown below:
params = 5
param00 = -cp
param01 = c:\jobserver;c:\jobserver\lib\*
param02 = -Dcom.sun.management.jmxremote
param03 = -Dtalend_props=<JobServerPath>\conf\TalendJobServer.properties
param04 = org.talend.remote.jobserver.service.WindowsJobServer
where <JobServerPath> refers to the installation directory of the Talend JobServer application and X to the version number of the packages. If you installed Talend Studio using the installer, this path corresponds to <JobServerPath>\agent.
Information noteNote: Note that the first parameter indicated is named param00 and not param01, and that the use of quotes is not required around strings holding spaces. Note also that every parameter value must be indicated in a separate parameter.

Procedure

  1. Configure your JobServer to execute Jobs using the appropriate Java version based on those Jobs' Java compatibility levels.
    Two approaches are available:
    • Adaptive mode (recommended for JobServer instances from version 8.0.2.20250129_0823_patch, released in R2025-01):
      1. Open the jsl_static64.ini file.
      2. Add the paramXX parameters. These parameters specify the paths to the bin folders of the Java instances to use as candidates for Job executions. For example:
        <!-- Other parameters skipped for brevity -->
        param05 = -Dorg.talend.execution.JAVA_8_PATH=<pathToJava8BinFolder>
        param06 = -Dorg.talend.execution.JAVA_11_PATH=<pathToJava11BinFolder>
        param07 = -Dorg.talend.execution.JAVA_17_PATH=<pathToJava11BinFolder> 
    • If your JobServer version is older and cannot be upgraded, follow this procedure to specify the Java version for executions:
      Information noteNote: This approach is not dynamic and allows specifying only one Java version.
      1. In the jsl64.ini file, define the JAVA_HOME variable with the path to the Java instance.
      2. Set the PATH value with the path to the Java version to use for running Jobs.
      3. Set the jrepath value with the path to the Java version to use to launch Talend JobServer.
      For example,
      • To use Java 17 everywhere, and if the %JAVA_HOME% variable is not already set in your user environment, add the following lines under the [defines] and [java] sections:
        [defines]
        JAVA_HOME = c:\java\17.0.11-zulu
        PATH = %JAVA_HOME%\bin;%PATH% 
                                      
        [java]
        jrepath = c:\java\17.0.11-zulu
      • To use Java 17 for Talend JobServer and Java 11 for running Jobs, add the following lines under the [defines] and [java] sections:
        [defines]
        PATH = c:\java\11.0.23-zulu\bin;%PATH% 
                                      
        [java]
        jrepath = c:\java\17.0.11-zulu
    Information noteTip: If you skip this step, the Java instance for Talend JobServer is used to run Jobs.
  2. Open a CMD window in Administrator mode and browse to the conf directory of your Talend JobServer installation directory.
  3. Execute the following command:
    jsl_static64.exe -debug
  4. Stop execution by pressing Ctrl+C.
  5. In the CMD window, execute the following command: jsl_static64.exe -install
    As a result, the system indicates that Talend JobServer is installed as a Windows service.

Results

The Talend JobServer service is created and can be viewed by selecting Control Panel > Administrative Tools > Services in the Start Menu of Windows.

Note that, when shutting down or rebooting Windows, the Talend JobServer service does not stop. In order to avoid issues during start-up, you need to stop the service before shutting down or rebooting your machine.

To remove the service you can enter the following command in the same command window: jsl_static64.exe -remove

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!