Installing and Configuring Talend server modules

Talend Big Data Platform Installation Guide for Windows

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

The following pages provide installation and configuration procedures for your Talend server modules.

Installing and configuring the Nexus artifact repository

Talend Administration Center is provided together with Nexus artifact repository. It is used to store software updates and Data Integration Job artifacts.

This tool is used for the Software Update feature and its instance holds the talend-updates repository where the updates are retrieved by the user.

It can also be used as a catalog for the Jobs created from Talend Studio or any other Java IDE. For this, two repositories are available: repo-snapshot for development purposes and repo-release for production purposes.

This instance is embedded in the .zip file of Talend Administration Center Web application and it allows you to store artifacts designed from Talend Studio or any other Java IDE and ready to be deployed and executed in an execution server. For more information, see the Talend Administration Center User Guide.

So when unzipping Talend Administration Center zip file, you will find an archive file called Artifact-Repository-Nexus-VA.B.C.D.E containing a ready-to-be-used Nexus artifact repository.

Nexus is based on Sonatype Nexus. For more information on how to use it, see Artifact Repository and Sonatype Nexus's documentation on http://www.sonatype.org/nexus.

To install and configure Nexus artifact repository, see the following procedures:

For more information on how to configure Nexus in Talend Runtime, see Configuring Nexus in Talend Runtime

Installing the Nexus artifact repository

To install the Nexus artifact repository, proceed as follow:

  1. Unzip the Artifact-Repository-Nexus-VA.B.C.D.E archive file in a dedicated folder.

  2. Launch the Nexus instance using the command nexus.bat console. If you installed Nexus as a service, run the start command to launch it.

  3. Log in the Nexus Web application (default login information: admin/Talend123). Make sure you have the relevant rights to access the releases and snapshots repositories.

Configuring the Software Update repository in Talend Administration Center

Once you installed the Nexus artifact repository and started it, you can configure it to use Talend Software Update.

Once you have launched and configured the Software Update repository, go to the Configuration page of Talend Administration Center and fill in the following information in the Software Update group:

  • Talend update url : Location URL to the Talend remote repository from which software updates are retrieved, this field is filled by default.

  • Talend update username et Talend update password : Type in the credentials of the software update repository user that you received from Talend.

  • Local repository url : Type in the location URL to the repository where software updates are stored. By default, it is http://localhost:8081/nexus/.

  • Local deployment username and Local deployment password : Type in the credentials of the user with deployment rights to the local repository. By default, it is talend-updates-admin/talend-updates-admin.

  • Local reader username and Local reader password : Type in the credentials of the user with read rights to the local repository. By default, no credentials are required but you are free to define them if you want to disable public access to the repository.

  • Local repository ID : Type in the ID of the repository in which software updates are published. By default, it is talend-updates.

In the Software Update page of Talend Administration Center, you can now see the versions and patches available and download them according to your needs.

Configuring Nexus in Talend Administration Center

Once you have launched the Nexus artifact repository, go to the Configuration page of Talend Administration Center and do the following:

  • Fill in the following information in the Artifact Repository node:

    • Artifact repository type: select NEXUS.

    • Nexus url: Type in the location URL to your Nexus Artifact repository, http://localhost:8081/nexus/ for example.

      Note

      "http://localhost:8081/nexus" is only given as example. Depending on your configuration, you may have to replace <localhost> with the IP address of the Web server and <8081> with the port that is used for your repository instance.

    • Nexus username: Type in the name of the repository user with Manager role. By default, it is admin.

    • Nexus password: Type in the password of the repository user with Manager role. By default, it is Talend123.

    • Nexus Default Release Repo: Type in the Nexus artifact repository's Release repository name. By default, it is releases.

    • Nexus Default Snapshot Repo: Type in the Nexus artifact repository's Snapshot repository name. By default, it is snapshots.

    • Nexus Default Group ID: Type in the name of the group in which to publish your Jobs, Service and Route artifacts. By default, it is org.example.

From the Job Conductor pages of Talend Administration Center, you can retrieve all the artifacts published in the two repositories to configure their execution in your execution server. For more information, see the Talend Administration Center User Guide.

Installing and configuring your JobServers

The execution servers allow you to execute the Jobs (processes) developed with Talend Studio from the Talend Administration Center web application.

Note that you can also use Talend Runtime servers to deploy and execute Jobs tasks if these Jobs are linked with Services or Routes, but these servers are especially used to deploy and execute Services, Routes, or even generic OSGi features when you are using our service-oriented products. For more information about the installation of Talend Runtime, see Installing Talend Runtime.

To install and configure your JobServers, see the following procedures:

Installing your JobServers

In order to install your JobServers, proceed as follows:

Unzip the archive file

  1. First select the servers that will be used to execute the Jobs developed with Talend Studio.

  2. Then, on each server, uncompress the archive file containing the JobServer application matching your version of Talend Studio.

    The archive file name for example reads: Talend-JobServer-YYYYMMDD_HHmm-VA.B.C.zip

  3. In the uncompressed file you need to configure the file TalendJobServer.properties that you can find in the directory <root>/conf/ where <root> is the JobServer path.

    For example, if you want to change the directory where the JobServer stores its data, change the org.talend.remote.jobserver.commons.config.JobServerConfiguration.ROOT_PATH parameter.

  4. Modify the installation directory of JobServer and check that the 8000, 8001 and 8888 ports are available.

Enable user authentication

  1. To enable user authentication on JobServer, you need to define one or more lines of username and password pairs in the file users.csv that you can find in the directory <root>/conf/ where <root> is the JobServer path.

  2. In the directory you have unzipped, you will find the files start_rs.bat and stop_rs.bat that will let you respectively start and stop the Job server.

JobServer is an application that allows a system installed on the same network as the Web application to declare itself as an execution server. These systems must obviously have a working JVM. For more information about the prerequisites of JobServer, see Software requirements.

Information about JobServer resources and load balancing :

Once you have declared these execution servers in the Servers page of the Talend Administration Center Web application, their resources (CPU, RAM, etc.) are displayed. For more information on how to do this, see your Talend Administration Center User Guide.

For some operating systems, the CPU information may not be available. You can test your system by setting up the following variable as true:

org.talend.monitoring.jmx.api.OsInfoRetriever.FORCE_LOAD in the file TalendJobServer.properties.

For users working in cluster mode, note that the ranking of servers to be used for load balancing is based on indicators, whose bounds (such as free disk space limits) and weight are defined in the file: monitoring_client.properties which is located in <ApplicationPath>\WEB-INF\lib\org.talend.monitoring.client-A.B.C.jar. These values can be edited according to your needs. For more information, see Configuring the indicators which determine which server to be used for load balancing.

Configuring the JVM for your JobServer (optional)

The JobServer application provided by Talend allows you to choose another JVM than the one used by default to launch your Jobs.

To change the Job launcher path, proceed as follows:

  1. Go to the directory <root>/conf/, where <root> is the 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=C:\Program Files\Java\jre1.8.0_65\bin\java.exe

    Note

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

  3. Save your changes and close the file.

The next time you launch JobServer, the java executable used will be the one you have previously set in the TalendJobServer.properties file.

Configuring the SSL Keystore (optional)

You are also able to choose another Keystore if needed.

To override the existing Keystore file, you have to:

  • generate a new Keystore with the utility tool called Keytool (Key and Certificate Management Tool);

  • set the new Keystore location;

  • enable the SSL Keystore at server side.

To generate a Keystore

  1. Open a command prompt and change directory to <root>/keystores where <root> is the JobServer path.

  2. Type in the following:

    keytool -genkey -keystore <myKeystoreName> -keyalg RSA

    where <myKeystoreName> refers to the name of the Keystore you are creating.

  3. Enter the password for your Keystore twice, then enter the other optional information, such as your name, the name of your organization, your state etc., if needed.

  4. Type in yes to confirm your information.

  5. Type in the password you have previously defined. The new Keystore file has been created in <root>/keystores.

To set the location of the new Keystore

To set the new Keystore location, you can either edit the JAVA_OPTS environment variable or edit the launching script (start_rs.bat) of the Jobserver.

  1. To edit the JAVA_OPTS environment variable, add:

    -Djavax.net.ssl.keyStore=/<myDirectory>/<myKeystore>

    -Djavax.net.ssl.keyStorePassword=<myPassword>

    to your JAVA_OPTS environment variable, where <myDirectory> is the installation directory of your Keystore, <myKeystore> is the name of your Keystore and <myPassword> is the password you have previously defined for your Keystore.

    Note

    If you have not created the JAVA_OPTS environment variable yet, you have to create it before completing this procedure.

    OR

  2. To edit the launching script, open the start_rs.bat to edit it.

  3. As shown in the capture, add

    -Djavax.net.ssl.keyStore=/<myDirectory>/<myKeystore>

    -Djavax.net.ssl.keyStorePassword=<myPassword>

    to the JVM arguments location, where <myDirectory> is the installation directory of your Keystore, <myKeystore> is the name of your Keystore and <myPassword> is the password you have previously defined for your Keystore.

To configure the service

  1. Open the jsl_static64.ini file to edit it.