Accessing Service Locator - 6.4

Talend Real-time Big Data Platform Installation Guide for Linux

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 Management
Talend Installer
Talend JobServer
Talend Log Server
Talend Project Audit
Talend Repository Manager
Talend Runtime
Talend SAP RFC Server
Talend Studio
Installation and Upgrade

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.

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:start-locator.

  3. To stop the Service Locator, type in the following command: tesb:stop-locator.

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


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



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


the location to store the in-memory database snapshots and, unless specified otherwise, the transaction log of updates to the database


the port to listen for client connections