Run the Monitoring Server

The Monitoring Server can be run on the Talend Runtime Container or in an embedded Jetty server, but only the Talend Runtime Container way is covered here.

A data source using an Apache Derby database is provided as default backend of the service activity monitoring server. This database is good for development and testing purposes, but it is not recommended for production because it has known limitations which may affect security also.

The Service Activity Monitoring configuration file is <TalendRuntimePath>/container/etc/org.talend.esb.sam.server.cfg. Please edit this file if you want to change the default values:

monitoringServiceUrl=/MonitoringServiceSOAP
db.driver=org.apache.derby.jdbc.ClientDriver
db.url=jdbc:derby://localhost:1527/db;create=true
db.username=test
db.password=test
db.incrementer=derbyIncrementer

db.recreate=true
db.createsql=create.sql

Then start the OSGi container by running <TalendRuntimePath>/container/bin/trun.bat on Windows or <TalendRuntimePath>/container/bin/trun on Linux. Once the OSGi Container is started, you can setup the server by executing the following commands on the OSGi Console:

feature:install tesb-derby-starter
feature:install tesb-sam-server
feature:install tesb-sam-agent

The Database, sam-server and sam-agent will be installed and are ready to be used.