Installing and Configuring Talend server modules

Talend ESB Installation Guide for Solaris

EnrichVersion
6.2
EnrichProdName
Talend ESB
task
Installation and Upgrade
EnrichPlatform
Talend ESB
Talend CommandLine
Talend Runtime
Talend Administration Center
Talend JobServer

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, ESB 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, Services, Routes, and Generic OSGi Features 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. Add the execution rights to the relevant files using the following commands:

    $ chmod 755 bin/nexus
    $ chmod 755 bin/jsw/linux-ppc-64/*
    $ chmod 755 bin/jsw/linux-x86-32/*
    $ chmod 755 bin/jsw/linux-x86-64/*
    $ chmod 755 bin/jsw/macosx-universal-32/*
    $ chmod 755 bin/jsw/macosx-universal-64/*
  3. Launch the Nexus instance using the command . If you installed Nexus as a service, run the start command to launch it.

  4. 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 and ESB 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 Talend Runtime

Note

According to the solution you have subscribed to, Talend recommend you to use:

  • JobServer, if you have subscribed to a Data Integration solution;

  • Talend Runtime, if you have subscribed to both a Data Integration and a ESB solution.

    However, if you are willing to use both Talend Runtime and JobServer on the same machine, you are required to change the port numbers because, by default, both servers are using the same ports.

Talend Runtime is an OSGi container, based on Apache Karaf, allowing you to deploy and execute various components and applications inside its deploy folder. It can be used as an execution server to deploy and execute all the Services, Routes and Generic OSGi Features created from Talend Studio or any other Java IDE.

You have the possibility to adapt the configuration of the Talend Runtime container to deploy several containers on the same machine. For more information, see the Talend ESB Container Administration Guide.

To install and configure your Talend Runtime, see the following procedures:

Installing the Talend Runtime containers

You need now to define on which server(s) you will install Talend Runtime.

  1. First select the servers that will be used for the execution.

  2. Then, on each server, unzip the archive file containing the Talend Runtime application matching your release version of Talend.

    The archive file name for example reads: Talend-Runtime-V6.2.0.zip

  3. In the unzipped file you might need to configure the files org.ops4j.pax.web.cfg to change the HTTP listening port and org.apache.karaf.management.cfg to manage RMI connection to connect to Talend ESB Container via JMX, that you can find in the directory Talend-Runtime-VA.B.C/etc. Note that this file also allows you to define the artifact repository URL.

  4. To launch Talend Runtime, browse to the bin directory and run the trun file.

Now we simply have to declare these runtime instances in the Web application and their resources (CPU, RAM, etc.) should become available. To do this:

  1. Go to the Servers page of Talend Administration Center.

    Warning

    Only users that have Operation Manager role and rights can have a read-write access to this page. For more information on access rights, see your Talend Administration Center User Guide. So, you have to connect to Talend Administration Center as an Operation Manager to be able to configure your servers.

  2. And define the server as follows:

    Label

    TestingServer

    Description

    Type in the description of server.

    Host

    localhost

    Command port

    8000

    File transfer port

    8001

    Monitoring port

    8888

    Timeout on unknown status(s)

    120

    Username

    Type in the username for user authentication to access a Job server.

    Password

    Type in the password for user authentication to access a Job server.

    Active

    Select/clear the check box to activate/deactivate this server

    Use SSL

    Select/clear the check box to use or not your own SSL Keystore to encrypt the data prior to transmission.

    For more information about how to enable SSL, see Enabling the SSL encryption in Talend Runtime.

    Talend Runtime

    By default, servers created are Job servers.

    To deploy and execute your Jobs, Services, Routes or Generic tasks into Talend Runtime, select the Talend Runtime check box. The following fields will display: Mgmt-Server port, Mgmt-Reg port, Admin Console port and Instance.

    Mgmt-Server port RMI Server Port (44444 by default). This field is mandatory.
    Mgmt-Reg port RMI Registry Port (1099 by default). This field is mandatory.
    Admin Console port Port of the Administration Web Console (8040 by default). This field is mandatory and allows to activate the Admin server button allowing you to access the Administration Web console.
    Instance Type in the name of the container instance in which you will deploy and execute your Jobs, Services, Routes or Generic tasks, trun by default.

    This corresponds to the configuration of a Talend Runtime on the system that hosts the Web application. For any other system, the Host field should contain the IP address of the system. Check also that the ports 8000, 8001 and 8888 are available. These ports must be the same as defined in the TalendJobServer.properties defined above. Note that if no username and password pairs are defined in the file users.csv in the directory <root>/conf/ where <root> is the JobServer path, then you do not have to set the Username and the Password.

  3. Click the Servers page again so that the Talend Runtime servers appear with their properties.

Enabling the SSL encryption in Talend Runtime

The execution servers provided by Talend allows you to encrypt data prior to transmission via an existing SSL Keystore. To enable Secure Sockets Layer (SSL) at server side in order to establish an encrypted link between the Jobserver and its clients, proceed as follows:

  1. If you want to configure Talend Runtime, go to the etc directory and open the org.talend.remote.jobserver.server.cfg file to edit it.

  2. Edit the following line

    org.talend.remote.jobserver.server.TalendJobServer.USE_SSL=false

    and replace false with true.

    The next time you launch your execution server, the SSL protocol will be used to secure the communication between servers and clients.

Note

From Talend Administration Center, you have to select the Use SSL check box to enable the encryption.

Configuring Nexus in Talend Runtime

The default Nexus artifact repository URL is described in the etc/org.ops4j.pax.url.mvn.cfg file.

If your artifact repository has been installed on another URL, edit the org.ops4j.pax.url.mvn.repositories part of the file.

Installing and configuring the Drools Business Rules Management System (BRMS)

To install and configure the Drools Business Rules Management System (BRMS) on your machine, follow these procedures:

Installing manually the Drools Business Rules Management System (BRMS)

To manually install the Drools Business Rules Management System (BRMS), proceed as follows:

  1. Download the Talend-BRMS-YYYYMMDD_HHmm-VA.B.C.zip file and unzip it.

  2. Stop your Tomcat server.

  3. Go to the Talend-BRMS-Webapp-A.B.C folder.

  4. Copy the talend-brms-A.B.C.war file to <TomcatPath>/webapps.

  5. Unzip the WorkbenchInstallationResources.zip file.

  6. Copy the content of the WorkbenchInstallationResources/lib folder to <TomcatPath>/lib.

  7. Got to the WorkbenchInstallationResources/conf folder.

  8. Copy the btm-config.properties and resources.properties files to <TomcatPath>/conf.

  9. Create a backup copy of your <TomcatPath>/bin/setenv.sh file.

  10. Copy the WorkbenchInstallationResources/bin/setenv.sh file to <TomcatPath>/bin.

  11. Restart Tomcat to deploy the Drools Business Rules Management System (BRMS).

Configuring the Drools Business Rules Management System (BRMS) in Talend Administration Center

Before being able to use Drools BRMS in Talend Administration Center web application, you will need to configure its URL in the Configuration page. For more information about configuring the Web application, first read Installing and configuring Talend Administration Center.

Then after you access Talend Administration Center's Configuration page, set Drools URL, http://10.42.10.84:8080/kie-drools-wb/ for example.

For more information about the actual data contained on the Configuration page of Talend Administration Center, check out the Talend Administration Center User Guide.

When Drools Guvnor URL is correctly set up, the application can be accessed through the menu tree view of Talend Administration Center:

Note

If you have used Drools with older Talend product releases and you do not want to use the latest Drools version installed with Talend Administration Center, you must upgrade your Drools repository before being able to use it with the current release. For more information, check the article Migrating Drools repository from version 5.x to version 6.0.