お問い合わせ

HTTP Channel

Technical Prerequisites

The following technical prerequisites have to be met in order to use the HTTP monitoring:

  • Managed system is ABAP based system with basis release ≥ 7.0
  • Managed system as at least ST-PI  2008_1 SP06 or higher

The channel monitoring data is based on information from ICM http log. Please make sure the relevant parameter (icm/HTTP/logging_X) in the ABAP system is set during the managed system setup of the system to make sure the data can be collected correctly. The collector requires the logformat SAPSMD. If there is already another log format for example SAPSMD2 or CLFMOD you need to add another one. Just add in the default profile a new parameter:

icm/HTTP/logging_* = PREFIX=/, LOGFORMAT=SAPSMD, LOGFILE=icmhttp.log, MAXSIZEKB=10240, SWITCHTF=day, FILEWRAP=on

where * is the next consecutive number. Example: if icm/HTTP/logging_0 is already set, take parameter icm/HTTP/logging_1.

To use the HTTP (Client) template is only available for the content of SAP Solution Manager 7.1 SP 14 or higher.

Available Monitoring Content

Monitoring Template: HTTP Server ABAP

This template allows to monitor incoming HTTP calls into the ABAP stack.

 

Note: Metrics for Interface Channels of type HTTP are always retrieved from the target system.

Metric Name Description MAI Category Since SP

HTTP Channel available

Availability measured by Script

Availability

 7.1 SP12

HTTP Destination available

HTTP Destination available measured by a ping to full specified destination.

Availability

 7.1 SP12

HTTP Destination available (with logon)

This metric measures the technical availability of an http RFC destination, including authentication, by performing an http get request using authentication information stored at source system side. It returns a green rating if http return code is smaller than 400 and a red rating if it is equal to or larger than 400.

Availability

 7.1 SP12

Number of HTTP Errors

HTTP responses with Status code ≥ 500

Exceptions

 7.1 SP12

Number of ABAP Dumps

Dumps containing the path

Exceptions

 7.1 SP12

HTTP Latency

Latency time of a ping to HTTP Destination

Performance

 7.1 SP12

Average HTTP Response Time

Average HTTP Response Time in ms

Performance

 7.1 SP12

Average HTTP Response Time per Instance

Average HTTP Response Time per instance in ms

Performance

 7.1 SP12

Number of HTTP executions

Number of executions of an application including path

Performance

 7.1 SP12

Number of HTTP executions per Instance

Number of executions per instance of an application including path

Performance

 7.1 SP12

Monitoring Template: HTTP Client (from ABAP)

This template allows you to monitor outgoing HTTP calls via RFC destination of type G and H from the ABAP stack.

Metric NameDescriptionMAI Category
HTTP PingThis metric measures the technical availability of an http RFC destination by performing an http get request.Availability
HTTP LatencyThis metric measures the latency of an http RFC destination in milliseconds.Performance

HTTP Logon

This metric measures the technical availability of an HTTP RFC destination by performing an HTTP GET request including a logon (since 7.2 SP11, MAI content delivery version 44).

Availability

Monitoring Template: HTTP Client (from Introscope)

This template allows you to monitor outgoing HTTP calls from the Java Stack.

This template can be used for Java stacks that use REST (Representational state transfer) web services for communication. If a Java system uses this communication you can find a sub-tree for the REST services in APM Introscope Enterprise Manager under coll_host|SAP Netweaver|coll_server_node|Backends|REST|Client.

If you don't find a REST sub-tree under Backends your Java system is not using REST and you cannot use this template (the metrics will stay grey)

Metric NameDescriptionMAI Category
Average REST Response Time (Introscope)Average response time of configured outgoing REST executions in ms.Availability
Number of REST executionsNumber of configured outgoing REST executions. Performance

Configuration

The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP). 

To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.

Note: If you didn't perform the infrastructure configuration yet, please follow the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2.

Monitoring Template: HTTP Server ABAP

Navigate to the Define Scope step. 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 the Preparation step, perform all relevant manual activities and run all automatic activities.
  3. In the Configuration step, click the Add button.
    • Channel Name: Enter a meaning full name (max. 30 characters)
    • Type: Select HTTP
    • Monitoring Template: Select HTTP Server ABAP
    • Description: Enter a description for the channel
  4. Click Next.
  5. Source type:
    • Select Technical System.
    • If the source system is not on-premise, 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
  8. Target: Select the target system from the drop-down list. Specification of Unspecific Managed Object or anything non-ABAP is only possible for the source system. The target system has to be a technical system of type ABAP and has to be part of the Scope (Technical Scenario) for which the setup is running.
  9. The measuring point is selected automatically.
  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.
    • HTTP Method: The method to monitor, e.g. GET, HEAD, POST etc.
    • URL Path: The path of the URL. You can use transaction SICF to find the exact URL path for the HTTP content you are trying to monitor.

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 Metrics tab, select the metrics you want to monitor. Note that the selected metrics are collected for each HTTP destination entered above.

  2. Enter Metric Parameters:

    • Metric: HTTP 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 HTTP availability. To learn how to record the UXMon script please refer to the page ICMon Availability Script.

    • HTTP Destination available
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one.
      • Destination: The name of the RFC destination in the source systems SM59.
    • HTTP Destination available (with logon)
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one.
      • Destination: The name of the RFC destination in the source systems SM59.
    • HTTP latency 
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one.
      • Destination: The name of the RFC destination in the source systems SM59.

You can maintain attributes as described in the Interface and Connection Monitoring Setup with SAP Solution Manager 7.2 on the Attributes tab.

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 Activation step.

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 Data Collection tab 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

Monitoring Template: HTTP Client (from ABAP)

Navigate to the Define Scope step. 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 the Preparation step, perform all relevant manual activities and run all automatic activities.
  3. In the Configuration step, click the Add button.
    • Channel Name: Enter a meaning full name (max. 30 characters)
    • Type: Select HTTP
    • Monitoring Template: Select HTTP Client (From ABAP)
    • 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. Specification of Unspecific Managed Object or anything non-ABAP is only possible for the target system. The source system has to be a technical system of type ABAP and 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, 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. If more than one client are connected for the on-premise system, select the correct client for the monitoring
  11. Click Next.
  12. Click Finish.

Maintain the Interface:

  1. The interface channel type does not have any configurable parameters on interface level. Move directly to the metric configuration.

Select Metrics:

  1. On the Metrics tab, select the metrics you want to monitor. Note that the selected metrics are collected for each HTTP destination entered above.

  2. Enter Metric Parameters:

    • HTTP Ping
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one.
      • Destination: The name of the RFC destination in the source systems SM59.
    • HTTP Latency 
      • Parameter set name: You can enter a name for the parameter set to distinguish it if you have more than one.
      • Destination: The name of the RFC destination in the source systems SM59.

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

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 Activation step.

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. The metric "HTTP Ping" is already rated and you should not change the threshold. It returns a green rating if http return code is smaller than 500 and a red rating if it is equal to or larger than 500.
    • Do not change the data collector type or data collector name on the Data Collection tab 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.

Monitoring Template: HTTP Client (from Introscope)

Navigate to the Define Scope step. 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 the Preparation step, perform all relevant manual activities and run all automatic activities.
  3. In the Configuration step, click the Add button.
    • Channel Name: Enter a meaning full name (max. 30 characters)
    • Type: Select HTTP
    • Monitoring Template: Select HTTP Client (From 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 an Apache Tomcat (ATC) and is used as measuring point. The Apache Tomcat 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, 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. 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
    • Name: The name of the REST service you want to monitor
    • Method: The method of the REST service you want to monitor

Select Metrics:

  1. On the Metrics tab, select the metrics you want to monitor. Note that the selected metrics are collected for each HTTP destination entered above.

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

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 Activation step.

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 Thresholds tab.
    • Do not change the data collector type or data collector name on the Data Collection tab 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