Monitoring the Web Service Runtime

In the AS ABAP, different tools for monitoring the correct functioning of the Web service runtime are at your disposal. You can deal with any errors that may occur using the tools provided.

Monitoring the Web service runtime is part of the central monitoring operation (for more information, refer to Central  Monitoring ).

The following tools are provided for monitoring the Web service runtime:

• Web Service Runtime Monitor

  The Web Service Runtime monitor triggers an alert if problems occur during the configuration of the Web service runtime, if there are runtime errors of different error categories, and whenever there are performance bottlenecks after certain threshold values have been exceeded.

• Logs and Tracing (SOA Manager)
  • The logging function provides information on processing steps in the SOAPruntime. With the tracing function, you can analyze errors or performance problems in detail.
  • First configure the logging and tracing. Configuring Logging , Configuring Tracing , Searching with Trace Patterns
  • Then display the information: Displaying Logs and Traces
  • Changes to the SOA configuration and publications are also logged in addition to this.

    More information: Evaluating SOA Configuration and Publication Logs , Activating and Forwarding SOA Configuration Traces

• Monitoring Sequences in the SOA Manager

  With Web Services Reliable Messaging , messages are grouped together into sequences. Using the analysis tools of the sequence monitor, you can find and remove any errors that occur during transmission.

• Monitoring Event-Controlled Processing

  When you are searching for errors, check whether the Event Handler and the Task Watcher are being started at regular intervals. This is another prerequisite for reliable message transmission and transaction processing in the SOAPruntime. 

• Debugging bgRFC Units

  You can debug a Web service with errors on the provider side using units of the bgRFC (Background Remote Function Call) .