Skip to end of metadata
Go to start of metadata

This topic lists the SAP environments supported by the ABAP Agent and SAP Analytics.

SAP Applications

The following table lists SAP applications with supported versions and functionalities:

SAP NetWeaver ABAP  7.0 EHP1 SP14 +
7.0 EHP2 SP13+
7.1 SP17+
7.1 EHP1 SP12+
7.3 EHP1SP09+
Supported OS, other OS through proxy Linux serverRFC, HTTP, Fiori, BSP, WebDynpro, SAPGUIBusiness transactionsABAP AgentABAP trace and DB trace not supported
SAP NetWeaver ABAP 

7.4 SP09+

7.5 - 7.53

Supported OS, other OS through proxy Linux serverRFC, HTTP, Fiori, BSP, WebDynpro, SAPGUI, WebGUI, 
ABAP and DB Trace, NetWeaver Gateway (OData)
Business transactionsABAP Agent 
SAP NetWeaver ABAP 7.0 SP25 - 7.53Supported OS, other OS through proxy Linux serverMonitoring: SAP application servers - CPU, memory, disk; DB benchmark, jobs, workload statistics, lock statistics, transport errors, application log errors, ABAP dumpsAnalyticsDatavard Insights 
SAP S/4 HANAAnySupported OSRFC, HTTP, Fiori

Business transactions

ABAP Agent 
SAP CRM7.0 BBPCRM 700 SP18 or newerNetWeaver ABAPBSP/CRM WebClient UI business transactions detectionBusiness transactionsABAP Agent  

7.4 from SP09

7.5 and newer

NetWeaver ABAPRFC, HTTP, Fiori, BSP, WebDynpro, WebGUI, 
ABAP and DB Trace, NetWeaver Gateway (OData), CIC0
Business transactionsABAP Agent for IS-UCIC0 business transaction splitting 
based on Front Office Processes

7.4 Single Stack (Java)

7.5 Single Stack (Java) and newer

NetWeaver JavaHTTP-to-RFC message transaction, synchronous & asynchronous communicationBusiness transactionsJava Agent + JCo extension 
SAP Portal 7.1, SAP JVM 5.1 (JDK 1.5) and aboveNetWeaver JavaHTTP, RFC (outgoing to ABAP)Business transactionsJava Agent + JCo extension

Web applications supported by Java Agent

RFC connections to ABAP (for example, ERP) supported by Java Agent extension

SAP NetWeaver ABAP systems on version 7.54 (S/4HANA 1909 and newer) are not yet fully supported by ABAP Agent and Datavard Insights.


SAP Supported Communication Technologies

The following table lists supported protocols used for communication between SAP systems and external applications:

NetWeaver ABAPRFCBidirectionalABAP AgentBusiness transactions & AnalyticsABAP to ABAP and ABAP outgoing calls require enhancement of ABAP code for each RFC Function Module. Monitoring is possible through Datavard Insights
NetWeaver ABAPHTTPBidirectionalABAP AgentBusiness transactions 
NetWeaver ABAPWebservicesBidirectionalABAP AgentBusiness transactions


NetWeaver ABAPODataBidirectionalABAP AgentBusiness transactions 
NetWeaver JavaRFCOutgoingABAP AgentBusiness transactionsLimited to calls from Java to ABAP. Java Agent JCo extension required
NetWeaver JavaHTTPBidirectionalABAP AgentBusiness transactionsSupported by Java Agent
Any JavaRFCOutgoingABAP AgentBusiness transactions

Limited to calls from Java to ABAP. Java Agent JCo extension required

SAP Supported UI Technologies

The following table lists supported user interface technologies used in SAP applications.

UI Technology


NetWeaver ABAPSAPGUIABAP AgentAnalytics & Business transactionsTransaction performance monitoring - workload statistics
NetWeaver ABAPFiori / SAPUI5ABAP AgentBusiness transactions & RUM


NetWeaver ABAPBSP ABAP AgentBusiness transactions 
NetWeaver ABAPCRM WebClient UIABAP AgentBusiness transactions 
NetWeaver ABAPWebDynproABAP AgentBusiness transactions & RUM 
NetWeaver ABAPWebGUI (SAPGUI for HTML)ABAP AgentBusiness transactions & RUMBusiness transactions detected as SAPGUI

SAP Supported Application Server Operating System

 The following table lists supported operating systems where local installation of HTTP SDK is possible. 


Windows Server 2008 R2 and higher (since agent version 4.4.1811)

64-bit (x86_64)

SAP supported Linux (Red Hat or SUSE) with glibc 2.11+

 Call Graphs are supported from glibc 2.22

64-bit (x86_64)

SAP system with multiple application servers running on mixed operating systems (i.e. Windows and Linux, or Linux and AIX, or Windows and AIX, etc.) are unsupported and local installation of HTTP SDK is not possible.

All application servers of one SAP system must either run on 64-bit Microsoft Windows or 64-bit Linux.

Also see Supported Environments, to know more about C/C++ Agent Supported Environments.

Selective application server instrumentation, i.e. exclusion of certain application servers from scope of ABAP agent, is currently not supported.

For SAP systems with unsupported application server operating systems, HTTP SDK must be installed on a separate 64-bit Linux machine. See Deploy SAP System on unsupported OS.

  • No labels