Using this monitor (part of the central NetWeaver Alert Monitor), you can check whether the Web service runtime works correctly. The Web Service Monitor triggers an alert if the Web service runtime does not function correctly.
The alert monitor consists of five areas:
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:
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.
|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.|
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.
The information in this article applies to the following releases of NetWeaver:
- 7.40 SP04
- 7.31 SP09
- 7.30 SP11
- 7.02 SP15
- 7.11 SP13
- 7.01 SP15
This article is also relevant for older releases, however, not all information may be accurate for them.
Changes to the structure of the nodes
The Infrastructure and Message Processing areas are new areas in the Web Service Runtime Monitor. You have the option to view alerts either in these areas, or in the older WS Infrastructure, WS Errors and WS Performance areas (you cannot view data in both). Use the SRT_CCMS_SET_COLL_VERSION report to determine which alerts are activated.
Data for the Infrastructure and Message Processing areas is only available if the CCMS Alerts based on Error Log setting in the SRT_CCMS_SET_COLL_VERSION report is activated. Alternatively, data for the WS Infrastructure, WS Errors and WS Performance areas is only available if the CCMS Alerts based on Log/Trace setting is active.
For areas that are not activated using this report, although they still appear in the Web Service Monitor, monitoring values are no longer collected and the Value is obsolete message will appear next to alerts after the system is next scheduled to collect data.
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 must have appropriate authorizations.
To start the Web Service Runtime Monitor:
Choose, or call transaction RZ20.
On the CCMS Monitor Sets screen, expand the SAP Web Service Monitor Templates node.
Start the Web Service Monitor in the monitor list by double-clicking it.
|Alerts in WS Infrastructure||Description|
|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 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.
|Setting of Default Trace Level||Shows whether a level different than the default trace level was chosen.|
The Task Watcher runs in the background and is started by AUTOABAP. AUTOABAP is a background process that is automatically started every 5 minutes.
|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.|
|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.
|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.|
The WS Errors and WS Performance nodes are no longer maintained. The content in WS Errors is now found in Message Processing.
|Alerts in Infrastructure||Description|
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.
|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.
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:
|WSRM Event Handling (7.01, 7,11 only)|
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.
|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.
|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.
|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.
|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.
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.
|Alerts in Message Processing||Error Category in Web Service Error Log (SRTUTIL)|
|Runtime||WS Runtime, Proxy Runtime|
How often data is collected for the different nodes depends on the method used to retrieve the data:
- Auto-ABAP - High frequency, every 5 minutes (maximum)
- CCMS Batch Report - Low frequency, every hour (maximum)
The table below lists the data collection frequency for the nodes in the Infrastructure and Message Processing categories:
|Node||Data Collection Frequency|
|WS bgRFC Inbound Destination||Low|
|WSRM Event Handling (7.01, 7,11 only)||Low|
|Error Log Level||High|
Functional Trace Level
Payload Trace Level
Performance Trace Level
|All nodes in Message Processing||High|