Skip to end of metadata
Go to start of metadata

This document describes how to install and configure SAP monitoring using AppDynamics.


SAP monitoring components are:
  • SAP ABAP Agent: Responsible for business transaction monitoring (communication between SAP and external systems, like the AppDynamics Controller).
  • Datavard Insights: Responsible for collecting SAP-specific metrics, logs, and events.

Supported AppDynamics Controllers

The SAP ABAP Agent supports AppDynamics Version 4.4 and beyond. 

License Requirements

The purchase of AppDynamics for SAP ABAP Agent covers the following licenses, but these must be generated and installed on the corresponding components.

AppDynamics Controller
  • One AppDynamics C/C++ SDK license for each SAP application server
  • One AppDynamics Machine Agent license for each SAP application server
Within SAPGUI configuration for licensing
  • One AppDynamics ABAP agent license for each SAP system

SAP ABAP Agent Architecture

The ABAP Agent uses the AppDynamics C++ SDK wrapped by the AppDynamics HTTP SDK to report business transaction performance metrics and snapshots. The following diagram describes the communication between ABAP Agent and AppDynamics Controller: 

Install the ABAP Agent and HTTP SDK


The HTTP SDK can be installed on the SAP application servers that run on supported operating systemIf the SAP application server runs on unsupported OS, for example, AIX, install HTTP SDK on a separate machine.


Purpose of installationComponentsComponent Description
Instrumenting the SAP systems


Connects the ABAP Agent and the AppDynamics Controller.
The ABAP Agent communicates with the HTTP SDK through HTTP protocol. HTTP Requests are mapped to functions from the AppDynamics C++ SDK library. The AppDynamics C++ SDK is included into the HTTP SDK and is used for communicating with the AppDynamics Controller, reporting business transaction metrics, dashboards, and so on.
ABAP Agent

Intercepts HTTP and certain RFC calls.

Detects business transactions, exit calls, and errors.

Reconstructs SAP GUI logs into business transactions.

Reports metrics to the controller.

Collecting SAP system performance metrics and events

AppDynamics Standalone Machine Agent

Reports application events to the controller.

Datavard Insights

Collects the SAP-specific metrics and events.


Before you begin, verify the support for your application environment at SAP Supported Environments. 

Deploy SAP system using one of the following OS options:

  1. SAP application server running on supported OS
  2. SAP application server running on unsupported OS


Deploy SAP System on Supported OS

Install the HTTP SDK locally on every server if all the SAP application servers are running on supported OS. You can automate the local installation, see Installing HTTP SDK Automatically. The ABAP Agent connects to the HTTP SDK using a local HTTP connection.

Deploy SAP System on Unsupported OS

If the SAP application servers are running on unsupported systems, install the HTTP SDK on a separate 64-bit Linux machine (Gateway system) that is used as a proxy for all SAP application servers. See Installing HTTP SDK Manually.

The ABAP Agents communicate through HTTP connection with the HTTP SDK instances on the Linux system. For every SAP application server, a separate HTTP SDK instance (process) starts on the Gateway system.

Following are the Gateway system requirements:

  • 64-bit Linux as Operating System
  • Physically close to the SAP systems to prevent latency issues
  • 512 MB RAM for each SAP system
  • Minimal disk requirements (logs)
  • Java 1.8 or newer (for SDK Manager)
  • IPv4 protocol is required (for SDK Manager)
  • Server host name must be maintained
  • One open port for SDK manager (default port is 7999) between this Gateway system and all SAP application server hosts
  • One open port for each HTTP SDK instance between this Gateway system and SAP application server that owns this HTTP SDK instance

The AppDynamics Machine Agent supports most operating systems. It must be installed on each SAP application server. See Standalone Machine Agent Requirements and Supported Environments.

Each HTTP SDK instance uses a unique port for HTTP communication with the ABAP Agent. The SDK Manager application governs all HTTP SDK instances on the Gateway system. This application allows remote control from the ABAP Agent GUI. See SDK Manager.

  • No labels