TalendEnterprise Installer UG 50a En

Talend EnterpriseInstallerUser Guide

5.0_a

Talend Enterprise Installer

Talend Enterprise Installer: User GuideAdapted for Talend Enterprise Installer v5.0.x. Supersedes any previous User Guide.Copyright © 2008-2011

Talend Enterprise Installer User Guide

Table of Contents

Preface .............................................. v1. General information ................... v

1.1. Purpose ........................... v1.2. Audience ......................... v1.3. Typographicalconventions ............................ v

2. History of changes ...................... v3. Feedback and Support ............... vi

Chapter 1. Prior to installingTalend Enterprise solutions .............. 1

1.1. License key ............................. 21.2. Hardware requirements ............ 2

1.2.1. Memory usage ................ 21.2.2. Disk usage ..................... 21.2.3. Compatible Webbrowsers ................................ 31.2.4. Naming conventions ........ 31.2.5. Third-party software ........ 4

1.3. Supported Platforms ................ 51.3.1. Platform compatiblewith Talend Studio andCommandline ......................... 51.3.2. Platform compatiblewith Talend Runtime ............... 51.3.3. Platform compatiblewith Talend AdministrationCenter ................................... 61.3.4. Platform compatiblewith JobServer ........................ 6

1.4. Compatible RuntimeContainers .................................... 7

1.4.1. Runtime Containerscompatible with Talend ESB............................................. 71.4.2. Runtime Containerscompatible with TalendAdministration Center .............. 71.4.3. Runtime Containerscompatible with Talend DataQuality Portal ........................ 71.4.4. Runtime Containerscompatible with MDMServer .................................. 7

1.5. Compatible Databases .............. 81.5.1. Databases compatiblewith Service ActivityMonitoring (SAM) .................. 81.5.2. Databases compatiblewith Talend AdministrationCenter ................................... 81.5.3. Databases compatiblewith Activity MonitoringConsole ................................. 8

Chapter 2. Introducing TalendEnterprise solutions ........................ 11

2.1. General introduction toTalend Enterprise solutions ............ 12

2.1.1. Apache Tomcat Server........................................... 122.1.2. Database ...................... 132.1.3. SVN ........................... 132.1.4. Talend ArtifactRepository ............................ 132.1.5. Apache Karaf ............... 13

2.2. Detailed introduction toTalend Enterprise solutions ............ 14

2.2.1. Administrationdatabase ............................... 142.2.2. Activity MonitoringConsole log database .............. 142.2.3. Apache Tomcat server........................................... 152.2.4. SVN server .................. 152.2.5. Software updaterepositories ........................... 152.2.6. ESB Artifactrepositories ........................... 16

Chapter 3. Using TalendEnterprise Installer ......................... 19

3.1. Talend Enterprise Installerspecific prerequisites .................... 203.2. Launching Talend EnterpriseInstaller ...................................... 20

3.2.1. Launching TalendEnterprise Installer Setupwizard ................................. 213.2.2. Entering the licensekey ..................................... 213.2.3. Selecting aninstallation type ..................... 21

3.3. Server type installation ........... 223.3.1. Configuring TalendAdministration Center ............ 23

3.4. Client type installation ............ 263.5. Custom type installation .......... 27

3.5.1. Configuring TalendAdministration Center ............ 293.5.2. Configuring TalendEnterprise MDM Server .......... 293.5.3. Configuring TalendData Stewardship Console ....... 313.5.4. Configuring TalendCommandLine ...................... 333.5.5. Configuring SOAManager .............................. 343.5.6. Configuring TalendJobServer ............................. 343.5.7. ConfiguringSubversion Repository ............ 353.5.8. Configuring TalendEnterprise Data QualityPortal .................................. 36

Talend Enterprise Installer

iv Talend Enterprise Installer User Guide

3.5.9. Installing Talendmodules as Services ............... 38

Chapter 4. Talend EnterpriseData Quality Portal’s specificinformation ..................................... 41

4.1. Upgrade information .............. 424.1.1. Upgrading from v4.2 ...... 424.1.2. Upgrading from aversion prior to 4.2 ................ 42

4.2. Sending reports by email ......... 424.3. LDAP configuration ............... 434.4. Memory Configuration of theTomcat server ............................. 45


Preface

1. General information

1.1. Purpose

This User Guide explains how to install and configure Talend modules and related applications. Fordetailed explanation on how to use and fine-tune Talend applications, please refer to the appropriateUser Guides of Talend Enterprise solutions.

Information presented in this document applies to Talend products releases v5.0.x onwards.

1.2. Audience

This guide is dedicated to the administrators of Talend products and server modules.

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

• 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 isalso used to add comments related to a table or a figure,

•The icon indicates a message that gives information about the execution requirements orrecommendation type. It is also used to refer to situations or information the end-user need to beaware of or pay special attention to.

Any command is highlighted with grey background or code typeface

2. History of changesThe below table lists the changes made in the Talend Enterprise Installer User Guide.

Feedback and Support

vi Talend Enterprise Installer User Guide

Version Date History of Change

v4.2a 05/17/2011 Creation of User Guide includes:

- Created sections regarding the launching of the Installer.

- Created sections regarding the three main installation types: Full,Custom and Client types.

- Reviewed overall information organization in document.

v4.2b 07/11/2011 Update of User Guide includes:

- Updated Prerequisites.

- Added information regarding Talend Enterprise Data QualityPortal configurations.

- Updated chapter Using Talend Enterprise Installer.

v5.0a 12/12/2011 Update of User Guide includes:

- Updated documentation to reflect new product names: TalendInstaller has become Talend Enterprise Installer.

For further information on these changes, see the Talend website.

- Updates chapter Prerequisites, especially section Hardwarerequirements and section Third-party softwares.

- Added two subsections in the chapter Using Talend EnterpriseInstaller about how to increase Tomcat memory size.

- Modified information regarding Server installation type (formerFull installation type).

- Added information about the Talend Runtime and the Talend ESBmodules.

3. Feedback and SupportYour feedback is valuable. Do not hesitate to give your input, make suggestions or requests regardingthis documentation or product and find support from the Talend team, on Talend’s Forum website at:

http://talendforge.org/forum

http://talendforge.org/forum


Chapter 1. Prior to installing TalendEnterprise solutionsThis chapter provides useful information on software and hardware prerequisites you should be aware of, priorto starting the installation of Talend modules.

License key

2 Talend Enterprise Installer User Guide

1.1. License keyYou 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 solutions. Keep this fileat hand in a safe place.

For more information on how to use your license key, see Talend Enterprise Data Integration Installation 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 (TalendStudio on a developer’s machine and Talend Administration Center on the execution server for example).

Use preferably 7-zip if you are on Windows.

• the documentation (including the one you are reading now):

Each module of Talend has a dedicated User Guide available in pdf.

1.2. Hardware requirementsTo make the most out of the Talend products you subscribed to, please consider the following hardwarerecommendations.

1.2.1. Memory usage

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

Product Client/Server Recommended alloc. memory

Talend Administration Center Server 4GB minimum, 8GB recommended

Talend Enterprise MDM Server 4GB minimum, 8 GB recommended2

Commandline Server 2GB minimum, 5 GB recommended

JobServer Server 1GB minimum, more recommended1

Studio Client 3GB minimum, 4 GB recommended

Talend Runtime Server 2GB minimum, 4 GB recommended1

1. Memory requirements depend on the executed processes.

2. Memory requirements depend on the number of entities installed.

1.2.2. Disk usage

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

Compatible Web browsers

Talend Enterprise Installer User Guide 3

Product Client/Server Required diskspace forinstallation

Required disk space for use

Talend AdministrationCenter with Talend ArtifactRepository (for Softwareupdate and ESB Artifactrepository)

Server 800MB 800MB minimum + projectsize = 20GB+ recommended

Talend Enterprise MDM Server 1+ GB 4GB+

Commandline Server 3GB 2GB minimum + project size =20 GB+ recommended

JobServer Server 20MB 2GB minimum + Jobsdeployed = 20+ GBrecommended

Studio Client 3GB 3+ GB

Talend Runtime Server 400MB 400+ MB

1.2.3. Compatible Web browsers

Despite our intensive tests, you might encounter some issues when accessing Talend Enterprise Data Integrationwith some Web browser.

Please refer to the table below for a summary of supported Web browser. Based on reported issues, we consideredthat some Web browsers are not supported even though the issue can be resolved in particular conditions. A notehas 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.2.4. Naming conventions

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

Zip/jar file naming convention Example Description

Talend-AdministrationCenter-rYYYY-VA.B.C

Talend-AdministrationCenter-r72851-V5.0.1.zip

Talend Administration CenterWeb-based application used toadministrate Talend Enterprisesolutions projects and users + TalendArtifact Repository.

Talend-Studio-rYYYY-VA.B.C Talend-Studio-r72851-V5.0.1.zip Commandline interface to the IDE +Studio IDE (GUI)

Third-party software


Zip/jar file naming convention Example Description

Talend-JobServer-rYYYY-VA.B.C

Talend-JobServer-r72851-V5.0.1.zip

JobServer: Standalone executionserver

Talend-Soamanager-rYYYY-VA.B.C

Talend-Soamanager-r72851-V5.0.1.jar

SOA Manager: helps deploying Webservices Jobs

Talend-Runtime-VA.B.C Talend-Runtime-V5.0.1.zip Talend Runtime: OSGi Containerincluding JobServer. TalendRuntime is a standalone equivalentto the Talend ESB OSGi Container(container folder) of Talend ESB.

Talend-ESB-VA.B.C Talend-ESB-V5.0.1.zip Talend ESB: application integrationsolution with an OSGi Container,Service Locator, Service ActivityMonitoring and Security TokenService. It includes the TalendRuntime (in the container folder)and provides additional partslike examples, standalone, Tomcatdeployment relevant parts and otheradditional parts primarily used byJava 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.Cmust match on both client side and server side.

1.2.5. Third-party software

Some additional third-party applications are required for Talend modules to work together smoothly.

• A MySQL/Oracle/SQLServer database to hold Talend Administration Center settings: http://www.mysql.com;http://www.oracle.com; http://www.microsoft.com .

• A Web application server being able to deploy WAR files, e.g.:

- Apache Tomcat version 5.5, 6.0 or 7.0 (version 6.0 or 7.0 are recommended) - http://tomcat.apache.org/or

- JBoss Application Server version 4.2.2 - http://www.jboss.org/jbossas/downloads/

• Oracle (JDK or JRE) JVM 1.6 - http://java.sun.com/javase/downloads/index.jsp

• Subversion for storing your projects http://subversion.tigris.org/ or http://www.visualsvn.com/server/download/

Talend Installer provides instances of Tomcat 6 and Subversion and a H2 database is by default embeddedin Talend Administration Center. So, the third-party softwares listed here are only for manual setup orif a specific database should be used.

For more information on Talend Enterprise Installer specific prerequisites, see Section 3.1, “ Talend EnterpriseInstaller specific prerequisites”

http://www.mysql.com

http://www.oracle.com

http://www.microsoft.com

http://tomcat.apache.org/

http://www.jboss.org/jbossas/downloads/

http://java.sun.com/javase/downloads/index.jsp

http://subversion.tigris.org/

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

Supported Platforms


1.3. Supported PlatformsDespite our intensive tests, you might encounter some issues when installing our products on some OperatingSystems.

Please refer to the grids below for a summary of supported OS and Java Runtime environments.

1.3.1. Platform compatible with Talend Studio andCommandline

OS Processor JDK/JRE Support type

MAC-OS Lion / 10.6 64 bits Oracle Java 1.6 recommended

Microsoft Windows XP SP3 32 bits Oracle Java 1.6 recommended

Microsoft Windows Vista SP1 32 & 64 bits Oracle Java 1.6 supported

Microsoft Windows 7 64 bits Oracle Java 1.6 recommended

Microsoft Windows 2003 SP2 64 bits Oracle Java 1.6 recommended1

Microsoft Windows 2008 R2 64 bits Oracle Java 1.6 recommended1

Microsoft Windows XP SP3 64 bits Oracle Java 1.6 supported

Microsoft Windows 7 32 bits Oracle Java 1.6 supported

Linux Ubuntu 10.04 64 bits Oracle Java 1.6 recommended

Linux CentOS 5.4 32 bits Oracle Java 1.6 recommended

Redhat Linux Enterprise Server Edition 6.1 64 bits Oracle Java 1.6 recommended

Redhat Linux Enterprise Server Edition 5.4 64 bits Oracle Java 1.6 recommended

Solaris 10 x86 64 bits Oracle Java 1.6 recommended1

Linux Ubuntu 10.4 32 bits Oracle Java 1.6 supported

Linux Ubuntu 11.10 32 & 64 bits Oracle Java 1.6 supported

Redhat Linux Enterprise Server Edition 5.3/5.4/5.6 32 bits Oracle Java 1.6 supported

Redhat Linux Enterprise Server Edition 6.1 32 bits Oracle Java 1.6 supported

1. Only for Commandline

1.3.2. Platform compatible with Talend Runtime



Linux CentOS 5.4 32 bits Oracle Java 1.6 recommended

Red Hat Linux Enterprise ServerEdition 5.3/5.4/5.6

64 bits Oracle Java 1.6 supported

Red Hat Linux Enterprise ServerEdition 6.1

64 bits Oracle Java 1.6 recommended

Solaris 10 sparc 64 bits Oracle Java 1.6 recommended

Linux CentOS 5.3/5.6 32 bits Oracle Java 1.6 supported


Platform compatible with Talend Administration Center




SUSE SLES 10/11 32 & 64 bits Oracle Java 1.6 supported

Solaris 10 x86 64 bits Oracle Java 1.6 supported

Windows Server 2008 R2 64 bits Oracle Java 1.6 recommended

Windows Server 2003 SP2 64 bits Oracle Java 1.6 supported

1.3.3. Platform compatible with Talend AdministrationCenter



Red Hat Linux EnterpriseServer Edition 5.4




Solaris 10 x86 64 bits Oracle Java 1.6 recommended

Linux CentOS 5.4 32 bits Oracle Java 1.6 supported




Solaris 10 sparc 64 bits Oracle Java 1.6 supported



1.3.4. Platform compatible with JobServer







Solaris 10 x86 64 bits Oracle Java 1.6 recommended

Linux CentOS 5.3/5.4/5.6 32 bits Oracle Java 1.6 supported



Red Hat Linux Enterprise ServerEdition 5.3/5.4/5.6



Solaris 10 x86 64 bits Oracle Java 1.6 supported


Compatible Runtime Containers




1.4. Compatible Runtime ContainersPlease refer to the grids below for a summary of supported runtime containers. Based on reported issues, weconsidered that some runtime containers are not supported even though the issue can be resolved in particularconditions. A note has been added providing configuration details.

1.4.1. Runtime Containers compatible with Talend ESB

Runtime Containers Version Supported type

Talend ESB Container (ApacheKaraf)

5.0 (2.2.4) recommended

Apache Tomcat 6 supported

JBoss Application Server 4.2.2 supported with limitations1

1. ESB/CXF service participants.

1.4.2. Runtime Containers compatible with TalendAdministration Center


Apache Tomcat 6 recommended


JBoss Application Server 4.2.2 supported

1.4.3. Runtime Containers compatible with Talend DataQuality Portal


Apache Tomcat 6 recommended


1.4.4. Runtime Containers compatible with MDMServer


JBoss Application Server 4.2.2 supported

Compatible Databases


1.5. Compatible DatabasesPlease refer to the grids below for a summary of supported databases. Based on reported issues, we consideredthat some databases are not supported even though the issue can be resolved in particular conditions. A note hasbeen added providing configuration details.

1.5.1. Databases compatible with Service ActivityMonitoring (SAM)

Databases Version Support type

MySQL 5.5 recommended

MS SQL Server 2008 supported

Oracle 10 recommended

H2 1.3 supported1

IBM DB2 9.7 recommended


Oracle 11 supported

Derby DB >10.8 supported with limitations2

1. Requires an H2 Database Server separated from Talend Enterprise Data Integration.

2. Only for development and test purpose.

For more information about Service Activity Monitoring, see the Talend Enterprise ESB Installation Guide.

1.5.2. Databases compatible with TalendAdministration Center




H2 1.3 recommended

MySQL 5.0/5.1 supported



Oracle 11 supported

1.5.3. Databases compatible with Activity MonitoringConsole



Databases compatible with Activity Monitoring Console




H2 1.3 recommended

MySQL 5.0/5.1 supported


IBM DB2 9.7 supported

Informix 11 supported

PostgreSQL 9.1 supported

Sybase 15 supported


Firebird 2.1 supported

Oracle 11 supported


Chapter 2. Introducing Talend EnterprisesolutionsThis chapter introduces Talend Enterprise solutions. It provides a detailed description of the architecture and listsall modules that are required for the installation and configuration of Talend Enterprise solutions.

General introduction to Talend Enterprise solutions


2.1. General introduction to Talend EnterprisesolutionsThe following image shows the distributed architecture of Talend Enterprise solutions. However, we recommendyou 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 solutions include:

• A server that hosts Talend Administration Center (Tomcat server + CommandLine),

• A storage server for Project metadata (SVN),

• A storage database for administration metadata (by default, an embedded H2 database is used).

• A Talend Artifact Repository (based on Apache Archiva) for storing all ESB artifacts to be deployed ontoTalend Enterprise Data Integration 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 applicationgives access to all management and administration functionalities for an integration project. These functionalitiesinclude:

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 todeploy the Web application on JBoss, see Talend Enterprise Data Integration Installation Guide.

2.1.2. Database

The database server is used to manage the persistence. By default an embedded H2 database is used, but youcan 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 inthe Repository (Jobs, Routes, Services, Business models, Metadata, Routines, etc.).

Talend Enterprise solutions are rich clients that allow 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

Both Talend software update repository and ESB Artifact repository are based on Talend Artifact Repository.Talend provides a preconfigured artifact repository with the repositories necessary to use the Software Update andESB Artifact repository functionalities.

The Software Update repository is used to manage application updates. By default two repositories are embeddedwithin this repository provided by Talend: one to publish the updates and one to retrieve them. These repositoriesallow the user to visualize the updates available. For detailed information, see the Section 2.2.5, “Software updaterepositories”.

The ESB Artifact repository is used as a catalog in which all ESB artifacts (Jobs, Routes, Services and GenericOSGi features) created from Talend Enterprise Installer or any other Java IDE and to be deployed and executed arestored. By default two repositories are embedded within this repository provided by Talend: one for developmentand one for production. These repositories make artifacts available for deployment in Talend Runtime. For detailedinformation, see the Section 2.2.6, “ESB Artifact repositories”.

2.1.5. Apache Karaf

The Talend Runtime Container (based on Apache Karaf) is an execution container in which all your Service,Route and Generic features, which are retrieved from the ESB Aritfact repository, are deployed and executed asOSGi bundles.

Detailed introduction to Talend Enterprise solutions


2.2. Detailed introduction to TalendEnterprise solutionsThis 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 possibilityto change database to MySQL, MSSQL or Oracle if you prefer so. For more information about how to set up adifferent database, see the FAQ in the Talend Enterprise Data Integration Installation Guide.

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 informationand administration including: administration data, project declaration (storage mode), user declaration andauthorization, task list, etc.

The tables in this database are automatically created when connecting for the first time to Talend AdministrationCenter. The created tables include (among others):

• a Users table,

• a Projects table,

• a Rights table.

These tables are created, populated and managed automatically by the Talend Enterprise solutions.

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 installedon any server. This <AMC> database will initially be empty. Its name may be modified, but you must take intoaccount 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 tableswill collect data from the following components:

• tFlowMeterCatcher,

• tLogCatcher,

• tStatCatcher.

Instructions on how to create these tables and their structure is provided in the Activity Monitoring Console UserGuide.

A corresponding SQL user must be created and thus mapped to have access to this database. This user should begranted the “create” and “update” rights.

The installation of the <AMC> database is optional for Talend Enterprise solutions and is only requiredwhen using the tFlowMeterCatcher, tLogCatcher and tStatCatcher components. These components can

Apache Tomcat server


be used in Jobs (for example, ESB Consumer jobs) for REST and Soap ESB Service Providers. Only thetLogCatcher 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 whichallows users to (depending on their role):

• Manage user accounts and roles/rights,

• Access to the 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 alsosupported.

Talend Web application can also be hosted by JBoss application server. For more information on how todeploy the Web application on JBoss, see the Talend Enterprise Data Integration Installation Guide.

2.2.4. SVN server

In SVN mode, project metadata (Jobs, Services, Routes, Business Models, Documentation, etc.) are stored in anSVN repository rather than in a database. This is the recommended storage mode and the only mode that allowsto store large projects.

We recommend you to store several projects per repository, simply in order not to have too many repositories todeal 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 onhow to create projects and store them in an SVN repository, see the Talend Administration Center UserGuide.

2.2.5. Software update repositories

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

ESB Artifact repositories


To download and install some software updates, you need to use an artifact repository and its two embeddedrepositories:

• 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 interfacefollowing the procedure described in the Talend Enterprise Data Integration Installation Guide.

The Talend Artifact Repository archive file is embedded in the Talend Administration Center archive filethat is provided by Talend.

The Studio is connected to Talend Administration Center to retrieve the repository connection information andthe 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 the Talend EnterpriseData Integration Installation Guide.

For more information on how to check updates via these repositories, see the Talend Administration Center andTalend Studio User Guides.

2.2.6. ESB Artifact repositoriesTalend Artifact Repository is an artifact repository used to store as artifacts all the Services, Routes and Jobscreated in Talend Enterprise Installer or any Generic OSGi Feature created in any other Java IDE.

ESB Artifact repositories


Once published, those artifacts can be selected through Talend Administration Center in order to set theirdeployment as OSGi features in Talend Runtime.

When the deployment of a feature is initiated in Talend Administration Center, Talend Runtime requests thecorresponding artifact in Talend Artifact Repository. So, Talend Artifact Repository deploys the feature in TalendRuntime which can now execute it.

Talend Artifact Repository comes with two embedded repositories 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 ESB Artifact repository, see Talend Enterprise DataIntegration Installation Guide.


Chapter 3. Using Talend Enterprise InstallerThis chapter details the procedures required to install one or more Talend modules using Talend EnterpriseInstaller.

We strongly encourage you to read the Chapter 1, Prior to installing Talend Enterprise solutions and the Chapter 2,Introducing Talend Enterprise solutions before starting this chapter.

Talend Enterprise Installer specific prerequisites


3.1. Talend Enterprise Installer specificprerequisitesPrior to launch Talend Enterprise Installer, please check that all the following softwares and modules are properlyset up on the station where you are to install the Talend modules:

• Mysql version 5.0+ (or Oracle 10g for Talend Enterprise Data Quality Portal) must be installed and memorywell configured;

• Operating System Linux 32/64 bits or Windows 32/64 bits;

• JDK 1.6.0_18+ must be installed;

Talend Enterprise Installer automatically checks for JDK version 1.6 or higher version. If no instance ofJDK is found, the installer will shut down.

• The JAVA_HOME environment variable must be defined and must point to the JDK directory;

For example, if the JDK path is C:\Java\JDKx.x.x\bin, you must set the JAVA_HOME environment variableto 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 anddoes 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 aroundthe path when setting the values for the environmental variable.

• The JRE_HOME must be defined and must point to the JRE directory;

• .Net version 2+ is required by Talend Enterprise Installer to install services on Windows;

• (optional) a mail server (to send notifications by email).

The platforms supported by Talend Enterprise Installer are the following: 32/64-bit Windows, 32/64-bitLinux and Mac OS X.

3.2. Launching Talend Enterprise InstallerThis section describes how to launch the Installer wizard. This wizard helps you to set up all the Talend modulesyou want to install. It will guide you step by step to configure these installations.

To install Talend Enterprise Installer, proceed as follows:

1. Copy the Talend Enterprise Installer archive file delivered by Talend onto the machine where you want toinstall the modules.

According to your needs, Talend Enterprise Installer allows you to install the various Talend moduleson different machines.

2. Unzip it under a folder which name does not contain any space character.

You can then rename the decompressed folder to Installer for more clarity.

Launching Talend Enterprise Installer Setup wizard


3.2.1. Launching Talend Enterprise Installer Setupwizard

In the Installation folder, you will find four executable files. According to your operating system, choose therelevant one to be launched:

Talend-Installer-rYYYY-VA.B.C-windows-installer.exe (for example, Talend-Installer-r73658-V5.0.1-windows-installer.exe) if you are on Windows,

Talend-Installer-rYYYY-VA.B.C-linux-installer.run (for example, Talend-Installer-r73658-V5.0.1-linux-installer.run) and Talend-Installer-rYYYYY-VA.B.C-linux64-installer.run (for example, Talend-Installer-r73658-V5.0.1-linux64-installer.run) if you are on 32bit Linux or 64bit Linux respectively,

Talend-Installer-rYYYYY-VA.B.C-osx-installer.app (for example, Talend-Installer-r73658-V5.0.1-osx-installer.app) in the .tar file called Talend-Installer-rYYYYY-VA.B.C-osx-installer.app.tar if you are on MacOS,

where YYYY is the revision number and A.B.C is the revision level (Major.Minor.Patch).

For Linux users: you will need to run the Installer as user ROOT (name of the login account given fulland complete access to all system resources). If not, the installer will display an error message.

1. Run this file. A [Setup] wizard displays.

2. Click Next to start the setup process.

3. On the next screen, read the Talend Enterprise Installer license agreement and select I accept the agreementto enable the Next button.

4. Click Next to continue the installation process.

3.2.2. Entering the license key

Before starting to install each module and configure them manually, you need to enter your license key.

1.In the License file field, paste the license key delivered by Talend, or upload it. To do so, click the buttonnext to the field and browse to the file that holds your license key.

2. Click Next. A progress information bar displays.

Once validated, you can proceed to the next step.

3.2.3. Selecting an installation type

Installation is divided into three types:

Server type installation


• Server installation type: allows you to install all Talend server components using default settings;

• Client installation type: allows you to install Talend Studio on your machine. The Studio that is installed onyour machine and the perspectives included in this Studio depend on your license key.

• Custom installation type: allows you to choose each module to install and to configure them manually;

Once you have selected your installation type, you need to specify the directory where Talend items will beinstalled. To do so, you can either:

• type in the path to the desired directory in the Installation Directory field;

•browse to the desired directory by clicking the button next to the Installation Directory field.

Choose the appropriate procedure among the following instruction sections. These sections are independent fromeach other.

For Server type installation, see Section 3.3, “Server type installation”.

For Client type installation, see Section 3.4, “Client type installation”.

For Custom type installation, see Section 3.5, “Custom type installation”.

3.3. Server type installationServer installation type allows you to install all Talend server components using default settings.

The Server type only displays the Talend Administration Center configuration because the other serversare installed by default. Note that these modules depend on your license key and thus the edition youhave subscribed to.

Server type installs all modules by default BUT some settings might not be automatically passed on tothe other modules. For example, if you want to set a CommandLine port that is different from the defaultone, you might have to go to the Talend Administration Center Web Application to configure the settingson the configuration page.

After validating your license file, select the Server option in the Setup wizard and click Next to install the Servertype.

Configuring Talend Administration Center


3.3.1. Configuring Talend Administration Center

The next pages will allow you to install and configure the Talend Administration Center items you may need. Formore information about Talend Administration Center, see Talend Administration Center User Guide.

3.3.1.1. Apache Tomcat server configuration

This step helps you to install a Tomcat server that hosts the Talend Web application.

For more information about the Apache Tomcat server and its functionalities, see Section 2.1.1, “Apache TomcatServer” and Section 2.2.3, “Apache Tomcat server”.

For Linux users: note that this installation WILL install an Apache server. Therefore, if you already havean Apache server, the existing one will be deleted.

1. On the next page, select either Install an embedded tomcat server (recommended) or Use an existing tomcatserver in the drop-down list.

The Install an embedded tomcat server (recommended) option is selected by default.

2. Type your Talend Administration Center user name in the Admin User Name field. The default user nameis [email protected].

3. Type your Talend Administration Center password in the Admin Password field. The default password isadmin.

4. Click Next to continue.

If you have chosen the Install an embedded tomcat server (recommended) option, please go directly to the nextstep, which is Section 3.3.1.2, “Database configuration”.



If you have chosen the Use an existing tomcat server option:

1. In the Tomcat directory field, enter the path to the directory where your Tomcat server is already installed, or

browse to this directory by clicking the button next to the field.

2. Click Next to proceed to the next step.

If your machine runs under Linux, you must have read and write permission to this directory.

According to your operating system and the Tomcat option you have selected, read the section corresponding toyour configuration among the following subsections.

On Windows

To increase the memory heap size of the server in order to make all the applications work properly, you have toconfigure Tomcat. To do that, proceed as follows:

1. Go to <TomcatPath>/bin where <TomcatPath> is the Tomcat installation directory, and edit the filecatalina.bat.

2. Add the following line:

set JAVA_OPTS=%JAVA_OPTS% -XX:MaxPermSize=512m -Xmx1024m -Xms256m

The Tomcat memory size is now increased and the server can hold several web applications.

On Linux

To increase the memory heap size of the server in order to make all the applications work properly, you have toconfigure Tomcat. To do that, proceed as follows:



1. Change directory to <TomcatPath>/bin where <TomcatPath> is the Tomcat installation directory, and edit thefile catalina.sh.

2. Add the following line:

JAVA_OPTS="$JAVA_OPTS -XX:MaxPermSize=512m -Xmx1024m -Xms256m"

The Tomcat memory size is now increased and the server can hold several web applications.

3.3.1.2. Database configuration

The next step helps you to install a database server in order to store administration information.

For more information about database servers, see Section 2.1.2, “Database” and Section 2.2.1, “Administrationdatabase”.

1. On the next page, choose one of the following options in the drop-down list: Embedded H2 database(recommended), Connect to a MySQL database, Connect to an Oracle database, Connect to SQL Serverdatabase.

The Embedded H2 database (recommended) option is selected by default.

2. In the Talend Administration Center Port (tomcat port) field, type in the Tomcat server port number. Bydefault, it is 8080.

With the Server type installation, by default the MDM server port is 8180 in JBoss. Make sure to usethe correct port when you set the server URL in the MDM Studio login window.

3. Type in the Talend’s webapp (directory) name under tomcat in the corresponding field. By default, it isorg.talend.administrator.

Client type installation


If you have chosen the Embedded H2 database (recommended) option:


2. On the next page, click Next to confirm your settings and install Talend server items.

A progress indicator shows the installation process.

3. Click Finish to close the [Setup] wizard.

A folder named Talend-<edition>-<version> displays on the installation directory you have previously defined,where <edition> refers to your Talend edition and <version> refers to your Talend Enterprise Installer version.

If you have chosen the Connect to a MySQL database, the Connect to an Oracle database, or the Connectto SQL Server database option:

1. Enter the relevant connection information.

Note that the database must exist and that you must have full rights on this database.

Field Description

Database host IP address of the server hosting the database

Database port Database server port

Database name Name of the database to connect to

User Name Login name to the database

Password Password to the database


3. On the next page, click Next to confirm your settings and install Talend server items.



A folder named Talend-<edition>-<version> is displayed on the installation directory you have previouslydefined, where <edition> refers to your Talend edition and <version> refers to your Talend Enterprise Installerversion.

3.4. Client type installationClient installation type allows you to install Talend Studio on your machine. This mode only installs the Studioon your machine without the server modules.

Custom type installation


The Studio that will be installed depends on you license key and thus the edition you have subscribed to.

The Studio that will be installed will include one or more of the following perspectives according to yourlicense key: Integration perspective, Data Quality perspective, MDM perspective.

1. After validating your license file, select the Client option in the Setup wizard and click Next to install TalendStudio.

2. On the next page, click Next to confirm your choice.



A folder containing the Studio is displayed on the installation directory you have previously defined.

3.5. Custom type installationCustom installation type allows you to choose each module to install and to configure these modules manually.

1. After validating your license file, select the Custom option and click Next to install the modules individually.

2. Select the check boxes of the Talend components you want to install and clear the other check boxes:

Custom type installation


Select To

Talend AdministrationCenter

Install Talend Administration Center items, including Apache Tomcat and thedatabase servers. For more information, see the Section 3.5.1, “ConfiguringTalend Administration Center”.

Server Install Talend Enterprise MDM server, including a JBoss server. For moreinformation, see the Section 3.5.2, “Configuring Talend Enterprise MDMServer”.

Data Stewardship Console Install Talend Data Stewardship Console. For more information, see theSection 3.5.3, “Configuring Talend Data Stewardship Console”.

There are two ways to install Talend Data Stewardship Console.Either it is installed automatically on the same server of TalendAdministration Center when sold with Talend Enterprise DataQuality, or it is installed on the MDM server when sold with TalendEnterprise MDM. If you want to install Talend Data StewardshipConsole on a different Tomcat server, you need to install it manually.

Talend CommandLine Install Talend CommandLine. For more information, see the Section 3.5.4,“Configuring Talend CommandLine”.

SOA Manager Install the SOA Manager. For more information, see the Section 3.5.5,“Configuring SOA Manager”.

Talend Runtime Install Talend Runtime which enables you to run Talend Jobs, Routes,Services and Generic OSGi features on a given server. For more information,see the Talend Enterprise ESB Installation Guide.

Talend JobServer (ExecutionServer)

Install Talend JobServer (Talend remote execution server). For moreinformation, see the Section 3.5.6, “Configuring Talend JobServer”.

FileScale Install a set of binary files that enables Talend Jobs developed withFileScale components to run on the machine. For more informationregarding Filescale components, see the Talend Enterprise Data IntegrationComponent Reference Guide.

Subversion Repository Install the SVN server. For more information, see the Section 3.5.7,“Configuring Subversion Repository”.

Talend Enterprise DataQuality Portal

Install the modules required to access and use Talend Enterprise Data QualityPortal. For more information, see the Section 3.5.8, “Configuring TalendEnterprise Data Quality Portal”.

Services Install Talend modules as services, which means that these modules willstart automatically at every system boot. For more information, see theSection 3.5.9, “Installing Talend modules as Services”.

Talend ESB Install Talend ESB, an application integration solution with OSGi Container,Service Locator, Service Activity Monitoring and Security Token Service.For more information about these modules, see the Talend Enterprise ESBInstallation Guide.

You have the possibility to click on each component name to get a detailed description of it.

Note that modules have potential dependencies between them. So, if you choose to install modulesindividually, some settings might not be automatically passed on to other modules. For example, ifyou configure the CommandLine manually, you will have to go to the Talend Administration CenterWeb Application to configure the new CommandLine settings on the configuration page.




Choose the appropriate procedure among the following instruction sections. These sections are independent fromeach other.

3.5.1. Configuring Talend Administration Center

The next steps refer to the configuration of Talend Administration Center items.

For more information about this configuration, see the Section 3.3.1, “Configuring Talend Administration Center”.

In Custom mode, you can configure Talend Administration Center so that an SMTP server sends automatic emailnotifications. These notifications are alerts based on Talend Administration Center events, such as task failures.

For more information, see the Talend Administration Center User Guide.

Parameter Value

SMTP mail server Type in the IP address of your mail server.

SMTP port Type in the port of your mail server.

Mail user name Type in the email address and/or mailbox name of the recipient that will receive thenotification.

Mail password If your email server requires an authentication, type in the password corresponding tothe mailbox that will send the notification. If your message server is anonym, this fieldis optional.

• Enter the relevant information in the corresponding fields and click Next to go to the next step.

3.5.2. Configuring Talend Enterprise MDM Server

Talend Enterprise MDM Studio and Talend Enterprise MDM Web User Interface that make up require that youinstall a JBoss Server. For more information, see the Talend Enterprise MDM Installation Guide.

To install a JBoss Server, follow the procedure below:

Configuring Talend Enterprise MDM Server


1. Select either Install an embedded JBoss Server (recommended) or Use an existing JBoss installation inthe list.

The Install an embedded JBoss Server (recommended) option is selected by default.

2. In the JBoss port binding list, select the port number of the JBoss server you want to use. The port numberlist includes: 8080, 8180, 8280 and 8380.

Usually, the port number used for the JBoss server in the Custom type installation mode is 8080, whichis not the case with the Server type installation. Make sure to use the correct port when you set theserver URL in the MDM Studio login window.

If you have chosen the Install an embedded JBoss Server (recommended) option, click Next and go directly tothe next step, which is the Section 3.5.3, “Configuring Talend Data Stewardship Console”.

If you have chosen the Use an existing JBoss installation option:

Configuring Talend Data Stewardship Console



2. In the JBoss Path field, enter the path to the directory where your JBoss server is already installed, or browse

to this directory by clicking the button next to the field.


3.5.3. Configuring Talend Data Stewardship Console

You also have the possibility to install an integrated data stewardship console.

For more information, see the Talend Enterprise MDM Installation Guide.

There are two ways to install Talend Data Stewardship Console. Either it is installed automatically onthe same server of Talend Administration Center when sold with Talend Enterprise solutions, or it isinstalled on the MDM server when sold with Talend Enterprise MDM. If you want to install Talend DataStewardship Console on a different Tomcat server, you need to install it manually.

Configuring Talend Data Stewardship Console


1. On the next page, select either Install with MDM server (JBoss) or Install with Talend AdministrationCenter Server (Tomcat) in the first drop-down list.

2. In the second drop-down list, select either Install embedded HSQL-DB (recommended) or Use an existingMySQL database.

If you have chosen the Install embedded HSQL-DB (recommended) option, click Next and go directly to thenext step, which is the Section 3.5.4, “Configuring Talend CommandLine”.

If you have chosen the Use an existing MySQL database option:

Configuring Talend CommandLine


1. On the next page, enter the relevant connection information.

Field Description

Database Host MySQL database server IP address

Database Port Listening port number of MySQL database server

Database Name Name of the MySQL database to connect to

Database User Login name to the MySQL database

Database Password Password to the MySQL database

re-enter Enter your password again to confirm it

Note that the database must exist and that you must have full rights on this database.


3.5.4. Configuring Talend CommandLine

Talend CommandLine offers the same basic functionalities as Talend Enterprise Data Integration Studio withoutGUI. It also helps executing Jobs in batch mode for example.

For more information about the CommandLine, see User Guide.

Configuring SOA Manager


1. On this page, enter the CommandLine port number in the CommandLine port field. By default, it is 8002.


3.5.5. Configuring SOA Manager

According to your needs, you may also want to install the SOA Manager.

For more information, see Talend Enterprise Data Quality Installation Guide.

1. On this page, enter the SOA server port number in the SOA manager port field. By default, it is 8004.


3.5.6. Configuring Talend JobServer

This step allows you to define Talend remote execution servers, known as Talend JobServers.

For more information, see Talend Data Quality Installation Guide.

You can see that, by default, the JobServer is configurated as follows:

Command port 8000

File transfer port 8001

Monitoring port 8888

This corresponds to the configuration of a Job server on the system that hosts the Web application. For any othersystem, the host field should contain the IP address of the system. Check also that the ports 8000, 8001 and 8888are available.

Configuring Subversion Repository


If necessary, you can change the duration time of the cache in the Max cache duration (days) field. Thiscache helps improve the deployment time performance since it avoids libraries to be redeployed everytime a Job is deployed to a JobServer.

• Click Next to continue.

3.5.7. Configuring Subversion Repository

This section describes how to install or configure the SVN server. The SVN server is used to manage the persistenceof all the data relating to the objects stored in SVN mode in the Repository (Jobs, business models, metadata,routines, etc.).

For more information, see Section 2.1.3, “SVN” and Section 2.2.4, “SVN server”.

• On the next page, select either I will configure my SVN server later, Use an existing SVN server or Installan SVN Server locally (Linux Only) in the drop-down list.

If you have chosen the I will configure my SVN server later option, click Next and go directly to the next step,which is the Section 3.5.8, “Configuring Talend Enterprise Data Quality Portal”.

If you have chosen the Use an existing SVN server option:

1. On the next page, enter the relevant information:

Field Description

SVN URL URL address of the SVN repository

User name Login name to the SVN repository

Password Password to the SVN repository

2. Click Next to go to the next step, which is Section 3.5.8, “Configuring Talend Enterprise Data Quality Portal”.

If your machine runs under Linux, you can choose the Install an SVN Server locally (Linux Only) option.

For more information, see Talend Data Quality Installation Guide.

For Linux users: note that this installation WILL install an Apache server. Therefore, if you already havean Apache server, the existing one will be deleted.

Configuring Talend Enterprise Data Quality Portal


3.5.8. Configuring Talend Enterprise Data QualityPortal

This section provides information regarding the installation of Talend Enterprise Data Quality Portal.

For more information, see the Chapter 4, Talend Enterprise Data Quality Portal’s specific information.

1. According to your needs, select either Install an embedded (standalone) Tomcat server or Install withTalend Administration Center Server (Tomcat) in the first drop-down list.

2. In the second drop-down list, select either Connect to a MySQL database (selected by default) or Connectto an Oracle database.

3. Under the TDQ Portal Port field, type in the port number to connect to the portal. By default, it is 8580.

If you have chosen the Connect to a MySQL database option:

Field Description

Database host name (IP) MySQL database server IP address

Database port Listening port number of MySQL database server

Database name Name of the MySQLdatabase to connect to

User name Login name to the MySQL database

Password Password to the MySQL database

If you are using Talend Enterprise Data Quality Portal with your Talend Enterprise Data Quality Studioto extend the dynamic reporting and monitoring capabilities of the latter, make sure to use the same

Configuring Talend Enterprise Data Quality Portal


database name that is defined when installing Talend Enterprise Data Quality Portal. Note also that thedatabase must exist and that you must have full rights on this database. For further information, see theTalend Enterprise Data Quality User Guide.

To install the Talend Enterprise Data Quality Portal configuration successfully in the defined MySQLdatabase, make sure that the specified user has the following system privileges (otherwise the installationwill fail): “CREATE ANY TABLE”, “INSERT ANY TABLE”, “CREATE ANY VIEW”, “UNLIMITEDTABLESPACE”, “EXPORT FULL DATABASE”, and “ALTER SESSION”. Once Talend EnterpriseData Quality Portal is succesfully installed, you can log in with the following profiles: “tdq_admin/tdq“ (administrator) and “tdq_user/tdq“ (user).

1. Enter the relevant connection information to store Talend Enterprise Data Quality Portal configuration in yourdatabase, and click Next to continue the database configuration.

A progress information bar displays while the database connection is checked.

2. On the next page, create a database by entering the relevant connection information to store the Data Qualityreports and analysis in it, and click Next to go to the next step, which is the Section 3.5.9, “Installing Talendmodules as Services”.

If you have chosen the Connect to an Oracle database option:

Field Description

Database host name (IP) Oracle database server IP address

Database port Listening port number of Oracle database server

Database SID Name of the Oracle database to connect to

User name Login name to the Oracle database

Password Password to the Oracle database

If you are using Talend Enterprise Data Quality Portal with your Talend Enterprise Data Quality Studioto extend the dynamic reporting and monitoring capabilities of the latter, make sure to use the samedatabase name that is defined when installing Talend Enterprise Data Quality Portal. Note also that thedatabase must exist and that you must have full rights on this database. For further information, see TalendEnterprise Data Quality User Guide.

To install the Talend Enterprise Data Quality Portal configuration successfully in the defined MySQLdatabase, make sure that the specified user has the following system privileges (otherwise the installationwill fail): “CREATE ANY TABLE”, “INSERT ANY TABLE”, “CREATE ANY VIEW”, “UNLIMITEDTABLESPACE”, “EXPORT FULL DATABASE”, and “ALTER SESSION”. Once Talend Enterprise

Installing Talend modules as Services


Data Quality Portal is succesfully installed, you can log in with the following profiles: “tdq_admin/tdq“ (administrator) and “tdq_user/tdq“ (user).

1. Enter the relevant connection information to store Talend Enterprise Data Quality Portal configuration in yourdatabase, and click Next to continue the database configuration.

A progress information bar displays while the database connection is checked.

2. On the next page, create a database by entering the relevant connection information to store the Data Qualityreports and analysis in it, and click Next to go to the next step.

3. In the Full path to Oracle Import utility (imp.exe or imp) field, type in the path to the Import utility of yourOracle database. This utility reads the object definitions and table data from an export file into your database.

You can also browse to this utility by clicking the button next to the field.

4. Click Next to go to the next step.

3.5.9. Installing Talend modules as Services

This section allows you to set up all Talend components as services, which means that these components will startautomatically at every system boot.

1. According to your needs, choose which components to install as Services.


3. On the next page, click Next to confirm your settings and install the Talend server components you have chosento install.



Installing Talend modules as Services


A folder containing the Talend server components you chose is displayed on the installation directory you havepreviously defined.


Chapter 4. Talend Enterprise Data QualityPortal’s specific informationThis chapter provides useful information specific to Talend Enterprise Data Quality Portal installation.

Upgrade information


4.1. Upgrade information

4.1.1. Upgrading from v4.2Upgrading Talend Enterprise Data Quality Portal v4.2 to v5.0 is a transparent process that does not require anymanual operation.

4.1.2. Upgrading from a version prior to 4.2If you want to upgrade from a 4.2.x version of Talend Enterprise Data Quality Portal, please check the followingrequirements:

• Apache tomcat version 6.0.24+ must be installed;

• Mysql version 5.0+ must be installed and memory well configured;

• Operating System Linux 32/64 bits or Windows 32/64 bits;

• JDK 1.6.0_18+ must be installed;

• The JAVA_HOME environment variable must be defined and must point to the JDK directory;

For example, if the JDK path is C:\Java\JDKx.x.x\bin, you must set the JAVA_HOME environment variableto 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 anddoes 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 aroundthe path when setting the values for the environmental variable.

• Talend Enterprise Data Quality Studio version 4.0 must have been upgraded to v4.1, and a MySql datamart(“talend_dq” by default) must be configured from the Studio Preferences (in order to be set up automatically).For more information regarding the datamart set up parameters in Preferences, see Talend Enterprise DataQuality Portal User Guide.

• (optional) a mail server (to send the generated reports by email).

• (optional) Talend Enterprise Data Integration may be installed.

Your Talend contact will help you migrate first to 4.2 prior to migrate to 5.0.

4.2. Sending reports by emailIn order to be able to send by email the data quality reports launched from Talend Enterprise Data Quality Portal,you need to complete the following:

Edit the tomcat/webapps/tdqportal/WEB-INF/conf/config/mail.xml file and modify the SMPT address, the portand the email account that will be used to send the reports. You must also edit the scheduler notifications, the usernotifications and the alerts as in the below example:

<PROFILE name="scheduler"

smtphost="10.42.10.11"

LDAP configuration


smtpport="25" from="[email protected]" user="akhenouche" password="*******"/>

<PROFILE name="user" smtphost="10.42.10.11" smtpport="25" from="[email protected]" user="" password=""/>

<PROFILE name="kpi_alarm" smtphost="10.42.10.11" smtpport="25" from="[email protected]" user="akhenouche" password="*******"/>

4.3. LDAP configurationIn order to be able to manage LDAP users from Talend Enterprise Data Quality Portal, complete the followingsteps:

1. Edit the file (tomcat)/webapps/tdqportal/WEB-INF/conf/config/SpagoBI.xml:

define the xml text between  and  as comment

using the comment string (and 

2. Edit the file (tomcat)/webapps/tdqportal/WEB-INF/conf/webapp/ldap_authorizations.xml and modify theLDAP parameters of your LDAP server:

use the LDAP principal DN prefix to access the server using:

the administrator authentication information, for example:

<USER_DN>cn=*,ou=People,dc=talend,dc=com</USER_DN>

<ADMIN_USER>cn=admin,dc=talend,dc=com</ADMIN_USER>

<ADMIN_PSW>503b1c3fdcf46f180eaa70ecf4fb043e</ADMIN_PSW>

and the IP address and port of the LDAP server, for example:

<HOST>10.42.10.36</HOST>

<PORT>389</PORT>

3. Add users using the LDIF File template:

for example:

we consider DN: ou=People,dc=talend,dc=com

and group of users: ou=/spagobi/talend/tdq_user

LDAP configuration


To add a group of users, use the following LDIF template:

...

dn: ou=Group,dc=talend;dc=com

objectClass: top

objectClass: organizationalUnit

ou: Group

dn: ou=/spagobi/dev,ou=Group,dc=talend;dc=com


objectClass: top

description: /spagobi/dev

ou: /spagobi/admin

dn: ou=/spagobi/dev,ou=Group,dc=talend;dc=com


objectClass: top

description: /spagobi/dev

ou: /spagobi/dev

dn: ou=/spagobi/test,ou=Group,dc=talend;dc=com


objectClass: top

description: /spagobi/test

ou: /spagobi/test

dn: ou=/spagobi/user,ou=Group,dc=talend;dc=com


objectClass: top

description: /spagobi/user

ou: /spagobi/user

dn: ou=/spagobi/talendbi/tdquser,ou=Group,dc=talend;dc=com


Memory Configuration of the Tomcat server


objectClass: top

description: /spagobi/talendbi/tdquser

ou: /spagobi/talendbi/tdquser

...

To add new users, use the following LDIF template:

...

dn: cn=tdq_user,ou=People,dc=talend,dc=com

objectClass: organizationalPerson

objectClass: person

objectClass: top

cn: tdq_user

description: data quality user

ou: ou=/spagobi/talend/tdq_user,ou=Group,dc=talend,dc=com

sn: tdq_user

userPassword: dGRx

...

The crypted password dGRX is <tdq>

4.4. Memory Configuration of the TomcatserverIn order to be able to work with Talend Enterprise Data Quality Portal using Tomcat without having any memoryissues, you must increase the heap size memory of Tomcat.

Usually, a MaxPermSize = 1024m should be enough, but all depends if you have other applications that use theTomcat server.

For more information on how to increase the memory size of Tomcat, see Section 3.3.1.1, “Apache Tomcat serverconfiguration ”.

TalendEnterprise Installer UG 50a En

Documents

Transcript of TalendEnterprise Installer UG 50a En