Once the Service Locator
feature configured to work in your Talend Runtime container(s), you can install
and run it.
Procedure
-
Start the container:
-
container/bin/trun.bat for Windows,
-
container/bin/trun for Linux.
New files appear in the container/etc directory. -
-
If you need to configure the Service Locator server, edit the
configuration file named:
org.talend.esb.locator.server.cfg.
The parameters available are the following:
tickTime=2000 initLimit=10 syncLimit=5 dataDir=${karaf.base}/zookeeper/data clientPort=2181 maxClientCnxns = 0 authentication = false
Here is a description for each of the 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. -
Now that you have configured the Service Locator, you can start it in
the Talend Runtime Container. To do so, execute the following command at
the console prompt:
tesb:start-locator
-
To check that the service has been successfully started and is
active, execute the console command:
list | grep Locator
You should see an output similar to this:ID State Blueprint Spring Level Name [ 211] [Active ] [Created ] [ ] [ 80] Talend ESB :: Locator :: Server ()
To ensure that the feature is installed successfully, you can try examples that use the Service Locator server.
To uninstall and stop the Service Locator, execute the console command:
tesb:stop-locator