Configuring the Service Activity Monitoring Server in a Servlet container

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

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!