Duplicating Tomcat and the TAC web application - 7.3

Talend Installation Guide

Operating system
Subscription type
Talend Big Data
Talend Big Data Platform
Talend Data Fabric
Talend Data Integration
Talend Data Management Platform
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Talend Activity Monitoring Console
Talend Administration Center
Talend Artifact Repository
Talend CommandLine
Talend Data Preparation
Talend Data Stewardship
Talend DQ Portal
Talend ESB
Talend Identity and Access Management
Talend Installer
Talend JobServer
Talend LogServer
Talend MDM Server
Talend MDM Web UI
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio
Installation and Upgrade
Last publication date


  1. Duplicate this Tomcat instance on different servers, as many times as needed.
    Warning: Having different Talend Administration Center Tomcat servers on the same OS instance is not supported when configuring high availability.
    Warning: Make sure that system clocks of databases and servers are synchronized (the clocks must be within a second of each other). For more information on time-sync services, please refer to the appropriate Microsoft documentation about SNTP, Windows Time Service tools and Network Clocks.
  2. Duplicate the org.talend.administrator Web application to all Tomcat instances. Make sure that all Web application configurations are identical.
  3. For each Tomcat instance, open configuration.properties file in the <TalendAdministrationCenterInstallationDirectory>/apache-tomcat/webapps/org.talend.administrator/WEB-INF/classes folder and set the value of node.identifier= parameter.
    Warning: Check that each Tomcat instance (or node) has a unique node identifier in the cluster.
  4. Launch one Tomcat instance following the commands given in Deploying Talend Administration Center on Tomcat.
  5. Launch the other instances of Tomcat following the same procedure.


Fail-over will occur when one of the multiple execution servers fails while in the midst of executing one or more tasks. When a server fails, the other servers of the cluster detect the condition and identify the tasks in the database that were in progress within the failed server. Any tasks marked for recovery will be taken over by another server.

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

Tip: One known minor issue related to the DST change might prevent the failover to operate correctly. To work around this issue, restart Tomcat after the time change. This should have no impact on executions.