Configuring JSL and .ini file for the CommandLine and JobServer services - 6.1

Talend Data Services Platform Installation Guide

EnrichVersion
6.1
EnrichProdName
Talend Data Services Platform
task
Installation and Upgrade
EnrichPlatform
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend DQ Portal
Talend ESB
Talend Identity Management
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio

A jsl.ini file is integrated in the JobServer and ready for configuration. However, before starting to install CommandLine as a service, you must have previously downloaded JSL.

Java Service Launcher allows you to launch Java applications as Windows services.

Prerequisites for the CommandLine service:

  • The JSL archive file has been downloaded, for example from this website, and has been unzipped in the directory of your choice.

    In the bin directory, make sure you have the following files: jsl.ini and jsl.exe for 32-bit Windows users, and jsl_static64.ini and jsl_static64.exe for 64-bit Windows users.

    If the jsl_static64.ini file does not exist in the JSL directory, copy the jsl.ini file and rename it to jsl_static64.ini.

  • You have copied these .ini and .exe files at the root of the CommandLine installation directory.

Editing the .ini file to reflect your configuration

  1. Open the file jsl.ini (for 32-bit Windows) or jsl_static64.ini (for 64-bit Windows) in order to configure it.

    This file is located at the root of the CommandLine installation directory for the CommandLine service, and in the conf folder of the JobServer installation directory for the JobServer service.

  2. At the beginning of the file, you can see different names: appname corresponds to the name of your application, servicename corresponds to the name you want to give to the service and displayname corresponds to the name that will be displayed when creating the service.

    If you are not satisfied with those default names, edit the part that is after the = sign according to your needs.

    Under this area, you can see that, by default, the JAVA_HOME environment variable is pointing towards the JRE path.

    [java]
    ;Path to the java runtime used
    ;If this option is not used the default from the registry will be used
    ;jrepath=..\..\..\jdk16
    jrepath=C:\Program Files\Java\jreX.X.X_XX

    This path is set in the [java] part of the .ini file. If the default path is not the path of the installation directory of your application, edit the part that is after the = sign and write this path. In this example, X.X.X_XX refers to the version of Java.

  3. Uncomment the following line to define the type of JVM to be used:

    jvmtype=server

    Next time the service starts, the jvm.dll file located in the <Java_Path>/jre/bin/server directory will be used.

  4. Save your changes and close the file.

Configuring the CommandLine parameters

To configure the CommandLine parameters that are passed to the Java application, you have to edit the last lines of the jsl.ini or jsl_static64.ini file which indicate the path to different files (such as configuration files, .jar files and/or java libraries).

  • To do so, edit the parameters as shown below:

    params = 14
    param00 = -Xms64m
    param01 = -Xmx1024m
    param02 = -XX:MaxMetaspaceSize=256m
    param03 = -jar
    param04 = <CommandLinePath>\plugins\org.eclipse.equinox.launcher_X.X.X.vXXXXXXXX.jar
    param05 = -nosplash
    param06 = -application
    param07 = org.talend.commandline.CommandLine
    param08 = -consoleLog
    param09 = -data
    param10 = <CommandLinePath>\commandline-workspace
    param11 = startServer
    param12 = -p
    param13 = 8002

    where <CommandLinePath> refers to the installation directory of the CommandLine application.

    Note

    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 of the command line must be indicated in a separate parameter.

    Once you have configured the jsl file you are able to install CommandLine as a service. For more information, see CommandLine.

Configuring the JobServer parameters

To configure the JobServer parameters that are passed to the Java application, you have to edit the last lines of the jsl.ini or jsl_static64.ini file which indicate the path to different files (such as configuration files, .jar files and/or java libraries).

  • To do so, edit the parameters as shown below:

    params = 6
    param00 = -cp
    param01 = <JobServerPath>;<JobServerPath>\lib\jmxremote_optional.jar;
    <JobServerPath>\lib\log4j-X.X.XX.jar;<JobServerPath>\lib\commons-io-X.X.jar;
    <JobServerPath>\lib\jsl.jar
    param02 = -Djava.library.path=<JobServerPath>\jsysmon-XXXXXXXX\native\windows\
    param03 = -Dcom.sun.management.jmxremote
    param04 = -Dtalend_props=<JobServerPath>\conf\TalendJobServer.properties
    param05 = org.talend.remote.jobserver.service.WindowsJobServer

    where <JobServerPath> refers to the installation directory of the JobServer application and X to the version number of the packages. Note that if you installed your Studio using the installer, this path corresponds to <JobServerPath>/agent.

    Note

    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 of the command line must be indicated in a separate parameter.

    Once you have configured the jsl file you are able to install JobServer as a service. For more information, see JobServer.