About Service Monitoring
When you run services on Integration Server, you can monitor the following:
Audit data for flow and coded (for example, Java) services
Integration Server documents that are in doubt, that have failed, or that have exhausted trigger retries (see
Publish-Subscribe Developer’s Guide)
Documents that
webMethods Broker (deprecated) clients publish or to which they subscribe
Error details for services and documents
You can use the data you obtain when monitoring a service to track when the service started and completed, and whether a service execution is successful or failed. If you execute a root service (that is invoked directly by a client or by a webMethods Messaging Trigger), you can edit the pipeline of the service and resubmit it. You can also edit and resubmit documents.
To ensure that Service Monitoring is at peak performance, you can archive or delete the monitored data for past periods.
To use Service Monitoring, you log on to the administration user interface of the Integration Server that hosts the WmMonitor package.