Service Locator installation as an OSGi bundle

Procedure

You first need to start the Talend Runtime Container and start the Service Locator feature via the tesb:start-locator. For more information on how to start them, see Starting Service Locator and Starting and stopping the Authorization service in the Talend Runtime Container.
Once the Service Locator feature started, a container/etc/org.talend.esb.locator.server.cfg configuration file is created. It is the Talend ESB equivalent to the ZooKeeper zoo.cfg configuration file.
Edit it and change the settings as follows:
```
tickTime=2000 
dataDir=./var/locator 
clientPort=2181
```
- The tickTime refers to the basic unit of time measurement used by ZooKeeper, used for later configuration of timeouts and other parameters.
- The dataDir holds database snapshots and transaction logs. Check the ZooKeeper Administration Manual for information on all possible parameters.
- The clientPort number should be same as the endpointPrefix defined in LocatorFeature above.
The ZooKeeper AdminServer is disabled by default with JVM parameters. To enable this feature, edit <TalendRuntimePath>/bin/setenv or <TalendRuntimePath>/addbin/setenv.bat as follows and set the proper available port.
```
-Dzookeeper.admin.enableServer=true Dzookeeper.admin.serverPort=<AVAILABLE PORT>
```
For more information on the ZooKeeper AdminServer, see the ZooKeeper AdminServer configuration.
Information noteNote: If Talend Runtime is installed as a service, the service's wrapper configuration file must be updated to include the JVM Parameters. For example:
```
wrapper.java.additional.XX=-Dzookeeper.admin.enableServer=true 
wrapper.java.additional.XX=-Dzookeeper.admin.serverPort=9090 
```
where "XX" should be the next integer in the series.
Restart the Container.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!

Leave your feedback here