Configuring the Service Activity Monitoring Server

The main configuration files for the Service Activity Monitoring Server are <Talend.runtime.dir>/container/etc/org.talend.esb.sam.server.cfg, <Talend.runtime.dir>/container/etc/org.talend.esb.sam.service.soap.cfg, <Talend.runtime.dir>/container/etc/org.talend.esb.sam.service.rest.cfg, and filter, handler configuration files.

The sam-server bundle is configured in the <Talend.runtime.dir>/container/etc/org.talend.esb.sam.server.cfg file.

Properties description:

Property	Default	Description
db.datasource	ds-derby	DataSource name used by the Service Activity Monitoring Server to store/query data. For J2EE or Tomcat, it should be like java:comp/env/<Resource name>, for OSGi container, use similar to ds-<Database>.
db.dialect	derbyDialect	The database used to store/query Event data (with different ID Incrementer, Query, and so on.)

For Derby:

db.datasource=ds-derby
db.dialect=derbyDialect

For H2 Database Engine:

db.datasource=ds-h2
db.dialect=h2Dialect

For Mysql 5.x:

db.datasource=ds-mysql
db.dialect=mysqlDialect

For MySQL 8.x:

db.datasource=ds-mysql8
db.dialect=mysqlDialect

For Oracle:

db.datasource=ds-oracle
db.dialect=oracleDialect

For IBM DB2:

db.datasource=ds-db2
db.dialect=DB2Dialect

For SQL Server:

db.datasource=ds-sqlserver
db.dialect=sqlServerDialect

For PostgreSQL:

db.datasource=ds-postgresql
db.dialect=postgresqlDialect

The sam-service-soap bundle is configured in the <Talend.runtime.dir>/container/etc/org.talend.esb.sam.service.soap.cfg file.

Properties description:

Property	Default	Description
monitoringServiceUrl	/MonitoringServiceSOAP	The address URL published by the Service Activity Monitoring Server

The sam-service-rest bundle is configured in the <Talend.runtime.dir>/container/etc/org.talend.esb.sam.service.rest.cfg file.

Property	Default	Description
sam.authentication	NO	NO - No security scenario SAML - SAML token scenario BASIC - Basic scenario
security.signature.properties	file:${tesb.home}/etc/keystores/serviceKeystore.properties	Link to the properties file which contains signature parameters.
security.signature.username	myservicekey	The signature username.
security.signature.password	${env:TESB_CLIENT_KEY_PASSWORD:-${TESB_CLIENT_KEY_PASSWORD}}	The signature password that is resolved as reference to environment variables. First the OS environment is queried. If the parameter is not set as an OS environment variable, the Java system variables set in etc/custom.properties are queried.

For filter and handler configuration, please refer to Configuring the Service Activity Monitoring Agent.

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