SAP ABAP platform

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

Prerequisites

  • SAP NetWeaver ABAP release 7.31+
  • ActiveGate version 1.167+
  • SAP Java Connector 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 several endpoints which poll from a single ActiveGate.
  • The ActiveGate requires remote access to the SAP application server (AS ABAP) over RFC protocol
  • If the endpoint is configured to poll all clustered instances, the remote access from the ActiveGate needs to be to all SAP AS instances
  • 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

Environment ActiveGate installation

ActiveGate plugin module installation

ActiveGate version 1.175+ has the ActiveGate 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 Dynatrace 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 "Dynatrace Remote Plugin Module"
      sc start "Dynatrace Remote Plugin Module"
  5. In Dynatrace, 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
    • Username: 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
    • Poll all clustered SAP instances: Instead of creating one endpoint per SAP instance, this option polls all clustered SAP instances at once
    • Path to a JCo destination file: If a specific destination file is required to connect to the SAP server, enter the path here. This will override all of the above settings
    • SAP JCo folder: The folder containing the sapjco3.jar and the native Java Connector file
    • Task types to report on: Comma-separated task types to report on, the rest will be combined. The possible task types are: NONE, DIALOG, UPDATE, SPOOL, BCKGRD, ENQUEUE, BUF.SYN, AUTOABA, UPDATE2, NATIVE_RFC, PLUGIN, AUTOTH, RPCTH, RFCVMC, DDLOGCLEANUP, DEL.THCALL, AUTOJAVA, LICENCESRV, AUTOCCMS, MSADM, SYS_STARTUP, BGRFCSDL, BGRFC, APC, OTHERS, DINOGUI, B.INPUT, HTTP, HTTPS, NNTP, SMTP, FTP, LCOM, HTTP/JSP, HTTPS/JSP, AUTO_RFC, WS-RFC, WS-HTTP, ESI, ALE, RFC and CPIC
    • Enable debug logging: Leave this option unselected unless requested by Dynatrace support to investigate an issue
    • Report on application server metrics: Create a custom device and send application server metrics
    • 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 Dynatrace in the menu
    • The Beacon URL of the custom application: 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: To create user sessions, fill in the Application ID you are prompted with after creating the custom application
    • Proxy: If a proxy is required for communicating with the Beacon URL, enter it here
    • Capture usernames as part of the user sessions: Check to capture usernames
    • Display best practice upper boundary: Adds an upper boundary line to the performance metric charts on the customer device

Windows ActiveGate-specific extension upgrades

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

Troubleshoot ActiveGate plugins

Metrics

Application server instance

  • Availability
  • Runtime errors
  • CPU time/Response time ratio
  • Database time/Response time ratio
  • Wait time/Response time ratio
  • Load time/Response time ratio

Tasks (split by task)

  • Response time
  • Dialog steps
  • CPU time
  • Database time
  • Database calls
  • Roll in time
  • Roll wait time
  • Load + generation time
  • User count

Dialog

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

Additional notes

  • ABAP runtime errors are created as events in Dynatrace and, if possible, mapped to the responsible user action
  • 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.