Web Services are a standardized way of communication between a client application which consumes e.g. information from a server application in service-oriented architectures. SAP NetWeaver Application Server ABAP can be used both as a provider and a consumer of Web services. You can create, configure, publish, and consume services.

The communication using web services needs to be monitored for errors and performance issues to ensure a smooth information flow.

Performance measurements are based on Real-User Monitoring (RUM) which is also a part of SAP Focused Run. When Web Service performance monitoring is set up, RUM is automatically configured in the background.

Available Monitoring Categories

For Web Service Monitoring, different monitoring categories are available:

• Web Service (Performance): Can be collected for SAP Java systems or for SAP ABAP systems
• Web Service Messages (ABAP): Web Service messages collected from SRT_UTIL → Message Monitor. Can be collected for ABAP systems.
• ABAP Web Service Consumer: Web service exceptions collected from the SRT_UTIL → Error Log. Can be collected for ABAP systems.
• ABAP Web Service Provider: Web service exceptions collected from the SRT_UTIL → Error Log. Can be collected for ABAP systems

For the category 'Web Service Messages (ABAP)' you can collect payload information from the web service message and display this payload in the AIM application in SAP Focused Run. You can then use this information to search for related messages in PI or CPI, related IDocs, or related web service calls. Find out how to set up the collection of payload information under Collecting Business Context for AIM.

Available Filter Options

For all monitoring categories, you can opt to use the default filter, that collects all web service communication. You can also use the following filters to restrict the web service communication:

Web Service Messages (ABAP)

• Processing Status Group: The status group of the message. Please use the input help to select a status group
• Adapter Type: The adapter used for the WS. Please use the input help to select an adapter.
• Sender Party: Sender Communication party
• Sender Interface Name: Sender Interface
• Receiver Party: Receiver Communication party
• Receiver Interface Name: Receiver Interface
• User Name: Login name of the user.
• Payload Field Name: User Defined Selection search field

Web Service (Performance)

• Web Service Name: The name of the web service called
• Method: The called web service method

ABAP Web Service Consumer

• Host: Application Server as in the Error Log
• Message: Short Text in the Error Log
• Proxy Name: Interface Name in the Error Log
• User: User in the Error Log

ABAP Web Service Provider

• Host: Application Server as in the Error Log
• Message: Short Text in the Error Log
• WS Name (Proxy): Interface Name in the Error Log
• User: User in the Error Log

Available Metrics

The following metrics are collected for the different web service categories:

Web Service Messages (ABAP)

• Number of Web Service messages: The metric specifies the number of Web Service messages within the collection interval.
• Average Web Service response time [ms]: The metric specifies the average runtime of successful Web Service messages in milliseconds within the collection interval.
• Number of erroneous Web Service messages: The metric specifies the number of erroneous Web Service messages within the collection interval.

Web Service (Performance)

• Web Service Response Time: The average response time of the Web Service requests as collected by RUM

ABAP Web Service Consumer

• ABAP Web Service Consumer exceptions: Indicates that ABAP Web Service Consumer exceptions were collected during the last collection period

ABAP Web Service Provider

• ABAP Web Service Provider exceptions: Indicates that ABAP Web Service Provider exceptions were collected during the last collection period