Web Service Runtime Monitor

Using this monitor, you can check the correct functioning of the Web service runtime.

To be able to use the information content of the data in an optimum manner, you should have knowledge of how to use the Alert Monitor.

The administrator has the appropriate Authorizations.

To start the monitor, follow the procedure below:

Choose CCMS Control/Monitoring Alert Monitor , or call transaction RZ20.
On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
Start the Web Service Monitor in the monitor list by double-clicking it.

Area:	Analysis:
WS Infrastructure	Are the required background jobs for the Web service runtime monitors 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	The system manager finds the runtime errors as aggregated values of different error categories. There are the following error types: System error Application error (caused by Web service applications)
WS Performance	Performance bottleneck when certain threshold values are exceeded

Area:

Analysis:

WS Infrastructure

Are the required background jobs for the Web service runtime monitors 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

The system manager finds the runtime errors as aggregated values of different error categories.

There are the following error types:

System error

Application error (caused by Web service applications)

WS Performance

Performance bottleneck when certain threshold values are exceeded

Features

Alert in the WS Infrastructure area	Meaning:
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.
WSRM Event Handler	Proper functioning of the event handler is a prerequisite for dependable messaging. For more information, refer to the section Monitoring Event-Controlled Processing.
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.