Web Service Runtime Monitor

WS Infrastructure

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.

WS Errors

Runtime errors, aggregated into the two error types:

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

WS Performance

Checks if certain performance thresholds have been exceeded.

Infrastructure

Checks technical background services that are required by the Web service runtime infrastructure to run correctly. Some of the settings relate to the entire system, and some of them are client-specific.

Message Processing

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.

Status of WS Batch Jobs

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 background job BC_SAP_SOAP_RUNTIME_MANAGEMENT.

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

Setting of Default Trace Level

Shows whether a level different than the default trace level was chosen. For more information, refer to the section Monitoring the Web Service Runtime .

Task Watcher

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

For more information, refer to the section Monitoring Event-Controlled Processing .

Supervisor Destination

The configuration of the Web service runtime is client-specific and must be performed in each productive client and in client 000. This includes setting up a supervisor destination.

For more information, refer to Configuring the Web Service Runtime under the section Creating a Supervisor Destination .

WS Namespace for Inbound Destination

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.

For more information, refer to the section Troubleshooting in the Web Service Runtime .

WS Service Destinations

To be able to communicate using RFC, you must have defined a service destination in the sender system and have performed a number of settings. For more information, refer to Configuring the Web Service Runtime under the section Creating a Service-Destination .

Task Watcher

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. For more information, see Troubleshooting in the Web Service Runtime and Monitoring Event-Controlled Processing.

WS bgRFC Inbound Destination

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. For more information, refer to the section Troubleshooting in the Web Service Runtime.

Jobs

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

Service Destination

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.

For more information, see Configuring the Web Service Runtime under the section Creating a Service Destination.

Error Log Level

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.

For more information, see Configuring Logging.

Functional Trace Level

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.

For more information, see Configuring Tracing.

Payload Trace Level

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.

For more information, see Configuring Tracing.

Performance Trace Level

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.

For more information, see Configuring Tracing.

IDP State

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.

For more information, see Idempotent Web Services.

Configuration

WS Configuration

Application

WS Application

Runtime

WS Runtime, Proxy Runtime

Security

WS Security

Communication

Communication

System

Server-System

Conversion

XML Conversion

Mapping

Mapping