Free trial

SAP ABAP platform

Learn how to monitor your SAP ABAP platform using the SAP ABAP ActiveGate extension.

Prerequisites

  • SAP NetWeaver ABAP release 7.31 or newer
  • SAP Java Connector is present on the ActiveGate host
  • An endpoint to an SAP application server with production load can consume up to 0.5 CPU cores and 500MB RAM on the ActiveGate. Make sure to size the ActiveGate accordingly if you configure a lot of endpoints to poll from a single ActiveGate.
  • The ActiveGate requires remote access to the SAP application server (AS ABAP) over RFC protocol
  • If the plugin is going to create user sessions, the ActiveGate requires HTTP access to the configured Beacon URL
  • A user account that has permission to execute the following monitoring functions:

    • Authorization Object: S_RFC

      • Activity: 16
      • RFC Name: /SDF/GET_DUMP_LOG, GET_SYSTEM_TIME_REMOTE, SWNC_GET_WORKLOAD_SNAPSHOT, TH_SERVER_LIST, TH_USER_LIST
      • RFC Type: FUNC

    • Authorization Object: /SDF/E2E

      • Activity: 03

    • Authorization Object: S_RZL_ADM

      • Activity: 03

    • Authorization Object: S_TOOLS_EX

      • AUTH: S_TOOLS_EX_A

Interested in monitoring SAP ABAP platforms with DESK?

The SAP ABAP ActiveGate extension is available as a Preview. To enroll, contact a DESK ONE product specialist. Just click the chat button in the upper-right corner of the DESK menu bar.

Environment ActiveGate installation

ActiveGate plugin module installation

ActiveGate version 1.175+ has the plugin module installed by default.

SAP Java Connector configuration

  1. Download the SAP Java Connector to the ActiveGate.
  2. Place the sapjco3.jar file into the JCo folder, as configured below when adding a new monitoring endpoint (step 7 in extension installation)
  3. Depending on the OS running on the ActiveGate host, place sapjco3.dll (Windows) or libsapjco3.so (Linux) into the JCo directory
  4. Make sure that the user account executing the plugin is permitted to read from the JCo folder

Extension Installation

  1. Obtain the install file (custom.remote.python.sap.zip). Don't rename the file.

  2. Unzip custom.remote.python.sap.zip to the plugin_deployment directory of your ActiveGate host.

  3. If the resulting directory structure isn't .\plugin_deployment\custom.remote.python.sap\, make the necessary changes.

  4. Restart the DESK Remote Plugin Module service.

    • On Linux, run the following command with admin rights:
      systemctl restart remotepluginmodule.service
    • On Windows, open a Command Prompt (Run as Administrator) and run these two commands:
      sc stop "DESK Remote Plugin Module"
      sc start "DESK Remote Plugin Module"

  5. In DESK, select Settings, Add new technology monitoring, and then Add ActiveGate plugin.

  6. Select Upload plugin and upload custom.remote.python.sap.zip.

  7. Enter the following information to connect to your SAP host:

    • Endpoint name: Meaningful and descriptive name
    • User: The username for the account connecting to the SAP application server
    • Password: The password for the account
    • SAP server: The IP or host name of the SAP server
    • Instance id: The instance ID to connect to (this is a numeric value)
    • Client number: The client number to use for the connection
    • SAP JCo folder: The folder containing the sapjco3.jar and the native Java Connector file
    • Enable debug logging: Leave this option unselected unless requested by DESK support to investigate an issue
    • Create user sessions based on TCodes: Check this box to create user sessions and user actions based on the customer executed Tcodes. This functionality requires a custom application to be created, this is done under Deploy DESK in the menu
    • The Beacon URL of the custom application: If you want to create user sessions, fill in the Beacon URL you are prompted with after creating the custom application
    • The Application ID of the custom application: If you want to create user sessions, fill in the Application ID you are prompted with after creating the custom application
    • Events: Enter the thresholds to generate performance related events:
      • Event - the average DIALOG response time is higher than (ms)
      • Event - the average RFC response time is higher than (ms)
      • Event - another task type has an average response time higher than (ms)
      • Event - average CPU time per task type is higher than (%) (also requires the response time event to be triggered)
      • Event - average CPU time per task type is lower than (%) (also requires the response time event to be triggered)
      • Event - average wait time per task type is higher than (%) (also requires the response time event to be triggered)
      • Event - average load time per task type is higher than (%) (also requires the response time event to be triggered)
      • Event - average database time per task type is higher than (%) (also requires the response time event to be triggered)
      • Event - average database time per task type is lower than (%) (also requires the response time event to be triggered)
      • Event - the average database call time is higher than (ms)

Extension Upgrades

  1. Disable the extension in the DESK UI
  2. Wait 5 minutes
  3. Replace the extension files on the ActiveGate host
  4. Enable the extension in the DESK UI

Troubleshoot ActiveGate plugins

Metrics

Host

  • Availability

Tasks per SAP instance (split by the tasks dialog, update, update2, spool, enqueue, RFC, and other)

  • CPU time/Response time ratio
  • Database time/Response time ratio
  • Wait time/Response time ratio
  • Load time/Response time ratio
  • Average response time
  • CPU time
  • Database time
  • Database calls
  • Roll in time
  • Roll wait time
  • Load + generation time
  • Response time

Dialog

  • Dialog steps
  • Dialog response time
  • Dialog network time
  • GUI user count

Additional Notes

  • ABAP runtime errors are created as events in DESK
  • Infrastructure and dependency monitoring requires OneAgent installation on the AS ABAP servers and other servers in the SAP landscape. Typically, this includes database servers and RFC client servers that communicate with SAP application servers.