Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

Configuration of Web Service Channels

Interface Channel Setup

Available Monitoring Templates

For Web Service Channels two different monitoring templates are available:

Monitoring TemplateDescription
Web Service ABAP (SOAP)This template provides metrics to monitor the response time, the number of executions and whether exceptions of synchronous web services occurred in the managed ABAP system. The data is collected via the enterprise extension /SDF/WS_MON which has to be activated in the Switch Framework.
 Web Service ABAP (STAD)This template provides metrics to monitor the response time, the number of executions and whether exceptions of web services occurred in the managed ABAP system. The data is collected from STAD in the ABAP system.
Web Service (Introscope)This template provides metrics to monitor the response time, the number of executions and whether exceptions of synchronous web services occurred in the managed NON-ABAP system.

The used monitoring template is selected during the creation of the interface channel. This selection cannot be revised after the channel creation. To change the assigned template you will have the recreate the channel.

Monitoring Template “ Web Service ABAP (SOAP) ”

System Requirements

The following technical prerequisites have to be met in order to use this template:

  • Basis release ≥ 7.0 on all managed systems
  • Switch enabled as described in note 1639329

Please follow the description in step "Preparation" activity "Activate Web Service Monitoring" to activate Web Service monitoring capabilities in the managed system.

Available Metrics

Supported Web Service Types

This monitoring template only supports synchronous Web Services. Only web service calls using the SOAP runtime can be measured. PI web services are not instrumented with this template.

You can check in statistics records which protocol is used. Call transaction STAD after the webservice was executed. Select the correct time interval and task type 9. Select OK. Double-click on the right entry to display the single statistical record details. Press button Web Service and check the Web Service Records .

Currently only the WS protocol is supported.

PI Protocol is not supported by this template:

Metric Name

Description

MAI Category

 SP

WS Channel available

Availability measured by a script

Availability

7.1 SP 05 

Number of AppLog Errors (WS)

Exceptions from Application log (SLG1)

Exceptions

7.1 SP 05 

Number of Web Service Exceptions

Exceptions from SRT_UTIL

Exceptions

7.1 SP 05

Number of WS executions below threshold

Number of executions below a defined threshold

Performance

7.1 SP 12

Percentage of WS executions below threshold

Percentage of executions below a defined threshold

Performance

7.1 SP 12

Average WS Response Time

Average WS Response Time in ms

Performance

7.1 SP 05

Average WS Response Time per Instance

Average WS Response Time per Instance in ms

Performance

7.1 SP 08

Number of WS executions

Number of WS executions

Performance

7.1 SP 05

Number of WS executions per Instance

Number of WS executions per Instance

Performance

7.1 SP 08

Configuration

The interface is characterized by Web Service / Web Service Method / Logical Port (if you monitor on client side) and/or Web Service User (if you monitor on server side). Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection.

 

After maintaining the necessary information to identify the correct Web Service you can select the metrics you are interested in. You will see that some metrics are pre-selected. These metrics are the most common metric to monitor.

 

Performance Warning

Because of potentially high data volume instance specific data collection is turned off by default.

For some metrics you need to maintain additional metric specific parameters.

  • WS Channel available: Enter the name of the EEM script you want to use to check the WS availability. To learn how to record the EEM script please refer to the wiki page ICMon Availability Script.
  • Number of AppLog Errors (WS): Here you can monitor application log entries created by the monitored web services. Enter Object and Sub-Object of the application log messages the web services create when being called and specify the technical system in which the application log entries shall be monitored. Please note: This metric is optional. It should only be activated if the web services calls trigger the creation of application log messages and you are aware of the right category and subcategory in the application log. Not all web service calls trigger the creation of application log messages. The use of wildcards “*” is not supported for category and subcategory.
  • Number of WS executions below threshold : Maintain the threshold for the Web Service execution in milliseconds

The thresholds for the metrics are set in the step "Activation" of the IFMon setup. 

WebService Performance Monitoring

In addition to the WebService metrics available in the IC Mon UI, a dedicated WebService Performance Monitoring for ABAP based Webservices is offered.

Monitoring Template “ Web Service ABAP (STAD) ”

With SAP Solution Manager 7.2 SP 05 we created a new data collector that can extract web service performance information from STAD in the ABAP managed system. No additional business function needs to be activated for this functionality. Also this supports SOAP as well as PI web service calls.

System Requirements

The following technical prerequisites have to be met in order to use this template:

  • SAP Solution Manager 7.2 SP 05

Available Metrics

Metric Name

Description

MAI Category

SP 

WS Channel available

Availability measured by a script

Availability

7.2 SP 05

Number of AppLog Errors (WS)

Exceptions from Application log (SLG1)

Exceptions

7.2 SP 05

Number of Web Service Exceptions

Exceptions from SRT_UTIL

Exceptions

7.2 SP 05 

Average WS Response Time (STAD)

Average WS Response Time in ms

Performance

7.2 SP 05

Number of WS executions (STAD)

Number of WS executions

Performance

7.2 SP 05

Configuration

The interface is characterized by Web Service / Web Service Method / Logical Port (if you monitor on client side) and/or Web Service User (if you monitor on server side). Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use wildcards, which will result in single metrics reported for each match during data collection.

 

After maintaining the necessary information to identify the correct Web Service you can select the metrics you are interested in. You will see that some metrics are pre-selected. These metrics are the most common metric to monitor.

 

For some metrics you need to maintain additional metric specific parameters.

  • WS Channel available: Enter the name of the EEM script you want to use to check the WS availability. To learn how to record the EEM script please refer to the wiki page ICMon Availability Script.
  • Number of AppLog Errors (WS): Here you can monitor application log entries created by the monitored web services. Enter Object and Sub-Object of the application log messages the web services create when being called and specify the technical system in which the application log entries shall be monitored. Please note: This metric is optional. It should only be activated if the web services calls trigger the creation of application log messages and you are aware of the right category and subcategory in the application log. Not all web service calls trigger the creation of application log messages. The use of wildcards “*” is not supported for category and subcategory.

The thresholds for the metrics are set in the step "Activation" of the IFMon setup. 

Monitoring Template “ Web Service (Introscope) ”

System Requirements

The following technical prerequisites have to be met in order to use this template:

  • SAP J2EE system or Apache Tomcat
  • Managed System Setup has been executed for this system
  • Metrics are aggregated in Introscope Enterprise Manager to system level (agentcluster.xml) 

Available Metrics

Metric Name

Description

MAI Category

 SP

WS Channel available

Availability measured by a script

Availability

 7.1 SP 05

Number of Web Service Exceptions (Introscope)

Number of SOAP Faults Per Interval

Exceptions

 7.1 SP 06

Average WS Response Time (Introscope)

Average Response Time (ms)

Performance

 7.1 SP 06

Number of WS executions (Introscope)

Responses Per Interval

Performance

 7.1 SP 06

Restrictions

  • Only outgoing web service calls can be measured.
  • Metrics are always retrieved from the Introscope Enterprise Manager for the source system.

Configuration

The interface is characterized by Web Service and Operation (Web Service Method). Leaving a parameter empty will result in an aggregation over this parameter. You also have the possibility to use regular expressions, which will result in single metrics reported for each match during data collection.

Four metrics are available for this kind of interface channel. For the metric WS Channel available you have to maintain the EEM script used to check the WS availability as metric specific parameter.

EEM Configuration

As prerequiste for using EEM scripts as availability EEM does not need any robot but needs to be configured in SOLMAN_SETUP under Technical Monitoring → (End)-User Experience Monitoring → Step 2.2  to step 2.4 until activity Create Logical Ports.

 

The thresholds for the metrics are set in the step "Activation" of the IFMon setup.

  • No labels