Configuring the Service Activity Monitoring Server in a Servlet container - 8.0

Talend ESB Infrastructure Services Configuration Guide

Version
8.0
Language
English
Product
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Real-Time Big Data Platform
Module
Talend ESB
Talend Runtime
Content
Design and Development
Installation and Upgrade
Last publication date
2024-03-13

The main configuration files for the Service Activity Monitoring Server are logserver.properties and filter, handler configuration files.

Properties description:

Property

Default

Description

monitoringServiceUrl   The address URL published by the Service Activity Monitoring Server
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:

monitoringServiceUrl=/MonitoringServiceSOAP
db.datasource=java:comp/env/jdbc/datasource
db.dialect=derbyDialect

For H2 Database Engine:

monitoringServiceUrl=/MonitoringServiceSOAP
db.datasource=java:comp/env/jdbc/datasource
db.dialect=h2Dialect

For Mysql:

monitoringServiceUrl=/MonitoringServiceSOAP
db.datasource=java:comp/env/jdbc/datasource
db.dialect=mysqlDialect

For Oracle:

monitoringServiceUrl=/MonitoringServiceSOAP
db.datasource=java:comp/env/jdbc/datasource
db.dialect=oracleDialect

For IBM DB2:

monitoringServiceUrl=/MonitoringServiceSOAP
db.datasource=java:comp/env/jdbc/datasource
db.dialect=DB2Dialect

For SQL Server:

monitoringServiceUrl=/MonitoringServiceSOAP
db.datasource=java:comp/env/jdbc/datasource
db.dialect=sqlServerDialect

For filter and handler configuration please refer to Configuring the Service Activity Monitoring Agent in a Servlet container.