SAP Supported Environments
This topic lists the SAP environments that are supported by the ABAP Agent, HTTP SDK, and SNP CrystalBridge® Monitoring.
SAP Applications
The following table lists the SAP applications with the supported versions and other details:
| Application | Version | Platform | Functionality | Type | Package | Comment |
|---|---|---|---|---|---|---|
| SAP NetWeaver ABAP |
|
Supported OS other OS through proxy Linux server. | RFC, HTTP, Fiori, BSP, WebDynpro, SAPGUI | Business transactions | ABAP Agent CORE |
ABAP trace and DB trace are not supported SAP systems with version 7.4 SP06 - SP08 can use this package. |
| SAP NetWeaver ABAP |
|
Supported OS other OS through proxy Linux server. | NetWeaver Gateway (OData) | Business transactions | ABAP Agent BEP |
Intended for older NetWeaver Gateway systems without SAP_GWFND component. Minimum component requirements:
|
| SAP NetWeaver ABAP |
|
Supported OS other OS through proxy Linux server. | RFC, HTTP, Fiori, BSP, WebDynpro, SAPGUI, WebGUI, ABAP and DB Trace, NetWeaver Gateway (OData), RUM | Business transactions | ABAP Agent 740 | |
| SAP NetWeaver ABAP | 7.0 EHP1 SP15 - 7.58 (up to S/4 HANA 2023 FPS03 supported by ABAP Agent 24.11.0 and newer) |
Supported OS other OS through proxy Linux server. | Monitoring: SAP application servers - CPU, memory, disk; DB benchmark, jobs, workload statistics, lock statistics, transport errors, application log errors, ABAP dumps. | Analytics | SNP CrystalBridge® Monitoring | |
| SAP S/4 HANA | up to S/4 HANA 2023 FPS03 supported by ABAP Agent 24.11.0 and newer |
Supported OS other OS through proxy Linux server. | RFC, HTTP, Fiori, BSP, WebDynpro, SAPGUI, WebGUI, ABAP and DB Trace, NetWeaver Gateway (OData), RUM | Business transactions | ABAP Agent 740 | |
| SAP CRM | 7.0 BBPCRM 700 SP18 or newer | NetWeaver ABAP | BSP/CRM WebClient UI business transactions detection | Business transactions | ABAP Agent | |
| SAP IS-U |
| NetWeaver ABAP | RFC, HTTP, Fiori, BSP, WebDynpro, WebGUI, ABAP and DB Trace, NetWeaver Gateway (OData), CIC0 | Business transactions | ABAP Agent for IS-U | CIC0 business transaction splitting based on Front Office Processes. |
| SAP PI/PO |
| NetWeaver Java | See SAP PI/PO AS Java | Business transactions and analytics | Java Agent + JCo extension and SNP CrystalBridge® Monitoring. |
Because of the changes in SAP NetWeaver Java core logic, some features are no longer available as of release 753 patch level 925. This limitation is resolved in version 22.8.0. |
| SAP Portal | 7.1, SAP JVM 5.1 (JDK 1.5) and above | NetWeaver Java | HTTP, RFC | Business transactions | Java Agent + JCo extension |
Web applications supported by Java Agent RFC connections to ABAP supported by JCo plugin For ABAP to Java calls, ABAP code modifications are needed, see Instrument custom ABAP code. |
SAP Supported Communication Technologies
The following table lists supported protocols used for the communication between SAP systems and external applications:
| Platform | Protocol | Direction | Package | Type | Comment |
|---|---|---|---|---|---|
| NetWeaver ABAP | RFC | Bidirectional | ABAP Agent | Business transactions & Analytics |
ABAP to ABAP, ABAP to Java, and ABAP outgoing calls require enhancement of ABAP code for each RFC Function Module. Monitoring is possible through SNP CrystalBridge® Monitoring. |
| NetWeaver ABAP | HTTP | Bidirectional | ABAP Agent | Business transactions | |
| NetWeaver ABAP | Webservices | Bidirectional | ABAP Agent | Business transactions | |
| NetWeaver ABAP | OData | Bidirectional | ABAP Agent | Business transactions | |
| NetWeaver Java | RFC | Bidirectional | ABAP Agent | Business transactions | Java Agent JCo extension is required. For ABAP to Java RFC calls, ABAP code modifications are needed, see Instrument custom ABAP code |
| NetWeaver Java | HTTP | Bidirectional | ABAP Agent | Business transactions | Supported by Java Agent |
| Any Java Application | RFC | Bidirectional | ABAP Agent | Business transactions | Java Agent JCo extension required. For ABAP to Java RFC calls, ABAP code modifications are needed, see Instrument custom ABAP code |
SAP Supported UI Technologies
The following table lists supported user interface technologies used in SAP applications:
| Platform | UI Technology | Package | Type | Comment |
|---|---|---|---|---|
| NetWeaver ABAP | SAPGUI | ABAP Agent | Analytics & Business transactions | Transaction performance monitoring - workload statistics |
| NetWeaver ABAP | Fiori / SAPUI5 | ABAP Agent | Business transactions & RUM | |
| NetWeaver ABAP | BSP | ABAP Agent | Business transactions & RUM | RUM beta |
| NetWeaver ABAP | CRM WebClient UI | ABAP Agent | Business transactions & RUM | RUM beta |
| NetWeaver ABAP | WebDynpro | ABAP Agent | Business transactions & RUM | |
| NetWeaver ABAP | WebGUI (SAPGUI for HTML) | ABAP Agent | Business transactions & RUM |
Business transactions are detected as SAPGUI. Currently, Browser RUM correlation is not supported. After the 23.5.0 version, EUM / RUM is supported on S/4 HANA 2020 and newer versions. |
SAP Supported Application Server Operating System
The following table lists supported operating systems where local installation of HTTP SDK is possible.
| System | Architecture |
|---|---|
| SAP supported Linux (Red Hat or SUSE) with GLIBC 2.17 or newer | 64-bit (x86_64) |
|
SAP supported Linux (Red Hat or SUSE) with GLIBC 2.11 - 2.16 Systems that fall under this category need to use the Legacy HTTP SDK build. Call Graphs are not supported due to GLIBC version limitations. Warning: Legacy component legal statement
This Legacy HTTP SDK build ("Legacy Build") is intended to support installations on Linux systems using GLIBC versions before 2.17. You acknowledge that the Legacy Build requires the inclusion of third-party libraries that are no longer supported. By using the Legacy Build, you understand and accept that such third-party libraries do not receive current security patches and may contain known vulnerabilities. If you do not agree to these terms, you must not access this Legacy Build. | 64-bit (x86_64) |
| Microsoft Windows with Visual Studio C++ Redistributable 2019 or newer | 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 run either on a 64-bit Microsoft Windows or on a 64-bit Linux.
Selective application server instrumentation, i.e. exclusion of certain application servers from the scope of ABAP agent, is currently unsupported.
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 .