Alternative installation of the Service Locator

The Service Locator can also be installed as standalone:

1. Navigate to <TalendRuntimePath>/zookeeper or the root of the unpacked Apache ZooKeeper package.

2. To start the Service Locator, a configuration file is needed, so create this file. Its default name is conf/zoo.cfg, but you can give it a different name.

3. It must contain the following configuration parameters:

   tickTime=2000
   initLimit=10
   syncLimit=5
   dataDir=/zookeeper/data
   clientPort=2181
   maxClientCnxns = 0

   Here is a description for each of the possible fields:

   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.
   initLimit	The number of ticks that the initial synchronization phase can take.
   syncLimit	The number of ticks that can pass between sending a request and getting an acknowledgment.
   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.
   maxClientCnxns	Number of client connection. Default is 10. 0 is unlimited.
   authentication	To enable the authentication in the Service Locator server.

4. Change the value of dataDir to specify an existing, initially empty directory.

5. Now that you have created the configuration file, you can start the Service Locator server. The <TalendRuntimePath>zookeeper/bin directory contains scripts that allow easy access (classpath in particular) to the Service Locator server and command-line client:

   • bin/zkServer.sh start [configFilename] (Linux)

   • bin/zkServer.cmd start [configFilename] (Windows)

   Where configFilename needs to be specified if it is not the default zoo.cfg configuration file.

   These steps run the Service Locator in standalone mode. There is no replication, so if the Service Locator process fails, the service will go down, so you may want to consider using a replicated Service Locator. For more information, see Running a replicated Service Locator.