Vous êtes sur la page 1sur 58

Talend Enterprise ESB

Installation Guide

5.0_b

Talend Enterprise ESB

Talend Enterprise ESB: Installation Guide


Adapted for Talend Enterprise ESB v5.0.x. Supersedes any previous Installation Guide.
Copyright 2011-2012

Notices
Talend, Talend Integration Factory, Talend Service Factory, and Talend ESB are trademarks of Talend, Inc.
Apache CXF, CXF, Apache Karaf, Karaf, Apache Camel, Camel, Apache Maven, Maven, Apache Archiva and Archiva are trademarks of
The Apache Foundation.
All other brands, product names, company names, trademarks and service marks are the properties of their respective owners.

Table of Contents
Preface .............................................. v
1. General information ................... v
1.1. Purpose ........................... v
1.2. Audience ......................... v
1.3. Typographical
conventions ............................ v
2. History of changes ...................... v
3. Feedback and Support ............... vi

Chapter 1. Prior to installing


Talend Enterprise ESB ..................... 1
1.1. License key ............................. 2
1.2. Installation requirements .......... 2
1.2.1. Memory usage ................ 2
1.2.2. Disk usage ..................... 2
1.2.3. Environment variable
configuration .......................... 3
1.2.4. Naming conventions
for software packages ............... 3
1.3. Compatible Platforms ............... 4
1.3.1. Talend Studio ................. 4
1.3.2. Talend Administration
Center ................................... 5
1.3.3. Talend Runtime .............. 5
1.4. Compatible SVN ...................... 6
1.5. Compatible Runtime
Containers .................................... 6
1.5.1. Talend Administration
Center ................................... 6
1.5.2. Talend ESB ................... 6
1.6. Compatible Web browsers ......... 7
1.7. Compatible Databases .............. 7
1.7.1. Talend Administration
Center ................................... 7
1.7.2. Activity Monitoring
Console / Service Activity
Monitoring (SAM) .................. 8

Chapter 2. Introducing Talend


Enterprise ESB ................................. 9
2.1. General introduction to
Talend Enterprise ESB ..................
2.1.1. Apache Tomcat Server
...........................................
2.1.2. Database ......................
2.1.3. SVN ...........................
2.1.4. Talend Artifact
Repository ............................
2.1.5. Talend Runtime ............
2.2. Detailed introduction to
Talend Enterprise ESB Server ........
2.2.1. Administration
database ...............................
2.2.2. Activity Monitoring
Console log database ..............
2.2.3. Apache Tomcat server
...........................................

10
10
11
11
11
11
12
12
12

2.2.4. SVN server .................. 13


2.2.5. Software update
repositories ........................... 13
2.2.6. Provisioning
repositories ........................... 14

Chapter 3. Installing Talend


Enterprise ESB for the first time
.......................................................... 17
3.1. Setting up your project
server on SVN ............................. 18
3.1.1. Windows ..................... 18
3.1.2. Debian, apache ............. 19
3.1.3. Debian, ssh .................. 20
3.1.4. Redhat (Fedora),
Apache ................................ 21
3.1.5. Mac OS X ................... 22
3.2. Deploying the Web
application on an application
server ......................................... 23
3.2.1. Deploying the Web
application on Tomcat ............ 23
3.2.2. Deploying the Web
application on JBoss ............... 24
3.2.3. Log storage mode .......... 24
3.3. Configuring Talend
Administration Center (Web
application) ................................. 25
3.3.1. Configuring the Web
application access .................. 25
3.3.2. Managing the
connection pool via Tomcat..... 26
3.3.3. Advanced
configuration ........................ 27
3.4. Installing and configuring
Talend ESB ................................. 28
3.4.1. Accessing Talend ESB
Container ............................. 28
3.4.2. Installing Apache
ActiveMQ ............................ 29
3.4.3. Accessing Service
Locator ................................ 30
3.4.4. Installing Service
Activity Monitoring ............... 31
3.4.5. Installing Security
Token Services ..................... 33
3.5. Installing and configuring
Talend Artifact Repository ............ 34
3.5.1. Configuration for the
Software Update repository ...... 35
3.5.2. Configuration for the
Provisioning repository ........... 36
3.6. Installing Talend Runtime ....... 37
3.6.1. Installing the Talend
Runtime containers ................ 37
3.7. Installing a Business Rules
Management System (Drools) ........ 39

13

Talend Enterprise ESB Installation Guide

Talend Enterprise ESB

3.8. Setting up the automatic log


purge (optional) ........................... 39

Chapter 4. Configuring Talend


Enterprise ESB Studio and AMC
.......................................................... 41
4.1. Prerequisites of Talend
Enterprise ESB Studio ...................
4.1.1. Installing database
client software (for bulk
mode) ..................................
4.2. Configuring the Talend
Enterprise ESB Studio ...................
4.2.1. Installing external
modules ...............................
4.3. Memory configuration and
launching issues ...........................
4.3.1. Configuring the .ini file
on Linux/Windows ................
4.3.2. For 64-bit platforms on
Linux/Windows .....................
4.3.3. For non Linux/
Windows platforms ................
4.3.4. For 64-bit platform on
non Linux/Windows OS ..........
4.4. Configuring Activity
Monitoring Console ......................

42

42
42
43
43
43
44
44
44
45

Appendix A. H2 Database
Administration & Maintenance
.......................................................... 47
A.1. About H2 embedded database
...................................................
A.2. Administrating the H2
database through the Web console
...................................................
A.2.1. Connecting to the H2
Web Console ........................
A.2.2. Backing up the H2
database ...............................
A.3. Setting up the H2 database for
access from other machines .............

iv

48

48
48
50
51

Talend Enterprise ESB Installation Guide

Preface
1. General information
1.1. Purpose
This Installation Guide explains how to install and configure Talend Enterprise ESB modules and
related applications. For detailed explanation on how to use and fine-tune Talend Enterprise ESB
applications, please refer to your Talend Enterprise ESB User Guides.
Information presented in this document applies to Talend Enterprise ESB releases beginning with
5.0.x.

1.2. Audience
This guide is devoted for administrators of Talend Enterprise ESB Studio, Talend Administration
Center, and/or Activity Monitoring Console.
The layout of GUI screens provided in this document may vary slightly from your actual GUI.

1.3. Typographical conventions


This guide uses the following typographical conventions:
text in bold: window and dialog box buttons and fields, keyboard keys, menus, and menu and
options,
text in [bold]: window, wizard, and dialog box titles,
text in courier: system parameters typed in by the user,
text in italics: file, schema, column, row, and variable names,

The
icon indicates an item that provides additional information about an important point. It is
also used to add comments related to a table or a figure,

The
icon indicates a message that gives information about the execution requirements or
recommendation type. It is also used to refer to situations or information the end-user need to be
aware of or pay special attention to.
Any command is highlighted with a grey background or code typeface.

2. History of changes
The below table lists changes made in the Talend Enterprise ESB Installation Guide.

Talend Enterprise ESB Installation Guide

Feedback and Support

Version

Date

History of Change

v5.0_a

12/12/2011

New Installation Guide.

v5.0_b

13/02/2012

Update of Installation Guide includes:


- Reorganized and updated the chapter about Prerequisites,
including information about supported Subversions,
- Updated information regarding the installation of Talend Artifact
Repository (Section 3.5, Installing and configuring Talend Artifact
Repository),
- Updated the Installing Talend Enterprise ESB for the first time
chapter: added an example of SVN installation for MAC OS X.

3. Feedback and Support


Your feedback is valuable. Do not hesitate to give your input, make suggestions or requests regarding
this documentation or product and find support from the Talend team, on Talends Forum website at:
http://talendforge.org/forum

vi

Talend Enterprise ESB Installation Guide

Chapter 1. Prior to installing Talend


Enterprise ESB
This chapter provides useful information on software and hardware prerequisites you should be aware of, prior
to starting the installation of Talend modules.

Talend Enterprise ESB Installation Guide

License key

1.1. License key


You should have received an email from Talend, including the following information:
your personal license key in a file with no extension:
The license key is mandatory to be able to access each module of Talend Enterprise ESB. Keep this file at
hand in a safe place.
For more information on how to use your license key, see Section 3.3.1, Configuring the Web application
access and Section 4.2, Configuring the Talend Enterprise ESB Studio.
The availability of different perspectives in the Studio you want to install and use depends on your
license or on the type of the remote project to which you connect. For further information on licenses
and perspectives in the Studio, see the appropriate Administrator or User Guide.
the software parts in archive files:
Unzip each archive file at the root or in a short path of the machine where they are to be deployed (Talend
Studio on a developers machine and Talend Administration Center on the execution server for example).
If you are on Windows, we recommend that you use 7-zip to unzip files, as it handles long file names well.
the documentation (including the one you are reading now):
Each module of Talend has a dedicated Administrator or User Guide available in pdf.

1.2. Installation requirements


To make the most out of the Talend products you subscribed to, please consider the following hardware and
software requirements.

1.2.1. Memory usage


Memory usage heavily depends on the size and nature of your Talend projects. However, to make it short, if
your Jobs include many transformation components, you should consider upgrading the total amount of memory
allocated to your servers, based on the following recommendations.
Product

Client/Server

Recommended alloc. memory

Talend Administration Center

Server

4GB minimum, 8GB recommended

Studio

Client

3GB minimum, 4 GB recommended

Talend Runtime

Server

2GB minimum, 4 GB recommended1

1. Memory requirements depend on the executed processes.

1.2.2. Disk usage


The same requirements also apply for disk usage. It also depends on your projects but can be summarized as:

Talend Enterprise ESB Installation Guide

Environment variable configuration

Product

Client/Server

Required
disk Required disk space for use
space
for
installation

Talend
Administration Server
Center with Talend Artifact
Repository (for Software
update and Provisioning
repository)

800MB

800MB minimum + project


size = 20GB+ recommended

Studio

Client

3GB

3+ GB

Talend Runtime

Server

400MB

400+ MB

1.2.3. Environment variable configuration


Prior to installing your Talend solutions, you have to set the JAVA_HOME Environment variable.
To do so, define your JAVA_HOME environment variable so that it points to the JDK directory.
For example, if the JDK path is C:\Java\JDKx.x.x\bin, you must set the JAVA_HOME environment variable to
point to: C:\Java\JDKx.x.x.
It is highly recommended that the full path to the server installation directory is as short as possible and
does not contain any space character. If you already have a suitable JDK installed in a path with a space,
you simply need to put quotes around the path when setting the values for the environment variable.

1.2.4. Naming conventions for software packages


In the email you received from Talend are listed a number of links to software modules for you to download. The
file naming convention is as follows:
Zip/jar file naming convention

Example

Description

Talend-AdministrationCenterrYYYYY-VA.B.C

Talend-AdministrationCenterr74687-V5.0.1.zip

Talend
Administration
Center
Web-based application used to
administrate Talend Enterprise ESB
projects and users + Talend Artifact
Repository.

Talend-Studio-rYYYYY-VA.B.C Talend-Studio-r74687-V5.0.1.zip

Commandline interface to the IDE +


Studio IDE (GUI)

Talend-Runtime-VA.B.C

Talend-Runtime-V5.0.1.zip

Talend Runtime: OSGi Container


including
JobServer.
Talend
Runtime is a standalone equivalent
to the Talend ESB OSGi Container
(container folder) of Talend ESB.

Talend-ESB-VA.B.C

Talend-ESB-V5.0.1.zip

Talend ESB: application integration


solution with an OSGi Container,
Service Locator, Service Activity
Monitoring and Security Token
Service. It includes the Talend
Runtime (in the container folder)
and provides additional parts
like examples, standalone, Tomcat
deployment relevant parts and other

Talend Enterprise ESB Installation Guide

Compatible Platforms

Zip/jar file naming convention

Example

Description
additional parts primarily used by
Java Developers.

Where:
YYYYY: Revision number,
A.B.C.: Major. Minor. Patch: revision level if relevant.
The software modules must be all in the same versions/revisions! This means that both YYYY and A.B.C
must match on both client side and server side.

1.3. Compatible Platforms


Despite our intensive tests, you might encounter some issues when installing our products on some Operating
Systems.
Please refer to the grids below for a summary of supported OS and Java Runtime environments.

1.3.1. Talend Studio


OS

Name

Version

Processor

Java
JRE

Unix

Linux Ubuntu

10.04

64 bits

Oracle
1.6

Java recommended

Unix

Redhat Linux
Server Edition

Enterprise 6.1

64 bits

Oracle
1.6

Java recommended

Unix

Redhat Linux
Server Edition

Enterprise 5.4

64 bits

Oracle
1.6

Java recommended

Unix

Linux CentOS

5.4

32 bits

Oracle
1.6

Java recommended

Unix

Linux Ubuntu

10.4

32 bits

Oracle
1.6

Java supported

Unix

Linux Ubuntu

11.10

32 & 64 bits

Oracle
1.6

Java supported

Unix

Redhat Linux
Server Edition

Enterprise 5.3/5.4/5.6

32 bits

Oracle
1.6

Java supported

Unix

Redhat Linux
Server Edition

Enterprise 6.1

32 bits

Oracle
1.6

Java supported

Windows

Microsoft Windows

XP SP3

32 bits

Oracle
1.6

Java recommended

Windows

Microsoft Windows

64 bits

Oracle
1.6

Java recommended

Windows

Microsoft Windows

XP SP3

64 bits

Oracle
1.6

Java supported

Windows

Microsoft Windows

Vista SP1

32 & 64 bits

Oracle
1.6

Java supported

Talend Enterprise ESB Installation Guide

JDK/ Support type

Talend Administration Center

OS

Name

Version

Processor

Java
JRE

JDK/ Support type

Windows

Microsoft Windows

32 bits

Oracle
1.6

Java supported

MAC-OS

MAC-OS

Lion/10.6

64 bits

Oracle
1.6

Java recommended

1.3.2. Talend Administration Center


OS

Name

Version

Processor

Java
JRE

JDK/ Support type

Unix

Linux Ubuntu

10.04

64 bits

Oracle
1.6

Java recommended

Unix

Red Hat Linux Enterprise 5.4


Server Edition

32 bits

Oracle
1.6

Java recommended

Unix

Red Hat Linux Enterprise 6.1


Server Edition

64 bits

Oracle
1.6

Java recommended

Unix

Solaris

10

x86 64 bits

Oracle
1.6

Java recommended

Unix

Linux CentOS

5.4

32 bits

Oracle
1.6

Java supported

Unix

Red Hat Linux Enterprise 5.4


Server Edition

64 bits

Oracle
1.6

Java supported

Unix

SUSE SLES

10/11

32 & 64 bits

Oracle
1.6

Java supported

Unix

Solaris

10

sparc 64 bits

Oracle
1.6

Java supported

Windows

Windows Server

2003 SP2

64 bits

Oracle
1.6

Java supported

Windows

Windows Server

2008 R2

64 bits

Oracle
1.6

Java recommended

1.3.3. Talend Runtime


OS

Name

Version

Processor

Java
JRE

Unix

Linux Ubuntu

10.04

64 bits

Oracle Java 1.6 recommended

Unix

Linux CentOS

5.4

32 bits

Oracle Java 1.6 recommended

Unix

Red Hat Linux Enterprise 5.3/5.4/5.6


Server Edition

64 bits

Oracle Java 1.6 supported

Unix

Red Hat Linux Enterprise 6.1


Server Edition

64 bits

Oracle Java 1.6 recommended

Unix

Solaris

10

sparc 64 bits Oracle Java 1.6 recommended

Unix

Linux CentOS

5.3/5.6

32 bits

Oracle Java 1.6 supported

Unix

Linux Ubuntu

10.04

32 bits

Oracle Java 1.6 supported

Talend Enterprise ESB Installation Guide

JDK/ Support type

Compatible SVN

OS

Name

Version

Processor

Java
JRE

JDK/ Support type

Unix

Linux Ubuntu

11.10

32 & 64 bits Oracle Java 1.6 supported

Unix

SUSE SLES

10/11

32 & 64 bits Oracle Java 1.6 supported

Unix

Solaris

10

x86 64 bits

Oracle Java 1.6 supported

Windows

Windows Server

2008 R2

64 bits

Oracle Java 1.6 recommended

Windows

Windows Server

2003 SP2

64 bits

Oracle Java 1.6 supported

1.4. Compatible SVN


Please refer to the tables below for a summary of supported SVN clients/servers that you can use to store your
projects.
Subversion client

Version

Support type
supported1

Apache Subversion (former Tigris) 1.7 or earlier


1. http://subversion.apache.org

Subversion servers

Version

Support type

Visual SVN Server

2.5 or earlier

recommended1

Bitnami Subversion Stack

based on SVN v.1.7 or earlier

supported

1. http://www.visualsvn.com/server/download

1.5. Compatible Runtime Containers


Please refer to the grids below for a summary of supported Web application server. Based on reported issues, we
considered that some runtime containers are not supported even though the issue can be resolved in particular
conditions. A note has been added providing configuration details.

1.5.1. Talend Administration Center


Runtime Containers

Version

Support type

Apache Tomcat

recommended

Apache Tomcat

supported

JBoss Application Server

4.2.2

supported

1.5.2. Talend ESB


Runtime Containers

Version

Talend ESB Container (Apache 5.0 (2.2.4)


Karaf)

Support type
recommended

Talend Enterprise ESB Installation Guide

Compatible Web browsers

Runtime Containers

Version

Support type

Apache Tomcat

supported

JBoss Application Server

4.2.2

supported with limitations1

1. ESB/CXF service participants.

1.6. Compatible Web browsers


Despite our intensive tests, you might encounter some issues when accessing Talend Administration Center with
some Web browser.
Please refer to the table below for a summary of supported Web browser. Based on reported issues, we considered
that some Web browsers are not supported even though the issue can be resolved in particular conditions. A note
has been added providing configuration details.
Web browser

Talend Administration Center

Mozilla Firefox 3.6 to 8

Working

Microsoft Internet Explorer 7 and 8

Working

Microsoft Internet Explorer 9

Not working

Google Chrome

Working1

1. Only limited support is provided. Contact Support for details.

1.7. Compatible Databases


Please refer to the grids below for a summary of supported databases. Based on reported issues, we considered
that some databases are not supported even though the issue can be resolved in particular conditions. A note has
been added providing configuration details.

1.7.1. Talend Administration Center


Databases

Version

Support type

H2

1.3

recommended1

MySQL

5.5

recommended2

Oracle

10

recommended3

MySQL

5.0/5.1

supported

MS SQL Server

2005

supported

MS SQL Server

2008

supported

Oracle

11

supported

1. http://www.h2database.com, H2 is provided by Talend with Talend Administration Center.


2. http://www.mysql.com

Talend Enterprise ESB Installation Guide

Activity Monitoring Console / Service Activity Monitoring (SAM)

3. http://www.oracle.com

1.7.2. Activity Monitoring Console / Service Activity


Monitoring (SAM)
Databases

Version

Support type

MySQL

5.5

recommended

Oracle

10

recommended

IBM DB2

9.7

supported

MySQL

5.0/5.1

supported

H2

1.3

supported1

MS SQL Server

2005

supported

MS SQL Server

2008

supported

Oracle

11

supported

Derby DB

>10.8

supported with limitations2

1. Requires an H2 Database Server separated from Talend Administration Center.


2. Only for development and test purpose.

Talend Enterprise ESB Installation Guide

Chapter 2. Introducing Talend Enterprise


ESB
This chapter introduces Talend Enterprise ESB. It provides a detailed description of the architecture and lists
all modules that are required for the installation and configuration of Talend Enterprise ESB Studio, Talend
Administration Center, Talend Enterprise ESB and/or Activity Monitoring Console.

Talend Enterprise ESB Installation Guide

General introduction to Talend Enterprise ESB

2.1. General introduction to Talend Enterprise


ESB
The following image shows the distributed architecture of Talend Enterprise ESB. However, we recommend you
to centralize all the server modules on one single system to ease their management:

All Talend applications installed must be in the same version.


The elements that are required at a minimum for using Talend Enterprise ESB include:
A server that hosts Talend Administration Center (Tomcat server),
A storage server for Project metadata (SVN),
A storage database for administration metadata (by default, an embedded H2 database is used).
An artifact repository software (based on Apache Archiva) for storing all ESB Artifacts to be deployed onto
Talend Enterprise ESB and for Software Updates to handle the updates of your Talend products.
An OSGi Container (based on Apache Karaf) for deploying and executing the artifacts (Talend Runtime)
Each of these elements is detailed in the following sub-sections.

2.1.1. Apache Tomcat Server


The Apache Tomcat server is an application server that hosts the Talend Web application. The Web application
gives access to all management and administration functionalities for an integration project. These functionalities
include:

10

Talend Enterprise ESB Installation Guide

Database

definition of projects,
management of user rights,
Service monitoring,
Service, Route and generic OSGi Feature deployment,
Service, Route and generic OSGi Feature execution.
Talend Web application can also be hosted by JBoss application server. For more information on how to
deploy the Web application on JBoss, see Section 3.2.2, Deploying the Web application on JBoss.

2.1.2. Database
The database server is used to manage the persistence. By default an embedded H2 database is used, but you
can also use MySQL, SQL Server, or Oracle to store all cross-project data (users, projects, authorization, license,
tasks, triggers, dashboard).

2.1.3. SVN
The SVN server is used to manage the persistence of all the data relating to the objects stored in svn mode in
the Repository (Jobs, Routes, Services, Business models, Metadata, Routines, etc.).
Talend Enterprise ESB Studio is a rich client that allows the user (such as a project manager, a developer or a
DBA) to work on any Talend project for which he has authorization.

2.1.4. Talend Artifact Repository


With Talend Artifact Repository, based on Apache Archiva, Talend provides access to a preconfigured artifact
repository with the repositories necessary to use the functionalities of the Software Update and Provisioning
repositories.
The software update repository is used to manage application updates (versions and patches) distributed by
Talend. By default two repositories are embedded within this repository: one to publish the updates and one to
retrieve them. These repositories allow the user to visualize the updates available. For detailed information, see
Section 2.2.5, Software update repositories.
The Provisioning repository is used as a catalog in which all ESB artifacts (Jobs, Routes, Services and Generic
OSGi features) to be deployed and executed are stored. These ESB artifacts are designed by the user from Talend
Enterprise ESB Studio or any other Java IDE. By default two repositories are embedded within this repository:
one for development and one for production. These repositories make artifacts available for deployment in Talend
Runtime. For detailed information, see Section 2.2.6, Provisioning repositories.

2.1.5. Talend Runtime


Talend Runtime (based on Apache Karaf) is an execution container in which all your Service, Route and Generic
OSGi features, which are retrieved from the Provisioning repository, are deployed and executed as OSGi bundles.

Talend Enterprise ESB Installation Guide

11

Detailed introduction to Talend Enterprise ESB Server

2.2. Detailed introduction to Talend


Enterprise ESB Server
This section describes in more details the architecture of each of the modules depicted in the previous section.

2.2.1. Administration database


By default, an embedded H2 database is used to store administration information. But you have the possibility to
change database to MySQL, MSSQL or Oracle if you prefer so.
The database will be named <talend_administrator> in the rest of this document.
The <talend_administrator> administration database will contain all the data related to project information
and administration including: administration data, project declaration (storage mode), user declaration and
authorization, task list, etc.
The tables in this database are automatically created when connecting for the first time to Talend Enterprise
ESBTalend Administration Center. The created tables include (among others):
a Users table,
a Projects table,
a Rights table.
These tables are created, populated and managed automatically by Talend Enterprise ESB.

2.2.2. Activity Monitoring Console log database


If you want to use the Activity Monitoring Console, an <AMC> log database must be created, which can be installed
on any server. This <AMC> database will initially be empty. Its name may be modified, but you must take into
account this modification in the rest of this document.
The <AMC> database will contain three tables that collect data allowing users to monitor Jobs. The three tables
will collect data from the following components:
tFlowMeterCatcher,
tLogCatcher,
tStatCatcher.
Instructions on how to create these tables and their structure is provided in the section Configuring Activity
Monitoring Console sources of the Activity Monitoring Console User Guide.
A corresponding SQL user must be created and thus mapped to have access to this database. This user should be
granted the create and update rights.
The installation of the <AMC> database is optional for Talend Enterprise ESB and is only required
when using the tFlowMeterCatcher, tLogCatcher and tStatCatcher components. These components can

12

Talend Enterprise ESB Installation Guide

Apache Tomcat server

be used in Jobs (for example, ESB Consumer jobs) for REST and Soap ESB Service Providers. Only the
tLogCatcher component is supported for now and Routes currently can not use these components.

2.2.3. Apache Tomcat server


Version 6.0 or later should be used. This software is an application server that can host the Web application which
allows users to (depending on their role):
Manage user accounts and roles/rights,
Access to the ESB Conductor to set the deployment and execution of Services, Routes and Generic OSGi
features,
Access to the Dashboard to monitor Jobs,
Manage projects.
Note that the best recommended versions for Tomcat are 6.0 and 7.0, however the 5.5 version is also
supported.
Talend Web application can also be hosted by JBoss application server. For more information on how to
deploy the Web application on JBoss, see Section 3.2.2, Deploying the Web application on JBoss.

2.2.4. SVN server


In SVN mode, project metadata (Jobs, Services, Routes, Business Models, Documentation, etc.) are stored in an
SVN repository rather than in a database. This is the recommended storage mode and the only mode that allows
to store large projects.
We recommend you to store several projects per repository, simply in order not to have too many repositories to
deal with. However you can choose to store only one project per SVN repository, if you prefer so.
You can also have several SVN repositories each containing several projects. For more information on
how to create projects and store them in an SVN repository, see Talend Administration Center User Guide.

2.2.5. Software update repositories


The following image shows the architecture of the software update repository linked to Talend Administration
Center and to the Studio.

Talend Enterprise ESB Installation Guide

13

Provisioning repositories

To download and install some software updates, you need to use Talend Artifact Repository and its two dedicated
embedded repositories:
an admin repository named talend-update-admin used to publish the updates;
a user repository named talend-update-user used to retrieve the updates.
To do so, you must install Talend Artifact Repository on your machine and log in once to its Web interface
following the procedure described in in the Section 3.5, Installing and configuring Talend Artifact Repository.
The Talend Artifact Repository archive file is embedded in the Talend Administration Center archive
file that is provided by Talend.
The Studio is connected to Talend Administration Center to retrieve the repository connection information and
the version updates are detected and installed automatically.
In Talend Administration Center, the new versions and patches are detected and the administrator can accept them.
For more information on how to install and configure this software update repository, see Section 3.5, Installing
and configuring Talend Artifact Repository.
For more information on how to check updates via these repositories, see the Talend Administration Center and
Talend Enterprise ESB Studio User Guides.

2.2.6. Provisioning repositories


Talend Artifact Repository is used to store as artifacts all the Services, Routes and Jobs created in Talend
Enterprise ESB Studio or any Generic OSGi Features created in any other Java IDE.

14

Talend Enterprise ESB Installation Guide

Provisioning repositories

Once published, those artifacts can be selected through Talend Administration Center in order to set their
deployment as OSGi features in Talend Runtime.
When the deployment of a feature is initiated in Talend Administration Center, Talend Runtime requests the
corresponding artifact in Talend Artifact Repository. So, Talend Artifact Repository deploys the feature in
Talend Runtime which can now execute it.
Talend Artifact Repository comes with two embedded repositories dedicated to store your ESB artifacts:
a repo-snapshot repository to publish snapshot artifacts for development purposes,
a repo-release repository to publish stable artifacts for production purposes.
For more information on how to install and configure Talend Artifact Repository, see the Section 3.5, Installing
and configuring Talend Artifact Repository

Talend Enterprise ESB Installation Guide

15

Talend Enterprise ESB Installation Guide

Chapter 3. Installing Talend Enterprise ESB


for the first time
We strongly encourage you to read the chapters: Chapter 1, Prior to installing Talend Enterprise ESB and
Section 2.2, Detailed introduction to Talend Enterprise ESB Server before starting this chapter.
This chapter details the procedures required to install each part of Talend Enterprise ESB.
The following parts usually need to be installed in the following order:
1. SVN Server, see Section 3.1, Setting up your project server on SVN
2. Tomcat, see Section 3.2.1, Deploying the Web application on Tomcat
3. Administration center Web application, see Section 3.3, Configuring Talend Administration Center (Web
application)
4. Talend ESB, see Section 3.4, Installing and configuring Talend ESB
5. Talend Artifact Repository, see Section 3.5, Installing and configuring Talend Artifact Repository.
6. Talend Runtime, see Section 3.6, Installing Talend Runtime
7. JBoss Business Rules Management System, see Section 3.7, Installing a Business Rules Management System
(Drools)
8. Automatic log purge (optional), see Section 3.8, Setting up the automatic log purge (optional)
In the following documentation, <TomcatPath> designates the Tomcats installation path and
<ApplicationPath> designates the directory in <TomcatPath>/Webapps where Talend Administration
Center war file has been deployed.

Talend Enterprise ESB Installation Guide

Setting up your project server on SVN

3.1. Setting up your project server on SVN


This section describes how to install the SVN server. This server will store all your project data (Jobs, Database
connections, Routines, Joblets, etc.).
The installation instructions for Subversion will differ depending on:
your development environment,
the access method,
the authentication mode.
The access methods and authentication modes to the Subversion server include:
Apache is a Web server and can be used to access a Subversion repository. Only the authenticated access is
documented here.
Note that VisualSVN has both Apache and Subversion embedded
SSH is another method for accessing a Subversion repository. Authentication is mandatory and brings a higher
level of security thanks to encrypted communication.
Choose the procedure that is most relevant to your environment among the following instruction sections. These
sections are independent from each other.

3.1.1. Windows
1.

Download the SVN server installer, for example: http://www.visualsvn.com/server/download/

2.

Launch the wizard.

3.

Clear the Use secure connection (https://) check box so that you use unsecured HTTP.

4.

Complete the installation process without changing the other parameters.

5.

Launch VisualSVN.

In the main window of VisualSVN Server Manager:


Check in the server URL that the port is 80, if not then perform the following operation:
1.

Right-click on VisualSVN Server on the left tree view.

2.

Select Properties.

3.

Click on the Network tab.

4.

Change the port selection to 80.

5.

Click Apply then OK.

Then create a new repository:


1.

Right-click on Repositories in the main window of VisualSVN.

2.

Click Create new repository...

3.

Name the repository newly created, for example: <repotis>.

18

Talend Enterprise ESB Installation Guide

Debian, apache

4.

Click OK.

Having done this, create a new user:


1.

Click Create new user... in the main window of VisualSVN.

2.

Then define a user name and his password.

Then grant read-write authorization to this user:


1.

Right-click on <repotis>.

2.

Select Properties.

3.

Change the default user (everyone) permissions to no access.

4.

Click Add.

5.

Select your username in the list displaying and click OK.

6.

Check that the granted permissions are read/write.

Your SVN server is now installed and the repository is ready to store all Talend Enterprise ESB projects.
One thing left to do is to link Talend Administration Center to this newly created repository.
In VisualSVN:
1.

Right-click on your new repository: <repotis>.

2.

Select Copy URL to Clipboard.

This copied URL is to be used along with the username and password when you configure the Talend
Administration Center application (see Section 3.3.1, Configuring the Web application access).
The SVN URL should read:
http://host_or_ip_address:port80/svn/repository_name
such as: http://talend-esa.talend.com:80/svn/repotis/

3.1.2. Debian, apache


In the following instructions, lines starting with "#" mean that they must be executed as root. A command line
starting with "$" means that it must be executed as standard user.
# apt-get install subversion apache2 libapache2-svn
# mkdir /svn
# chown www-data:www-data /svn
Switch to webserver user, which is www-data by default on Debian systems.
# su - www-data
$ svnadmin create /svn/repotis
$ htpasswd -cmb /svn/passwd tisadmin secretpassword

Talend Enterprise ESB Installation Guide

19

Debian, ssh

# vi /etc/apache2/sites-available/default
<Location /repotis>
DAV svn
SVNPath /svn/repotis
AuthUserFile /svn/passwd
Require valid-user
AuthType basic
AuthName "Subversion"
</Location>
# /etc/init.d/apache2 restart
Your SVN server is now installed and the repository is ready to store Talend Enterprise ESB projects.
One thing left to do is to link Talend Administration Center to this newly created repository.
You will need the URL as well as the username and password of your newly created SVN when configuring
Talend Administration Center (see Section 3.3.1, Configuring the Web application access).
The URL syntax should read: http://host_or_ip_address/repotis/project_name.
For example:
http://10.42.0.10/repotis/first_project
http://tisserver/repotis/another_project
Then give the user tisadmin, password secretpassword as described in the passwd file.

3.1.3. Debian, ssh


You can start with the following line:
# apt-get install ssh subversion
Create a user "tisadmin" with password "secretpassword".
# adduser tisadmin
# mkdir /svn
# chown tisadmin:tisadmin /svn
Switch to tisadmin user.

20

Talend Enterprise ESB Installation Guide

Redhat (Fedora), Apache

# su - tisadmin
$ svnadmin create /svn/repotis
Your SVN server is now installed and the repository is ready to store Talend Enterprise ESB projects.
One thing left to do is to link Talend Administration Center to this newly created repository.
You will need the URL as well as the username and password of your newly created SVN when configuring
Talend Administration Center (See Section 3.3.1, Configuring the Web application access).
The URL syntax should read:
svn+ssh://tisadmin@host_or_ip_address/svn/repotis/project_name.
For example:
svn+ssh://tisadmin@10.42.0.10/svn/repotis/first_project
svn+ssh://tisadmin@tisserver/svn/repotis/another_project
Then give the user "tisadmin", password "secretpassword".

3.1.4. Redhat (Fedora), Apache


As User: apache
-ORAs Root
# yum install httpd mod_dav_svn
The above command installs the following:
- httpd-2.2.9-1.fc9.i386.rpm
- mod_dav_svn.i386 0:1.4.6-7
- subversion.i386 0:1.4.6-7
# mkdir /var/www/svn
# svnadmin create /var/www/svn/repository
# htpasswd -cmb /var/www/svn/passwd admin@company.com admin
# chown -R apache.apache /var/www/svn
# vim /etc/httpd/conf.d/subversion.conf
Add:
<Location /svn>
DAV svn
SVNPath /var/www/svn/repository
Require valid-user

Talend Enterprise ESB Installation Guide

21

Mac OS X

AuthType basic
AuthName "Subversion"
AuthUserFile /var/www/svn/passwd
</Location>
# /etc/init.d/httpd start

3.1.5. Mac OS X
1.

Download the SVN server installer, for example Bitnami Subversion Stack at http://bitnami.org/stack/
subversion.

2.

Install it in the Apllications/Utilities directory.


Choose a port according to your environment. The default port 8080 clashes with Talend
Administration Center.

3.

Launch Bitnami in a terminal.


It will provide a step-by-step wizard.

In Bitnami, during the setup:


1.

Create a new repository and name it <repotis>.

2.

Create a new user and define his user name and password.

3.

Grant read-write authorization to this user.


Your SVN server is now installed and the repository is ready to store all Talend Enterprise ESB projects.
One thing left to do is to link Talend Administration Center to this newly created repository.

4.

Copy the URL of your new <repotis> repository.


This copied URL is to be used along with the username and password when you configure the Talend
Administration Center application (see Section 3.3.1, Configuring the Web application access).

22

Talend Enterprise ESB Installation Guide

Deploying the Web application on an application server

For more information, please refer to the Bitnami Subversion Stack documentation. We recommend
that you use Bitnami to create repositories and users, as it is a preconfigured stack, but you also have
the possibility to install Subversion server manually on your Mac OS X.

3.2. Deploying the Web application on an


application server
This section shows how to deploy the Web application on an application server; it can be an Apache Tomcat or
a JBoss server application.

3.2.1. Deploying the Web application on Tomcat


First, install the Apache Tomcat application server and stop the Tomcat service if it is automatically started.
In the rest of this documentation, <TomcatPath> points out the path where Tomcat has been installed.
Indeed we recommend you
(org.talend.administrator.war).

to

stop

this

service

prior

to

deploying

the

Web

application

Using 7zip:
1.

Unzip the package delivered by Talend: Talend-AdministrationCenter-rYYYYY-VA.B.C.


This will give you access to the different components needed to benefit from all the Talend Administration
Center functionalities:
org.talend.administrator.war, the archive containing the actual Talend Administration Center Web
application.
Talend-Artifact-Repository-VA.B.C.zip, the archive containing an artifact repository software, based on
Apache Archiva, that will be used to handle software updates, and also ESB artifacts, only if you subscribed
to one of our ESB oriented solutions. For more information, see Section 2.2, Detailed introduction to
Talend Enterprise ESB Server.
an endorsed folder containing a library necessary to use the ESB Conductor of Talend Administration
Center, only if you subscribed to one of our ESB oriented solutions.

2.

Unzip the Web application, org.talend.administrator.war, into the following directory of Tomcat:
<TomcatPath>/webapps/.

3.

If you subscribed to one of our ESB oriented solutions, to be able to use the ESB Conductor module of Talend
Administration Center, copy the endorsed folder provided into the root directory of Tomcat.

On Linux:
1.

Edit the following file:


etc/default/tomcat6

2.

and uncomment the tomcat security setting and change the default setting, in order to read:
#TOMCAT6_SECURITY=no

Talend Enterprise ESB Installation Guide

23

Deploying the Web application on JBoss

The storage of log outputs is managed by Tomcat application server, by default, but you are also able
to define your own path for storing the logs. From 4.0, you can configure the path directly from Talend
Administration Center. In prior versions, refer to Section 3.2.3, Log storage mode for more information
on manual configuration.
Then start Tomcat using the following commands:
Linux

Windows

Start the Tomcat service

sh <TomcatPath>/bin/startup.sh

net start Apache Tomcat

Stop the Tomcat service

sh <TomcatPath>/bin/shutdown.sh

net stop Apache Tomcat

For reasons of right management, make sure you launch Tomcat using the same administrator account
as for the Commandline. E.g.: Create an account TISAdmin for both Tomcat and Commandline.
If you deploy a large number of applications on Tomcat, you should increase its memory to improve its
performance. For more information on this process, see section about Tomcat server configuration in
Talend Enterprise Installer User Guide.

3.2.2. Deploying the Web application on JBoss


First, install the JBoss application server and stop the JBoss service if it is automatically started.
In the rest of this documentation, <JBossPath> points out the path where JBoss has been installed.
Indeed we recommend you
(org.talend.administrator.war).

to

stop

this

service

prior

to

deploying

the

Web

application

1.

Using 7zip, unzip the archive delivered by Talend.

2.

Manually change the file extension from org.talend.administrator.war to org.talend.administrator.zip.

3.

Unzip the file to an org.talend.administrator folder into the following directory:


<JBossPath>/server/default/deploy/
The storage of log outputs is managed by JBoss application server, by default, but you are also able to
define your own path for storing the logs. From 4.0, you can configure the path directly from Talend
Administration Center. In prior versions, refer to Section 3.2.3, Log storage mode for more information
on manual configuration.

Then start JBoss using the following commands:


Linux

Windows

Start the JBoss service

sh <JBossPath>/bin/run.sh

net start JBoss

Stop the JBoss service

sh <JBossPath>/bin/shutdown.sh

net stop JBoss

For reasons of right management, make sure you launch JBoss using the same administrator account as
for the Commandline. E.g.: Create an account TISAdmin for both JBoss and Commandline.

3.2.3. Log storage mode


The log outputs are stored by default in the server application standard log file (STDOUT) as defined in the
Log4j.xml file. However you can store the log in a different file by setting the path to this file in the Log4j.xml file.

24

Talend Enterprise ESB Installation Guide

Configuring Talend Administration Center (Web application)

To do so, simply set the path in the Configuration page in Talend Administration Center. For more information,
refer to your Talend Administration Center User Guide.
If you leave the Path field blank in the Configuration page, then you can also customize the Log4j.xml to address
your custom needs.

3.3. Configuring Talend Administration


Center (Web application)
Talend Administration Center is a Web-based administration application that allows Talend Enterprise ESB Studio
project managers to administrate users and projects and manage access to the remote repository.
You can configure the way Talend Administration Center will operate directly from its Web interface, especially
you need to link Talend Administration Center to the shared Repository (stored on SVN). This server stores all
your project data.
For more details, see Section 3.3.1, Configuring the Web application access.
Choose a port according to your environment. The default port 8080 clashes with Talend Enterprise ESB.
If needed, you can also configure the connection pool to be managed via Tomcat. However this advanced
configuration mode cannot be done through the Web interface of Talend Administration Center.
For more details, see Section 3.3.2, Managing the connection pool via Tomcat.

3.3.1. Configuring the Web application access


The recommended way to configure the connection to the database and to the shared repository (SVN) is through
the Web interface of Talend Administration Center.
1.

Open a Web browser (Internet Explorer, Firefox, etc.) and type in the following URL: http://localhost:8080/
<ApplicationPath>.
Replace <localhost> with the IP address or the hostname of the Web server if the Web browser IP is different
from the machine you are on and <ApplicationPath> with the Talend Administration Center Web application
path.
For example, http://localhost:8080/org.talend.administrator.
When connecting for the first time, a dialog box displays asking you the password to access the Database
Configuration page:

2.

Type in the default admin password.


H2 database connection parameters display and some automatic checks are performed on driver, url,
connection, version information.
The administration database (storing users, rights, etc.) being an H2 embedded database, its access
information is automatically set. However, if you do not want to use the embedded H2 database, you
can set up a database server (MySQL, MSSQL or Oracle) in which case, set the required parameters.

3.

Click Set new license.


Talend Enterprise ESB Installation Guide

25

Managing the connection pool via Tomcat

4.

Browse your system to the License file you received from Talend and click Upload. A final License check
is performed.

5.

Click Go to Login.

6.

On the Login page, type in the default connection login for your first access:
Default login: admin@company.com,
Default password: admin.
Those credentials correspond to the default user of the Web application. You can create a new one via the
Users menu in Talend Administration Center, and then delete the admin@company.com user after you
are connected using the newly created user login.
If your Web access is restricted, you may need to click Generate Validation request to perform the
validation of your license key. Follow the instructions on screen.

Once the license is validated, the navigation bar of Talend Administration Center opens with all the pages
accessible for the default administrator user account. For more information on which pages of Talend
Administration Center an administrator user can access, see the Talend Administration Center User Guide.
You can now configure the link to the shared repository (SVN):
1.

Click Configuration to access the setting page of Talend Administration Center.

2.

Change the following parameters for the SVN module using the parameters you have set during the
installation process of the SVN server.
- Server Location URL: your <repotis> SVN URL.
- Username: your <repotis> user.
- Password: your <repotis> SVN password.

For examples of SVN URLs, and more details, see Section 3.1, Setting up your project server on SVN, and
Section 3.1.1, Windows, Section 3.1.2, Debian, apache, Section 3.1.3, Debian, ssh.
If you use several SVN repositories to store your projects, refer to the User Guide of Talend Administration
Center and check the Advanced settings procedure.
The link to the SVN is now established, you can thus create a new project in order for the Talend Enterprise ESB
clients to have at least one project in their workspace. To do so, you have to:
1.

Create one or more users from the Users page;

2.

Create a new, remote, collaborative project from the Projects page;

3.

Associate the user(s) with the project from the Project Authorizations page.

For more details on how to add a project in Talend Administration Center, see the Talend Administration Center
User Guide.

3.3.2. Managing the connection pool via Tomcat


By default, a third-party application (c3p0) has been embedded into the configuration file of Talend Administration
Center, to manage the connection pool.
However if you want Tomcat to manage directly the connection pool, perform the following operations:

26

Talend Enterprise ESB Installation Guide

Advanced configuration

In the Web application installation directory, proceed as follows:


1.

In the <ApplicationPath>/WEB-INF/Classes folder, edit the configuration.properties file:


Change the default setting to: database.useContext=True

2.

In the WEB-INF folder, edit the web.xml file:


Uncomment the following piece of code (at the end of the file), to make it read as follows:
<resource-ref>
<description>Our Datasource</description>
<res-ref-name>jdbc/ADMINISTRATOR_CONNECTION</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

3.

In the file <ApplicationPath>/META-INF/context.xml, set the fields as follows:


Configure the parameters of connection to the database.
schema name= talend_administrator
server= localhost or IP of the server on which the database is
installed
login= tisadmin or your login for MySQL
password= tisadmin or your password for MySQL
driverClassName="org.gjt.mm.mysql.Driver" (for MySQL DB)
url="jdbc:mysql://<host>:3306/talend_administrator" (for MySQL
DB)

4.

Copy over the following .jar file from <ApplicationPath>/WEB-INF/lib to <TomcatPath>/lib/ in case your
administration data are stored in MySQL:
mysql-connector-java-5.1.3-bin.jar

5.

In case your data are stored in a different database, copy the relevant .jar in <TomcatPath>/lib/.
In this case, the DB config page of the Web application will not be operating.
You can also deploy Talend Web application on a JBoss application server (instead of a Tomcat). So,
you can follow the same above instructions for Jboss. From more information on how to deploy the Web
application on JBoss, see Section 3.2.2, Deploying the Web application on JBoss.

3.3.3. Advanced configuration


You can fine-tune the usage parameters for the various Talend Enterprise ESB modules to address your particular
needs.
To access the advanced parameter configuration, edit the following file:
<ApplicationPath>/WEB-INF/classes/configuration.properties

Talend Enterprise ESB Installation Guide

27

Installing and configuring Talend ESB

For example the following parameters help you change the default credentials:
install.defaultaccount.login=admin@company.com
install.defaultaccount.password=admin
install.defaultaccount.firstname=admin
install.defaultaccount.lastname=admin

3.4. Installing and configuring Talend ESB


Talend ESB is provided to you throught a zip file named Talend-ESB-VA.B.C. To install Talend ESB on your
server machines, unzip the Talend-ESB-VA.B.C.zip file.
Talend ESB package contains the following ready-to-be-used tools:
Talend ESB Container (based on Apache Karaf)
Apache ActiveMQ
Service Locator (based on Apache Zookeeper)
Service Activity Monitoring
Security Token Service

3.4.1. Accessing Talend ESB Container


Once Talend ESB installed, you can access Talend ESB Container in the Talend-ESB-VA.B.C/container directory.
Talend ESB Container is an OSGI container, based on Apache Karaf, allowing you to deploy and execute various
components and applications inside its Talend-ESB-VA.B.C/container/deploy folder.
To launch Talend ESB Container:
1. Browse to the Talend-ESB-VA.B.C/container/bin directory.
2. Run the trun.bat file on Windows and the trun file on Linux.
After starting Talend ESB Container, you need to wait a few seconds for initialization to complete before
entering the commands. Karaf, on which the Talend ESB Container is built, starts the non core bundles
in background. So even if the console is already available, the commands may not.
For more information on Talend ESB Container usage, see Talend ESB Container Administrator's Guide.
Once Talend ESB Container installed and launched, you will be able to install all the other components available
in the Talend ESB package as features directly in the container. Thus, when launching Talend ESB Container, all
the other components will be launched at the same time.
When installing Talend ESB components as features in the container, you might encounter memory
problems. For more information on how to increase the memory allocation of the container, see Talend
ESB Container Administrator's Guide.
This implementation can ease the management of Talend ESB but if you want to create a cluster environment, you
will need to replicate the container to have several containers with the right components installed as features in it,
whereas if you are using the different components as standalone you will only have to duplicate the corresponding
instance.

28

Talend Enterprise ESB Installation Guide

Installing Apache ActiveMQ

If you only want to use several basic containers, you can also use Talend Runtime, as Talend Runtime is the exact
equivalent of the container folder provided in Talend Enterprise ESB. For more information about the installation
of Talend Runtime, see Section 3.6, Installing Talend Runtime.

3.4.1.1. Configuring the container parameters


To customize the Talend ESB Container:
1. Go to the following directory: Talend-ESB-VA.B.C/container/etc.
2. Edit the following files for example:
org.ops4j.pax.url.mvn.cfg, to change the HTTP listening port.
org.apache.karaf.management.cfg, to manage RMI connection to connect to Talend ESB Container via JMX
in order to manage and supervise each of its component and their activity from a JConsole, for example.

3.4.2. Installing Apache ActiveMQ


ActiveMQ is a message broker enabling to support different messaging options. It will provide you high
availability, performance, scalability, reliability and security for enterprise messaging. And it allows you to
mediate events between distributed applications, guaranteeing that they reach their intended recipients.
Once Talend ESB installed, you can either access a standalone instance of ActiveMQ in the Talend-ESB-VA.B.C/
activemq directory or install it as a feature directly within the Talend ESB Container.
Once installed, ActiveMQ can be used in Talend's Mediation routes, for example.

3.4.2.1. As standalone
To launch ActiveMQ in standalone:
1. Browse to the Talend-ESB-VA.B.C/activemq/bin directory.
2. Run the activemq.bat file on Windows and type in the following command on Linux and MacOS: ./
activemq console.

3.4.2.2. As an OSGi feature


ActiveMQ can also be installed as a feature in Talend ESB Container, this way, it will be automatically launched
when launching Talend ESB Container.
By default, ActiveMQ is activated. To check that the activemq bundles are activated, use the list | grep
activemq command.
To launch ActiveMQ as a feature in Talend ESB Container:
1. Run the Container.
2. Type in the following command to install the war feature allowing you to install features from war files:
install war.

Talend Enterprise ESB Installation Guide

29

Accessing Service Locator

3. Type in the following command to install the ActiveMQ feature: features:install activemq-webconsole.
When installing ActiveMQ as a feature in Talend ESB Container, a message broker will automatically
created by default.

3.4.3. Accessing Service Locator


Service Locator provides automatic and transparent failover and load balancing between service Consumers and
Providers and allows for dynamic endpoint registration and lookup.
Once Talend ESB installed, you can access the Service Locator in the Talend-ESB-VA.B.C/zookeeper directory
or install it as a feature directly within the Talend ESB Container.

3.4.3.1. As an OSGi feature (Recommended)


Service Locator can also be installed as a feature in Talend ESB Container, this way, it will be automatically
launched when launching Talend ESB Container.
To launch Service Locator as a feature in Talend ESB Container:
1. Run the Container.
2. Type in the following command to start the feature corresponding to Service Locator: tesb:startlocator.
3. To stop the Service Locator, type in the following command: tesb:stop-locator.

3.4.3.2. As standalone (Alternative)


To launch Service Locator in standalone:
1. Open a command window.
2. Browse to the Talend-ESB-VA.B.C/zookeeper/bin directory.
3. Run the following command:
zkServer.cmd start on Windows.
zkServer.sh start on Linux.
Under Linux, ensure execution rights for the locator startup scripts:
chmod a+x zookeeper/bin/*.sh
To customize the configuration of the Service Locator standalone, edit the following file: Talend-ESB-VA.B.C/
zookeeper/conf/zoo.cfg and change the parameters according to your needs:
Field name

Description

tickTime

the basic time unit in milliseconds used by the Service Locator. It is


used to do heartbeats, and the minimum session timeout will be twice
the tickTime

30

Talend Enterprise ESB Installation Guide

Installing Service Activity Monitoring

Field name

Description

dataDir

the location to store the in-memory database snapshots and, unless


specified otherwise, the transaction log of updates to the database

clientPort

the port to listen for client connections

3.4.4. Installing Service Activity Monitoring


Service Activity Monitoring (SAM) facilitates the capture of analysis of service activity, including service
response times, traffic patterns, auditing and more, by capturing events and storing information. This component
consists of two parts:
Agents (sam-agent) which gather and send monitoring data
A monitoring Server (sam-server) which processes and stores the data
The sequence of how these are used is as follows:
1. The Agent creates events out of requests and replies from both the service consumer and provider side.
2. The events are first collected locally and then sent to the Monitoring Server periodically (so as not to disturb
the normal message flow).
3. When the Monitoring Server receives events from the Agent, it optionally uses filters and/or handlers on those
events and stores them into a database.
The Agent and Monitoring Service are made available as follows:
The agent is by default installed as a feature in Talend ESB Container.
The Monitoring Server needs to be installed into a Servlet Container (Tomcat) or an OSGi Container (Talend
ESB Container) and needs access to a database.
Once Talend ESB installed, you can access the Service Activity Monitoring server in the Talend-ESB-VA.B.C/
add-ons/sam directory to install it or directly install it as a feature within the Talend ESB Container.

3.4.4.1. Prerequisite to the Monitoring Server


The Monitoring Server requires a database engine to store Events data. The supported databases are listed in
Section 1.7, Compatible Databases.
The following are the script files corresponding to the databases, run them to configure the database properly. You
can find the SQL scripts in the Talend-ESB-VA.B.C/add-ons/sam/db directory.
SQL script filename

Database

create.sql

Apache Derby

create_mysql.sql

MySQL

create_oracle.sql

Oracle

create_sqlserver.sql

SQL Server

create_h2.sql

H2 Database Engine

create_db2.sql

IBM DB2

Talend Enterprise ESB Installation Guide

31

Installing Service Activity Monitoring

1. Make sure your chosen database is installed properly and is accessible.


2. Login with a user which has CREATE permissions.
3. Run the init SQL script for the corresponding database from the table above.
If the value of db.recreate property in the logserver.properties is set to true, the init SQL script will be
executed automatically when starting the Monitoring Server. But this is not recommended for any database
except Apache Derby running in embedded mode.
You will then find the EVENTS and EVENTS_CUSTOMINFO table have been created in your database.
Now, you can install the Monitoring server either in standalone or as a feature in the Talend ESB Container.

3.4.4.2. As Web application (Recommended)


To install the Service Activity Monitoring server as Web application, you need to deploy it in an Servlet Container.
1.

Deployment into Apache Tomcat, for example:


1. Copy the sam-server-war.war file of the Talend-ESB-VA.B.C/add-ons/sam directory.
2. Paste it in the <TomcatPath>/webapps directory.
The next time you will start Tomcat, the Sam Server application will automatically be deployed on the
server.
To do it in command line, you can use the following commands:
copy Talend-ESB-VA.B.C\add-ons\sam\sam-server-war.war <TomcatPath>\webapps for Windows
cp Talend-ESB-VA.B.C/add-ons/sam/sam-server-war.war <TomcatPath>/webapps for Linux
You can check whether the Sam Server has been successfully installed and is running by going to the
following URL: http://localhost:8080/sam-server-war/
"http://localhost:8080/sam-server-war" is only given as example. Depending on your configuration,
you may have to replace <localhost> with the IP address of the Web server and <8080> with the
actual port used for the application.

2.

Configure the database connection information in the Monitoring Server:


1. Go to <TomcatPath>/webapps/sam-server-war/WEB-INF.
2. Edit the logserver.properties file.
3. Configure the database.

3.

Now, configure the Monitoring endpoint in the Talend ESB Container. To do so:
1. In the Service Activity Monitoring Server page available at http://localhost:8080/sam-server-war/, click
the services link.
2. In the services page, copy the Endpoint address, for example: http://localhost:8080/sam-server-war/
services/MonitoringServiceSOAP
3. Go to Talend ESB Container configuration directory: Talend-ESB-VA.B.C/container/etc to configure its
Sam agent with the right Monitoring endpoint.
4. Edit the org.talend.esb.sam.agent.cfg.

32

Talend Enterprise ESB Installation Guide

Installing Security Token Services

5. Replace the service.url field with the new Endpoint address.

3.4.4.3. As an OSGi feature (Alternative)


Service Activity Monitoring server can also be installed as a feature in Talend ESB Container, this way, it will be
automatically launched when launching Talend ESB Container.
To launch Service Activity Monitoring as a feature in Talend ESB Container:
1. Run the Container.
2. Type in the following command to start the SAM server feature: tesb:start-sam.
3. To stop the Service Locator, type in the following command: tesb:stop-sam.
If you install the Service Activity Monitoring server as an OSGi feature within the Talend ESB Container,
you will only be able to use an Apache Derby database, also included in the container and automatically
started with the tesb:start-sam command. If you want to use one of the other supported databases,
use the Tomcat Web Application installation of the Service Activity Monitoring server.

3.4.5. Installing Security Token Services


An informal description of a Security Token Service is that it is a web service that offers some or all of the
following services (among others):
It can issue a Security Token of some sort based on presented or configured credentials.
It can say whether a given Security Token is valid or not.
It can renew (extend the validity of) a given Security Token.
It can cancel (remove the validity of) a given Security Token.
It can transform a given Security Token into a Security Token of a different sort.
Offloading this functionality to another service greatly simplifies client and service provider functionality, as they
can simply call the STS appropriately rather than have to handle the security processing logic themselves. For
example, the WSDL of a service provider might state that a particular type of security token is required to access
the service. Then:
1. A client of the service can ask an STS for a Security Token of that particular type, which is then sent to the
service provider.
2. The service provider could choose to validate the received token locally, or dispatch the token to an STS for
validation.
These are the two most common use cases of an STS.

3.4.5.1. Run STS server as feature in container (Recommended)


To enable the STS server feature in the Karaf container, execute the following command:

Talend Enterprise ESB Installation Guide

33

Installing and configuring Talend Artifact Repository

tesb:start-sts
The STS service will start automatically. To make sure that it is running, execute the following command in the
console:
list
and find two additional bundles: Apache CXF STS Core and Talend :: ESB :: STS :: CONFIG which enable the
STS functionality.
It is normal that the status of this (fragment) bundle is only Resolved and not Active, as the other one.
Sample keys distributed with the RentACar demo should not be used in production. For more information
on how to replace the keys used, see "Chapter 5. Security Token Service Installation" from "Talend ESB
Runtime Configuration Guide".
For additional information about the usage of STS, please read the "Talend ESB STS User's Guide" and "Chapter
5. Security Token Service Installation" from "Talend ESB Runtime Configuration Guide".

3.4.5.2. Run STS server as Web application (Alternative)


The STS war file is located at add-ons/sts/SecurityTokenService.war of the distributive directory and ready for
deployment on Tomcat.
For the STS war file deployment, please use standard deployment instructions for your J2EE container
(Deployment guide for Tomcat 7: http://tomcat.apache.org/tomcat-7.0-doc/deployer-howto.html ) and read
"Chapter 5. Security Token Service Installation" from "Talend ESB Runtime Configuration Guide".
Sample keys distributed with the RentACar demo should not be used in production. For more information
on how to replace the keys used, see "Chapter 5. Security Token Service Installation" from "Talend ESB
Runtime Configuration Guide".

3.5. Installing and configuring Talend Artifact


Repository
Talend Administration Center is provided together with an artifact repository based on Apache Archiva and
customized to be used with Talend Enterprise ESB. This Talend tool is used for the Software Update feature and
its instance holds two dedicated repositories: talend-update-admin where the updates are uploaded and talendupdate-user where the updates are retrieved by the user. It is also used for the Provisioning repository as a catalog
for the Services, Routes, Jobs and Generic OSGi features created from Talend Enterprise ESB Studio or any other
Java IDE. For this, two other 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 display the updates on versions and patches available for download. And it also allows to store ESB artifacts
designed from Talend Enterprise ESB Studio or any other Java IDE and ready to be deployed and executed in
Talend Runtime. 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 Talend-Artifactrepository-VA.B.C containing an artifact repository software that will be used to handle software updates and ESB
artifacts.
To obtain a preconfigured and ready-to-be-used artifact repository, unzip it to the directory of your choice.

34

Talend Enterprise ESB Installation Guide

Configuration for the Software Update repository

By default, the Talend Artifact Repository starts at TCP Port 8082 but you have the possibility to change
the default port of the repository by editing the corresponding line of the jetty.xml file located in the conf
folder of this directory.
To launch Talend Artifact Repository:
1.

From a commandline window, browse to the bin directory of Talend-Artifact-Repository-VA.B.C.

2.

On Windows, run the archiva.bat console command to run it interactively (in this case, press Ctrl+C
in the console to later stop the server)
or, if you have previously installed the artifact repository as a Windows service, run the archiva.bat
start command to run it in the background (in this case, run the stop command to later stop the server).
On Linux, run the archiva.sh console command to run it interactively (in this case, press Ctrl+C in
the console to later stop the server)
or, if you have previously installed the repository manager as a Linux service, run the archiva.sh start
command to run it in the background (in this case, run the stop command to later stop the server).

3.5.1. Configuration for the Software Update repository


Once you installed the Talend Artifact Repository and started it, you can configure it to use Talend Software
Update.

3.5.1.1. Repository configuration


To configure Talend Software Update, open your Web browser and type in the URL to your instance of Talend
Artifact Repository, http://localhost:8082/archiva for example, then proceed as follows:
"http://localhost:8082/archiva" is only given as example. Depending on your configuration, you may have
to replace <localhost> with the IP address of the Web server and <8082> with the port that is used for
your repository instance.
1.

Log in with the following credentials:


Username

Password

admin

1q2w3e4r
By default, password expiration in the repository is set to false, but you have the possibility to
enable it. To do so, open the <TalendArtifactRepositoryPath>/conf/security.properties file and set
the password.expiration parameter to true. To define how long the password is valid, edit
the value of the security.policy.password.expiration.days parameter according to
your needs.

2.

Click Repositories on the menu tree view.

3.

Edit the remote repository named talend-update-admin-remote. To do so:


Click Edit to the right of the repository.
Fill in the Username and Password fields with the credentials provided with your licence key in the email
sent by Talend (different for each user).
Save these changes by clicking Update Repository.

Talend Enterprise ESB Installation Guide

35

Configuration for the Provisioning repository

3.5.1.2. Configuration in Talend Administration Center Web


application
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:
Repository URL: Type in the location URL to your software update repository, http://localhost:8082/archiva/
for example.
"http://localhost:8082/archiva" is only given as example. Depending on your configuration, you may
have to replace <localhost> with the IP address of the Web server and <8082> with the actual port
used for your repository instance.
Admin username: Type in the name of the repository user with Manager role. By default, it is
SoftwareUpdateAdmin.
Admin password: Type in the password of the repository user with Manager role. By default, it is
SoftwareUpdateAdmin.
Reader username: Type in the name of the repository user with Observer role. By default, it is
SoftwareUpdateReader.
Reader password: Type in the password of the repository user with Observer role. By default, it is
SoftwareUpdateReader.
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.

3.5.2. Configuration for the Provisioning repository


Once you installed the Talend Artifact Repository and started it, you can configure it to use the Provisioning
repository.

3.5.2.1. Accessing the repository


To access the Provisioning repository, open your Web browser and type in the URL to your instance of Talend
Artifact Repository, http://localhost:8082/archiva for example, then proceed as follows:
"http://localhost:8082/archiva" is only given as example. Depending on your configuration, you may have
to replace <localhost> with the IP address of the Web server and <8082> with the port that is used for
your repository instance.
1.

Log in with the following credentials:


Username

Password

tadmin

tadmin
By default, password expiration in the repository is set to false, but you have the possibility to
enable it. To do so, open the <TalendArtifactRepositoryPath>/conf/security.properties file and set
the password.expiration parameter to true. To define how long the password is valid, edit
the value of the security.policy.password.expiration.days parameter according to
your needs.

36

Talend Enterprise ESB Installation Guide

Installing Talend Runtime

2.

Click Repositories on the menu tree view.


The two repositories repo-snapshot and repo-release display.
By default, these repositories are preconfigured to work with the Talend Enterprise ESB Studio but you
can add more repositories or reconfigure the given repositories according to your needs.

3.5.2.2. Configuration in Talend Administration Center Web


application
Once you have launched the Provisioning repository, go to the Configuration page of Talend Administration
Center and fill in the following information in the Conductor group:
Artifact repository url: Type in the location URL to your Artifact repository, http://localhost:8082/archiva/
for example.
"http://localhost:8082/archiva" is only given as example. Depending on your configuration, you may
have to replace <localhost> with the IP address of the Web server and <8082> with the actual port
used for your repository instance.
Artifact repository username: Type in the name of the repository user with Manager role. By default, it is
tadmin.
Artifact repository password: Type in the password of the repository user with Manager role. By default, it
is tadmin.
In Talend Enterprise ESB Studio, you can now configure the access to your Talend Artifact Repository in its
Preferences and publish your Services, Routes and Jobs into the two repositories according to your need. For
more information, see Talend Enterprise ESB Studio User Guide.
In the ESB Conductor page of Talend Administration Center, you can retrieve all the artifacts published in the two
repositories to configure their execution into Talend Runtime. For more information, see Talend Administration
Center User Guide.

3.6. Installing Talend Runtime


Talend Runtime is an OSGi container, based on Apache Karaf, allowing you to deploy and execute various
components and applications inside its deploy folder or via remote repositories (for example, standard Maven
Repositories like the Talend Artifact Repository). It can be used as an execution server to deploy and execute all the
Services, Routes and Generic OSGi Features created from Talend Enterprise ESB Studio or any other Java IDE.

3.6.1. 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 Enterprise ESB.
The archive file name for example reads: Talend-Runtime-V5.0.1.zip

Talend Enterprise ESB Installation Guide

37

Installing the Talend Runtime containers

3. In the unzipped file you might need to configure the files org.ops4j.pax.url.mvn.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. You can also change the
configuration in the configure files in the Talend-Runtime-VA.B.C/scripts directory. For more information on
these files, see the Talend ESB Getting Started Guide..
4. To launch Talend Runtime, browse to the bin directory and run the trun.bat file on Windows and the trun file
on Linux.
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.
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. tadmin by default.

Password

Type in the password for user authentication to access a Job


server. tadmin by default.

Active

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

Use SSL

Select/clear the check box to use your own SSL Keystore to


encrypt the data prior to transmission.
For further information about creating and enabling an SSL
Keystore, see Talend Integration Suite Installation Guide.

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 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

38

Talend Enterprise ESB Installation Guide

Installing a Business Rules Management System (Drools)

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 appear with their properties.

3.7. Installing a Business Rules Management


System (Drools)
A dedicated .war file has been delivered to you in the Talend archive.
Unzip the drools-guvnor.war file in:
<TomcatPath>/webapps/
After deploying the Drools BRMS, you will need to configure its URL in the Talend Administration Center
Web application Configuration page. For more information about configuring the Web application, first read the
Section 3.3, Configuring Talend Administration Center (Web application).
Then after you access Talend Administration Centers Configuration page, set Drools Guvnors URL, http://
localhost:8080/drools-guvnor 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:

3.8. Setting up the automatic log purge


(optional)
When deploying and executing tasks using the Job Conductor in Talend Administration Center, multiple files are
created and stored locally.
These files include the Job archives (before deploying over job servers), execution & recovery logs, deployment
logs.
You can configure Talend Administration Center to get rid of these legacy files when they are not used anymore:
1.

Edit the configuration file of Talend Administration Center:


<ApplicationPath>/WEB-INF/classes/configuration.properties

Talend Enterprise ESB Installation Guide

39

Setting up the automatic log purge (optional)

2.

Set the following parameters:


### Temporary data cleaning parameters ###
# Time in seconds between each cleaning action, set with 0 to disable
all cleanings
scheduler.conf.cleaning.frequencyCleaningAction=600
# Time in seconds before cleaning executions logs from the current
date,
3 months=3*30*24*60*60=7776000, set with 0 to disable delete action
with this method
scheduler.conf.cleaning.maxDurationBeforeCleaningOldExecutionsLogs=7776000
# Max executions logs to keep, set with 0 to disable delete action with
this method.
scheduler.conf.cleaning.maxOldExecutionsLogs=1000
# Time in seconds before cleaning archives jobs from the current date,
3 months=*30*24*60*60=7776000,
set with 0 to disable delete action with this method
scheduler.conf.cleaning.maxDurationBeforeCleaningOldJobs=7776000
# Max archive and deployed jobs to keep, set with 0 to disable delete
action with this method.
scheduler.conf.cleaning.maxOldJobs=200
Take into account your available disk space when setting these parameters.

3.

In the Job Server configuration file, the same parameters can be adapted:
root/conf/configuration.properties

The following files are impacted by the auto-cleaning operation:


Job archives in:
<ApplicationPath>/archiveJobs
Job execution & recovery logs in:
<ApplicationPath>/executionLogs
Job Server files in:
<ApplicationPath>/TalendJobServersFiles

40

Talend Enterprise ESB Installation Guide

Chapter 4. Configuring Talend Enterprise


ESB Studio and AMC
This chapter describes the configuration steps for Talend Enterprise ESB Studio and Activity Monitoring Console.
It also provides useful information related to memory and launching issues you might encounter when working
with Talend Enterprise ESB Studio and Talend Administration Center.

Talend Enterprise ESB Installation Guide

Prerequisites of Talend Enterprise ESB Studio

4.1. Prerequisites of Talend Enterprise ESB


Studio
To use Talend Enterprise ESB Studio properly, you first need to install the following programs:
Java Virtual Machine version 1.6.
External programs specific to bulk components (if you want to use Oracle, Sybase, Informix or Ingres bulk
functionality). For more information, see the below sub-section.
On Windows XP and Windows Server 2003, the GDI is already installed. However, on
Windows 2000, this installation is required. The GDI can be downloaded from Microsofts
Website [http://www.microsoft.com/downloads/en/details.aspx?FamilyID=6a63ab9c-df12-4d41-933cbe590feaa05a&DisplayLang=en]. For further information, visit Eclipses FAQ.
On some Linux distributions, the xulrunner package is required for the Welcome page to display properly.

4.1.1. Installing database client software (for bulk


mode)
Some bulk components, like Oracle, Sybase, Informix or Ingres, require database client software to run properly:
OracleBulkExec uses the sqlldr external utility. This utility is available in Oracle clients that must be installed
on the computer.
Informix uses the dbload external utility.
Ingres uses the sql external utility.
Sybase uses the bcp.exe external utility. This utility is asked for in the Sybase bulk components Basic Settings
view. For more information, see tSybaseBulkExec, tSybaseOutputBulk and tSybaseOutputBulkExec components
on Talend Enterprise Components Reference Guide.

4.2. Configuring the Talend Enterprise ESB


Studio
Installing Talend Enterprise ESB Studio on your client machines is as easy as these three steps:
1.

Unzip the archive under a directory. If possible, keep the path length at a minimum.

2.

Double-click the executable file corresponding to your operating system.

3.

In the [License setup] dialog box that appears, paste your license key in the blank area or click Load the
License... to browse and select your license file and then click OK.

Or, after unzipping Talend Enterprise ESB Studio,


1.

42

Create a file (without extension) named license containing your license key and only your license key
(found in your email - For more information, see Section 1.1, License key).

Talend Enterprise ESB Installation Guide

Installing external modules

2.

Paste the file at the root of the extracted directory, at the same level as the .exe or .sh files
Make sure this file is present at the root of the extracted directory and has no extension.

3.

Run the software according to your architecture (if you are running under a 64-bit capable OS then use x86_64
executable).
This license key is valid for ALL the modules and is particularly required for the Studio to start. For
more information on the license key request and management, see sections Section 1.1, License key
and Section 3.3.1, Configuring the Web application access.

When launching Talend Enterprise ESB Studio for the first time, you will need to set up the connection to the
Talend Administration Center Web application in order to access your allocated projects.
You will thus be asked to fill in a URL field with the Talend Administration Center's URL.
For more details about how to connect to the Talend Administration Center, see Section 3.3.1, Configuring the
Web application access and read the Talend Administration Center User Guide.
When filling out the URL field in the Studio, users should never use Localhost, but the actual
IP address or the hostname of your Talend Administration Center server. (e.g.: 192.168.1.1:8080/
org.talend.administrator).
You may need to install the Activity Monitoring Console now.
For more information on Activity Monitoring Console, see Section 4.4, Configuring Activity Monitoring
Console.

4.2.1. Installing external modules


Some specific components need specific java library classes to be installed to run properly. For more information
on how to install those external libraries, see section How to install external modules of Talend Studio User Guide.

4.3. Memory configuration and launching


issues
4.3.1. Configuring the .ini file on Linux/Windows
To gain in performance at run time and when launching the Studio, you can edit the memory settings in the .ini
file corresponding to your OS.
Examples:
Talend-Studio-linux-gtk-x86 -> Talend-Studio-linux-gtk-x86.ini
Talend-Studio-win32-x86.exe -> Talend-Studio-win32-x86.ini
The default values are:
-vmargs -Xms40m -Xmx500m -XX:MaxPermSize=128m

Talend Enterprise ESB Installation Guide

43

For 64-bit platforms on Linux/Windows

If your system resources allow you to change it, edit the default values to:
-vmargs -Xms40m -Xmx500m -XX:MaxPermSize=256m
For more details: http://www.oracle.com/technetwork/java/hotspotfaq-138619.html
If your Studio is installed on Unix-like system, add execution rights on the relevant Studio binary file. On a
standard Linux distribution, type in the following command:
$ chmod +x Talend-Studio-linux-gtk-x86
$ ./Talend-Studio-linux-gtk-x86

4.3.2. For 64-bit platforms on Linux/Windows


You need to add the following JVM attributes to the -vmargs:
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/
DataTreeNode,forwardDeltaWith
in the .ini file corresponding to the binary file called in the commandline.sh.

4.3.3. For non Linux/Windows platforms


To be able to use a different JVM than the default one (for platforms other than Windows and Linux for example),
edit the commandline.sh file and replace the following content (in bold):
./Talend-Studio-linux-gtk-x86
-nosplash -application org.talend.commandline.CommandLine -consoleLog
-data commandline-workspace startServer -p 8002
with:
/My_Jvm_Path/java -Xmx1024m -XX:MaxPermSize=256m -jar
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20100507.jar
-nosplash -application org.talend.commandline.CommandLine -consoleLog
-data commandline-workspace startServer -p 8002 -vmargs
Do not forget the -vmargs information as the corresponding .ini file will not be taken into account any
longer.

4.3.4. For 64-bit platform on non Linux/Windows OS


For non Linux/Windows 64-bit platforms, change the following information (in bold):
./Talend-Studio-linux-gtk-x86 -nosplash -application
org.talend.commandline.CommandLine -consoleLog -data
commandline-workspace startServer -p 8002
to
/My_Jvm_Path/java -jar

44

Talend Enterprise ESB Installation Guide

Configuring Activity Monitoring Console

plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20100507.jar
-nosplash -application org.talend.commandline.CommandLine
-consoleLog -data commandline-workspace startServer -p 8002
-vmargs -Xmx500m -XX:MaxPermSize=256m
-XX:CompileCommand=exclude,org/eclipse/core/internal/dtree/
DataTreeNode,forwardDeltaWith

4.4. Configuring Activity Monitoring Console


Activity Monitoring Console is an application that allows you to monitor Job executions. The Job executions are
monitored using three database tables that relate to the following data:
collection of logs,
component statistics,
data flow volumes.
To store this data, you need to create three database tables respectively using the schema of the tLogcatcher,
tStatcatcher, tFlowMeterCatcher connectors (present in the Palette of your Talend Enterprise ESB Studio).
The installation of the <AMC> Database and the use of the Activity Monitoring Console in
Talend Enterprise ESB Studio is optional for Talend Enterprise ESB and is only required if the
tFlowMeterCatcher, tLogCatcher and tStatCatcher components are used. These components can be
used in Jobs (for example, ESB Consumer jobs) for REST and Soap ESB Service Providers. Only the
tLogCather is supported for now as the other components are not fully supporting the "Keep listening"
environments, and Routes currently can not use these components.
1.

Create a database that you name amc, for example.

2.

Then, create a Job to create these tables in the amc database.

3.

Launch a Talend Enterprise ESB Studio and connect to the WORK project that you just created when
configuring Talend Enterprise ESB client.

4.

Create a Job that contains three tCreateTable components.

5.

Define the connection parameters to the amc in the three tCreateTable components.

6.

Define the data structure by taking the schema provided in the components: tLogCatcher, tStatCatcher and
tFlowMeterCatcher.
In the tStatsCatcher schema, make sure the Moment data type is set to datetime type and not date.
To change this data type, click Edit Schema in the corresponding tCreateTable.

Now that the Activity Monitoring Console database is created, you can monitor the Job executions either from
Talend Enterprise ESB Studio or from the Dashboard module of Talend Administration Center (available from
Talend Enterprise ESB Professional Edition).
To do so, you simply need to tell Talend Enterprise ESB Studio and Talend Administration Center about the
connection parameters to these tables.
From the Talend Enterprise ESB Studio, configure the Activity Monitoring Console:
1.

Click Edit>Project Settings>Job Settings>Stats&Logs.

2.

Then define the connection parameters to the tables.

Talend Enterprise ESB Installation Guide

45

Configuring Activity Monitoring Console

The Activity Monitoring Console builds charts on the basis of the data collected during execution of various Jobs.
For more details on how to use the Activity Monitoring Console, refer to the Activity Monitoring Console User
Guide.
From the Web application (Talend Administration Center):
1.

Select the Dashboard menu, then click Connections.

2.

Set the connection parameters to the LogCatcher and StatCatcher tables.


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 the Talend Administration Center User Guide. So, you have
to connect to Talend Administration Center as an Operation Manager to be able to configure the amc
monitoring database connection information.

For more details on how to use the Dashboard, refer to the Talend Administration Center User Guide.

46

Talend Enterprise ESB Installation Guide

Appendix A. H2 Database Administration &


Maintenance
This Chapter provides information about how to manage and back up the H2 embedded database.
For more information about how to use the H2 database and web console, refer to the H2 database documentation
at http://www.h2database.com.

Talend Enterprise ESB Installation Guide

About H2 embedded database

A.1. About H2 embedded database


H2 is a relational database management system written in Java. It can be embedded in Java applications or run
in the client-server mode.
This database is the default solution embedded in Talend Administration Center to store all cross-project
information such as users, authorizations, projects...
If you do not want to use this default database, you can set up a database server (MySQL, MSSQL or Oracle).
The benefits of using this H2 embedded database is that it simplifies the installation process.

A.2. Administrating the H2 database through


the Web console
To help you administrate the H2 embedded database, a dedicated Web console is available directly from Talend
Administration Center.

A.2.1. Connecting to the H2 Web Console


From Talend Administration Center, you can access the H2 administration console:
1.

From the main Menu, click Configuration to access the Configuration page.

2.

On the Configuration page, develop the Database node to display the parameters.

3.

In the Web Console field, click the link to access the H2 Web Console.

4.

The H2 Web Consoles Login page displays:

48

Talend Enterprise ESB Installation Guide

Connecting to the H2 Web Console

5.

In the User Name and Password fields, type in the connection login and password to the database, by default
tisadmin and tisadmin.

6.

The JDBC URL field reads by default:


jdbc:h2:/<ApplicationPath>/WEB-INF/database/
talend_administrator;AUTO_SERVER=TRUE;MVCC=TRUE;LOCK_TIMEOUT=15000
where <ApplicationPath> is the location where org.talend.administrator was deployed.
If you have moved the H2 embedded database location, then fill out the JDBC URL field with the
updated URL information. Then click the Test Connection button prior to clicking Connect in order
to check the new URL. In case of a mistyped URL, the JDBC URL will revert back to the original
URL information.

7.

Click Connect.
The Web database administration page displays.

Talend Enterprise ESB Installation Guide

49

Backing up the H2 database

For more information about H2 use and troubleshooting, please refer to the H2 online documentation
on http://www.H2database.com.

A.2.2. Backing up the H2 database


The configuration parameters of the H2 database backup is already set by default so that the backup occurs on
an everyday-basis.
If you need or want to make edits to this setting, edit the configuration file:
<ApplicationPath>/WEB-INF/classes/configuration.properties
The cron-based backup of the embedded database triggers everyday at 3.45am all year round. The syntax reads as
follows Seconds Minutes Hours Day-of-month Month Day-of-week Year, such as for example:

0 45 3 ? * * * (default setting - trigger every day at 3.45am)


0 45 5 ? * MON-FRI (every monday, tuesday, wednesday, thursday and friday at 5.45 am)
More examples are available on http://www.quartz-scheduler.org/docs/tutorials/crontrigger.html.
Other automatic backups are performed at startup and shutdown of the application server:
database.embedded.backup.doBackupAtStartup=true
database.embedded.backup.doBackupAtShutdown=true
The backup files are stored at the following location, up to the 30 latest backups:
<ApplicationPath>/WEB-INF/database/backups

50

Talend Enterprise ESB Installation Guide

Setting up the H2 database for access from other machines

A.3. Setting up the H2 database for access


from other machines
To allow other users to access the H2 database for centralized storage of cross-project information, do the
following:
1.

Stop Tomcat service if it is running.

2.

Unzip your H2 database server package to any of your local drives. The latest H2 database server package is
available at www.h2database.com/html/download.html [http://www.h2database.com/html/download.html].

3.

Open a CMD window, navigate to the drive where the H2 database server package was unzipped, and change
directory to h2\bin, which contains the h2*.jar file.

4.

Start the H2 server as a service using the following command:


java -cp h2*.jar org.h2.tools.Server -tcp -tcpAllowOthers
-tcpPort <port_number>

Now other users can access the H2 database, but you still need to edit the database URL to make Talend
Administration Center work.
To do so, proceed as follows:
1.

Open the configuration.properties file in the <ApplicationPath>/WEB-INF/Classes folder, and edit the H2
database URL setting as follows:
database.url=jdbc:h2:tcp://<IP_address>:<port_number>/
file:<ApplicationPath>/WEB-INF/database/
talend_administrator;AUTO_SERVER=TRUE;IFEXISTS=TRUE;MVCC=TRUE;
LOCK_TIMEOUT=15000
where <IP_address> is your IP address, <port_number> is the TCP port number specified in the command
used to start the H2 server, and <ApplicationPath> is the location where org.talend.administrator was
deployed.

2.

Start the Tomcat service.

3.

Start your Talend Administration Center Web application.

Now others can access and use the H2 database through the URL address.

Talend Enterprise ESB Installation Guide

51

Talend Enterprise ESB Installation Guide