Web Service Runtime Monitor

Checks that the required background jobs for monitoring the Web service runtime are running.

Which trace level is set?

Note: If the trace level has a value higher than 1, this can cause a performance bottleneck.

Note: This area is avalable up to and including 7.31.

Runtime errors, aggregated into the two error types:

• System errors (for example, system shutdowns and network errors)
• Application errors (caused by Web service applications)

Note: WS Errors is an older implementation of alerts for runtime errors. It is is avalable up to and including 7.31. The content has been reorganized under Message Processing, below.

Checks if certain performance thresholds have been exceeded.

Note: This area is avalable up to and including 7.31.

Displays the most important errors from the Web service error log. For each error category, the information from the error log is displayed for each client.

If you display an alert for the client you are currently logged on to, you can navigate to the error log directly from the alert monitor. Note that the alert monitor and the error log use different time periods for their analyses. Therefore, the number of entries in the error log and in the alert monitor can differ slightly.

Shows whether standard background processes are running. For the status check, choose Standard Jobs in transaction SM36.

The job list shows two entries for the BC_SAP_SOAP_RUNTIME_MANAGEMENT background job.

One with the status completed and the other with the status released. All the other entries point to an error.

The Task Watcher runs in the background and is started by AUTOABAP. AUTOABAP is a background process that is automatically started every 5 minutes.

The name of the bgRFC destination is maintained in two different areas. One is in the general configuration of the bgRFC and the other in the configuration of the WS runtime. It is possible that two different values were set for the bgRFC destination - for example, through manually setting up an inbound destination in an area. This results in problems when scheduling sequences.

Task Watcher runs in the background and is started by AUTOABAP. AUTOABAP is a background process that is automatically started every 5 minutes.

An alert is shown if Task Watcher is not configured properly.

The name of the bgRFC inbound destination is specified in two different areas: In the general configuration of the bgRFC and in the configuration of the WS runtime. If it is not configured, an alert is displayed.

You can define the bgRFC inbound destination in transaction SRT_ADMIN.

Shows whether the standard background processes are running. There is one job that makes sure all of these jobs are running correctly.

For the status check, choose Standard Jobs in transaction SM36 and see whether BC_SAP_SOAP_RUNTIME_MANAGEMENT is released. If not, check the job protocol to see which of the following jobs has errors:

SAP_SRT_REORG_LOG_TRACE

SAP_SRT_SEQ_DELETE_BGRFC_QUEUES

SAP_SRT_SEQ_DELETE_TERM_SEQ

SAP_SRT_SEQ_SOFT_TERM_RFC

SAP_SRT_UTIL_CLEANUP

SAP_SRT_UTIL_PERSIST_CHECK

SAP_SRT_UTIL_PERSIST_CLEANUP

SAP_WSSE_TOKEN_CACHE_CLEANUP

Proper functioning of the event handler is a prerequisite for dependable messaging.

Note: This alert only exists in 7.01 and 7.11. The alert was removed and no longer exists in 7.02 SP15, 7.30 SP11 and 7.31 SP09.

To be able to communicate using RFC, you must have defined a service destination in each client of the sender system and have performed a number of settings.

The error log level can be set in the Web Service Support Utilities (transaction code SRT_UTIL). If it has been set to inactive, an alert is displayed to inform the administrator about the fact that errors that occur in the Web service runtime are not being logged.

The functional trace level can be set in the Web Service Support Utilities (transaction code SRT_UTIL). The functional trace is usually only necessary when a specific problem is being analyzed. If it is active, an alert is displayed.

The payload trace level can be set in the Web Service Support Utilities (transaction code SRT_UTIL). The payload trace is usually only necessary when a specific problem is being analyzed. Otherwise, it uses up space in the database unnecessarily. If it is active, an alert is displayed.

The performance trace level can be set in the Web Service Support Utilities (transaction code SRT_UTIL). The performance trace is usually only necessary when a specific problem is being analyzed. If it is active, an alert is displayed.

Idempotence state. The service that ensures messages sent via synchronous communication are processed only one time in the case when no response is received. This could be due to either the original message not being received by the Web service provider, or communication of the response was interrupted. The IDP service ensures that when the message is resent by the service consumer, the message ID can be checked to determine if the required business logic has already been executed or not.

Functional Trace Level

Payload Trace Level

Performance Trace Level