The data source for the metric "Number of Web Service Exceptions" is the web service error log (transaction SRT_LOG). When you activate this metric, Solution Manager automatically creates customizing in Exception Management to capture the web service errors from this log. The customizing uses a filter on the column "Interface Name" in the error log. The value for this filter is the value you entered in the field "WS name" or "WS proxy".
The input help for the field "WS name" or "WS proxy" will return the internal name as known in transaction SOAMANAGER.
Unfortunately for asynchronous web services, this is not the value that is used for the column "Interface" in the web service error log. Instead the error log uses the ABAP name in this column. However the internal name is used to identify the web service in STAD to measure the number of web service executions and the web service performance. Hence, for asynchronous web services we have to distinguish between the filter values used for the collection of performance metrics and the filter values used to collect exceptions.
As a workaround you can create two line items (two interfaces) for each asynchronous web service in your web service channel.
- Interface 1: Use the internal name to satisfy the performance metrics
- Interface 2: Use the ABAP name to satisfy the exceptions metric
You can use the same "Interface Name" for both interfaces.
To find out the ABAP name of an asynchronous web service use transaction SPROXY.
- Open transaction SPROXY
- Click the 'Open Object' button
- Switch to the tab 'Web Service Definition'
- Enter the internal web service name
- Switch to the view 'Internal View'
- There you find the ABAP name