Requirements for Service Monitoring
Service Monitoring uses the audit data that Integration Server logs into the service log. This service log requires an external database.
To be able to monitor services and documents in Integration Server, you must set up the Integration Server environment as follows:
Install
Integration Server and the WmMonitor package (see
Installing Software AG Products)
Configure the
Integration Server that hosts the WmMonitor package to connect to an external database (see
Installing Software AG Products)
Create the ISCoreAudit database component on the external database (see
Installing Software AG Products)
Create the ProcessAudit database components on the external database and then assign the ProcessAudit JDBC function to the appropriate JDBC pool alias. Service monitoring requires the ProcessAudit database components even if process runtime (PRT) is not installed. For information about creating the ProcessAudit database components, see
Installing Software AG Products.
Configure and enable the service logger and the document logger for the
Integration Server that hosts WmMonitor (see
webMethods Audit Logging Guide)
Enable audit logging for each service (see
webMethods Service Development Help)
To monitor services and documents executed on remote
Integration Servers, the
Integration Server that hosts WmMonitor and the remote
Integration Servers must share the same external database.
For detailed information about Integration Server logging, see webMethods Audit Logging Guide.
To be able to archive the data from the ISCoreAudit database component, you must:
Create an Archive database component using the Database Component Configurator (see
Installing Software AG Products)
Create a JDBC database connection pool (see Creating a Connection Pool in
webMethods Integration Server Administrator’s Guide)
Point the Archiving function at the JDBC database connection pool alias (see Pointing Functions at Connection Pools in
webMethods Integration Server Administrator’s Guide).