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 collector 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.

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.

Navigate to the step 'Define Scope'. You can create a new scenario or use an existing one. Make sure the sender and the receiver system are part of the Interface and Connection Monitoring scenario.

Create the Interface Channel:

1. Select the scenario and click 'Next'
2. In step 'Preparation' perform all relevant manual activities and run all automatic activities.
3. In step 'Configuration' click the 'Add' button.
   • Channel Name: Enter a meaning full name (max. 30 characters)
   • Type: Select 'Web Service'
   • Monitoring Template: Select 'Web Service ABAP (STAD)'
   • Description: Enter a description for the channel
4. Click Next.
5. Source type:
   • Select 'Technical System'
   • If the source system is not on-premise please select 'External Service' if it is a cloud service or 'Unspecified Managed Object'.
6. Source: Select the source system from the drop-down list or enter the name for the unspecified managed object
7. Target Type:
   • Select 'Technical System'
   • If the target system is not on-premise please select 'External Service' if it is a cloud service or 'Unspecified Managed Object'.
8. Target: Select the target system from the drop-down list or enter the name for the unspecified managed object
9. The measuring point is selected automatically. Please note that for this template either the target or the source system must be an ABAP system! If both source and target are ABAP systems you can select the measuring point as necessary.
10. If more than one client are connected for the on premise system please select the correct client for the monitoring
11. Click Next.
12. Click Finish.

Maintain the Interface:

1. Select the interface channel you created
2. On the 'Interfaces' tab click the 'Add' button.
3. Provide the following information
   • Interface Name: The name of the interface
   • WS name / WS proxy: internal Web Service name. You can use the input help to select a web service and the method. In case the internal name is unknown, wildcards can be used for initial identification.
   • WS method: Web service method
   • WS user (on Server side): Web Service user
   • Logical Port (on Client side): Web Service logical port

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. 

Select Metrics:

1. On the tab 'Metrics' select the metrics you want to monitor. Please note that the selected metrics are collected for each WS destination entered above.

2. Enter Metric Parameters:

   • Metric: WS Channel available

     • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one

     • Script Name (mandatory): Enter the name of the UXMon script used to monitor the WS availability. To learn how to record the UXMon script please refer to the wiki page ICMon Availability Script.

   • Metric: Number of AppLog Errors (WS)
     • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one
     • Technical System (mandatory): The technical system in which the application log is written
     • Object name (mandatory): The object name for the application log entry
     • Sub-object name (mandatory): The sub-object for the application log entry
     • User name: Name of the user who caused the logged event
     • External ID (Expert field): External ID for the application log entry
     • Message ID (Expert field): Message ID for the application log entry
     • Message no. (Expert field): Message number for the application log entry
     • Message text (Expert field): Message text for the application log entry
     • Program (Expert field): Name of the program which caused the logged event
     • Transaction code (Expert field): Name of the transaction which caused the logged event

You can maintain attributes as described in the Interface and Connection Monitoring Setup on the tab 'Attributes'.

Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.

Maintain Thresholds and Schedule:

1. Select the Alert for the channel (the alert is the line with the red flash icon next to it)
   • On alert level you can maintain notification and incident message creation
2. Select the Metrics
   • You can adjust the thresholds on the tab Thresholds.
   • Do not change the data collector type or data collector name on the tab 'Data Collection' as the monitor will not work anymore if this is changed.
   • Only change the collection interval if you know what you do or if advised to do this by SAP.
3. Click 'Apply and Activate' → <Choose one option> to activate the monitoring 

Navigate to the step 'Define Scope'. You can create a new scenario or use an existing one. Make sure the sender and the receiver system are part of the Interface and Connection Monitoring scenario.

Create the Interface Channel:

1. Select the scenario and click 'Next'
2. In step 'Preparation' perform all relevant manual activities and run all automatic activities.
3. In step 'Configuration' click the 'Add' button.
   • Channel Name: Enter a meaning full name (max. 30 characters)
   • Type: Select 'Web Service'
   • Monitoring Template: Select 'Web Service (Introscope)'
   • Description: Enter a description for the channel
4. Click Next.
5. Source type:
   • Select 'Technical System'
6. Source: Select the source system from the drop-down list. The source system for this channel type can only be a JAVA system and that the measuring point is always the Java source system. The Java system has to be part of the Scope (Technical Scenario) for which the setup is running.
7. Target Type:
   • Select 'Technical System'
   • If the target system is not on-premise please select 'External Service' if it is a cloud service or 'Unspecified Managed Object'.
8. Target: Select the target system from the drop-down list or enter the name for the unspecified managed object
9. The measuring point is selected automatically.
10. Click Next.
11. Click Finish.

Maintain the Interface:

1. Select the interface channel you created
2. On the 'Interfaces' tab click the 'Add' button.
3. Provide the following information
   • Interface Name: The name of the interface
   • WS name: Web Service name.
   • WS method: 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.

Select Metrics:

1. On the tab 'Metrics' select the metrics you want to monitor. Please note that the selected metrics are collected for each WS destination entered above.

2. Enter Metric Parameters:

   • Metric: WS Channel available

     • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one

     • Script Name (mandatory): Enter the name of the UXMon script used to monitor the WS availability. To learn how to record the UXMon script please refer to the wiki page ICMon Availability Script.

You can maintain attributes as described in the Interface and Connection Monitoring Setup on the tab 'Attributes'.

Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.

Maintain Thresholds and Schedule:

1. Select the Alert for the channel (the alert is the line with the red flash icon next to it)
   • On alert level you can maintain notification and incident message creation
2. Select the Metrics
   • You can adjust the thresholds on the tab Thresholds.
   • Do not change the data collector type or data collector name on the tab 'Data Collection' as the monitor will not work anymore if this is changed.
   • Only change the collection interval if you know what you do or if advised to do this by SAP.
3. Click 'Apply and Activate' → <Choose one option> to activate the monitoring