On this page:

Your Rating:
42 rates
This topic explains how to install the tools for SAP applications running on the NetWeaver ABAP platform to support monitoring with AppDynamics. It includes:

  • AppDynamics C++ SDK and related components
  • ABAP agent
  • SAP Analytics components

Install the HTTP SDK

Install HTTP SDK directly to SAP application servers running on 64-bit Linux or Microsoft Windows systems. See Installing HTTP SDK Automatically
To install the Linux version of HTTP SDK manually:

  1. Extract the ABAP agent zip file: APPD-SAP-<version>.zip
  2. Copy the appdhttpsdk sub-directory of the SapAgent-<version> directory into /opt/appdynamics/ on every 64-bit Linux-based SAP application server or the Gateway system server.
  3. Provide full access rights (read/write/execute) to the /opt/appdynamics/appdhttpsdk directory for configuration and control of the HTTP SDK proxy by:
    • SAP instance user (<SID>ADM) on SAP application servers
    • Any user that will start the SDK manager on the Gateway system

SSL Communication with On-premises Controllers

HTTP SDK is delivered with default certificate used for SSL communication with SaaS controllers only. You need to enable SSL communication with on-premises controller.

  1. Go to your controller using web browser.
  2. Download SSL certificate in .crt format and save as ca-bundle.crt.
  3. Go to <APPD_INSTALLATION_DIRECTORY>/appdhttpsdk directory. 
    /opt/appdynamics/appdhttpsdk or C:/AppDynamics/appdhttpsdk

    The path is different If you are using custom installation directory.

  4. Replace the existing ca-bundle.crt in the installation directory with the SSL certificate you downloaded in Step 2.
  5. Repeat this procedure for all your application servers.

SDK Manager

If you are using a Linux Gateway system, start the SDK manager on this system to enable remote control and lifecycle management of your HTTP SDK instances. SDK manager is installed along with the HTTP SDK proxy.

To start the SDK manager application, run the following command:


Optional parameters:

  • -p <port number>Use this parameter to override the default SDK manager port, 7999.

  • -j <path to java> used to set JAVA_HOME variable for SDK manager 

  • -cSDK manager will not restart previously running HTTP SDK instances when this parameter is used

It is recommended that you add the SDK Manager startup script to your OS-level startup scripts. It enables the HTTP SDK auto-restart functionality for the Linux Gateway system.

Open the SDK Manager port (default 7999) for all the SAP application server hosts that connect to the SDK Manager instance. This port enables control of HTTP SDK instance and access to logs. An additional port must be open per each SAP application server to enable communication between ABAP Agent and HTTP SDK instance. If you are using strict firewall rules, open all relevant ports between relevant hosts.


Ensure that the SDK Manager is executed by one user or user group. HTTP SDK proxy configuration and log file authorizations are restricted to the user and user group that started the SDK Manager.

Set Sufficient Access Rights

For the SAP application server, SAP instance user (<SID>ADM) must have full access rights that include read, write, and execute on /opt/appdynamics/appdhttpsdk. This means that the directories, all the sub-directories, and the contents must meet one of the following:

  • owned by the <SID>ADM user
  • assigned to the SAPSYS user group
  • assigned to a user group where the <SID>ADM user is assigned
  • all users have full access (read, write, and execute) rights

Same rules apply to the Linux Gateway system, except that substitute <SID>ADM with the user and SAPSYS with the user group that executes SDK Manager.

Install the AppDynamics Machine Agent

The Machine Agent collects the OS performance metrics, such as CPU, RAM, disk, and network, for the application servers. SAP Analytics uses the Machine Agent to report SAP-specific metrics, logs, and events. Install the Machine Agent on all SAP application servers and enable the HTTP listener.

See Install the Standalone Machine Agent and Configure the Standalone Machine Agent

Enable Machine Agent HTTP Listener

The Machine Agent HTTP listener is used to pass metrics and events from SAP system. Do the following when you install the standalone Machine Agent from the RPM package:

  1. To enable the HTTP listener, edit the /opt/appdynamics/machine-agent/etc/sysconfig/appdynamics-machine-agent configuration file and add the following line: 
    JAVA_OPTS="-Dmetric.http.listener=true -Dmetric.http.listener.port=8293 -Dmetric.http.listener.host="
  2. Save the changes. 
  3. Restart the Machine Agent service.

For a non-RPM installation, enable the HTTP listener of the machine. See Standalone Machine Agent HTTP Listener

Install ABAP Agent

You install the ABAP agent on the SAP system by importing standard SAP transport requests. The installation requires several transport requests to be imported in the correct order due to dependencies.

Before the installation, check your SAP NetWeaver release. There are two ABAP agent versions:

  • ABAP agent for NetWeaver earlier than version 7.4.0 
  • ABAP agent for NetWeaver version 7.4.0 or later.


Import SAP requests into production systems when the traffic and load are minimal. It is recommended to import SAP requests outside of business hours or during weekends. ABAP Agent takes advantage of several enhancements placed in standard objects that trigger recompilation of these objects during import. This affects HTTP client, HTTP server, SOAP handler, BSP controllers, UI5 apps, SAP Gateway/Backend, ST05 trace, and Application log.

Install SAP NetWeaver Earlier Than Version 7.4

To install the ABAP agent without import errors with RC=8, import the following transport requests in the sequence: 

  1. Datavard Reuse Library
  2. Datavard Insights (SAP Analytics)
  3. AppDynamics ABAP Agent Core

Install SAP NetWeaver Gateway Earlier Than Version 7.4

To install the ABAP agent on the NetWeaver Gateway system, import the following transport requests on both front end and back end systems:

  1. All transport requests for ABAP Agent on SAP NetWeaver
  2. AppDynamics BEP instrumentation

Installation on SAP NetWeaver Version 7.4 or Later

To install the ABAP agent on SAP NetWeaver 7.4 and higher, import the following transport requests:

  1. Datavard Reuse Library
  2. Datavard Insights (SAP Analytics)
  3. AppDynamics ABAP agent 7.4

Installation on SAP NetWeaver Gateway Version 7.4 or Later

SAP NetWeaver 7.4 includes NW Gateway, so the instrumentation is part of ABAP Agent version 7.4. Use the same transport requests for all SAP NetWeaver version 7.4 or later systems.

If you have a separate NW Gateway system version 7.4 or later, the installation steps are the same as all ABAP version 7.4 systems. See Instrument NetWeaver Gateway

SAP Authorizations

Authorize SAP Monitoring

To authorize a user to start SAP transaction monitoring, add the user to the /DVD/MON_ADMIN role. The role is part of the transport.

AppDynamics Authorizations

To authorize a user to administer and use AppDynamics in SAP, add the user to the /DVD/APPD_ADMIN role. Role /DVD/APPD_USER exists as a subset of the Admin role and allows execution of certain components (start, stop, collect traces, call AppDynamics RFC Function Modules from external systems, etc.). The User role is meant for users to be monitored and technical users utilized during RFC calls. The roles are part of the transport.


  • No labels