Enhancements

General

Handling of Enhancements

ABAP Agent transport requests no longer contain any enhancements of standard SAP components ("enhancements"). All enhancements are now moved to separate transport requests that need to be imported after ABAP Agent installation transport requests. A new transport request for pre-upgrade cleanup was also added and is intended for removal of all enhancements.

This change affects the following processes:

  • ABAP Agent Installation
    • Transport requests with relevant enhancements must be imported after all relevant ABAP Agent component transport requests are imported.
  • ABAP Agent Upgrade
    • Pre-upgrade cleanup transport request must be imported before all other transport requests.
    • Transport requests with relevant enhancements must be imported after all relevant ABAP Agent component transport requests are imported.
  • ABAP Agent Uninstallation
    • Pre-upgrade cleanup transport request can be imported before all other transport requests.
  • Enhancement deactivation
    • Enhancement uninstallation transport request is reproposed as pre-upgrade cleanup transport request, and is now placed in a dedicated sub-folder in the release zip file.
  • Enhancement reactivation
    • Transport requests for enhancement reinstallation are repurposed as enhancement installation transport requests, and are now placed in a dedicated sub-folder in the release zip file.

Please refer to individual readme.txt files for more details.

Agent Dependencies

SNP Reuse Library transport request is excluded from the list of dependencies and it is no longer part of the release bundle. Uninstallation transport for SNP CrystalBridge Monitoring and Reuse Library is split into two separate transports. Uninstall transport request for SNP Reuse Library can be applied when the SAP system does not contain any other SNP software that is dependent on SNP Reuse Library.

Components With Different Versions

There are AppDynamics components included in this release where version does not match with ABAP Agent components version. The following components report a version that was used in this release:

  • C++ SDK legacy - version 22.12.0-576
  • C++ SDK latest - version 24.9.1-1000

HTTP SDK Compatibility Version

Due to C++ SDK changes in oldest supported GLIBC, ABAP Agent ships with two types of HTTP SDK:

  • HTTP SDK latest - includes newest C++ SDK version and contains all features. Requires GLIBC version 2.17 or newer (on Linux) or Microsoft Visual C++ Redistributable 2019 or newer (on Windows).
  • HTTP SDK legacy - includes a special C++ SDK version (22.12.0-576) that is compatible with older GLIBC versions. Does not support call graphs, but contains features added up to the specified C++ SDK version.

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.

If the C++ libraries on supported SAP application servers cannot be upgraded, HTTP SDK can be installed on a remote Linux gateway system with sufficient GLIBC version as a workaround. See Installing HTTP SDK Manually.

Legacy component deprecation

As of release 24.11.0, Legacy Build is no longer included in the remote HTTP SDK installation scenario. It is still available for local HTTP SDK installation, but this option will be removed in near future. If your SAP system is still running on unsupported GLIBC version, it is recommended to switch from legacy local HTTP SDK scenario to latest remote HTTP SDK scenario.

Please refer to individual readme.txt files for more details.

ABAP Agent

SAP-527 (ASM-1644, ASM-1681, ASM-1682): Handling of Enhancements

ABAP Agent transport requests no longer contain any enhancements of standard SAP components ("enhancements"). All enhancements are now moved to separate transport requests that need to be imported after ABAP Agent installation transport requests. A new transport request for pre-upgrade cleanup was also added and is intended for removal of all enhancements.

Please refer to individual readme.txt files for more details.

Monitoring

SAP-348 (ASM-1016, ASM-1510, ASM-1645): Prevent KPI Value Overflows

Enqueue monitoring collector was completely overhauled. Some old KPIs are now obsolete and new KPIs and metrics are added. The change is intended to reduce the risk of KPI value overflow. This change is also reflected in the corresponding dashboard that needs to be reuploaded after upgrade.

See Mapping Between KPIs and Metrics and Lock Statistics.

SAP-520 (ASM-1635): Filter Background Jobs by Report Name

Background job monitoring collectors now allow to define report name on top of background job name in the collector input table. This enables more granular filtering of different background jobs and is intended for scenarios where job name changes between two job runs.

See Performance Collector Settings

SAP-525 (ASM-1270, ASM-1271): Extended HANA Thread Monitoring

All existing HANA thread monitoring functionality was merged into a single collector and the logic was extended to cover several new scenarios. One of the new scenarios is monitoring and reporting the HANA queries that are currently running and consuming the most CPU or memory resources. The collector now collects additional metrics and detail tables. See Collector for HANA Threads Monitoring for more details.

A new OOTB HANA threads dashboard is now available and contains HANA threads data available out of the box. Not all new content is replicated into Splunk AppDynamics Collector and Event Service by default. Additional detail tables can configured for replication to harmonized analytics schema sap_hana_data using t-code /DVD/APPD_CC. See Monitoring Connector Mapping.

JCo Extension

SAP-529 (ASM-1652): Better Handing of Multithreading

The JCo extension was optimized to better handle multi-threaded operations in combination with asynchronous RFC (aRFC) calls. These changes are intended to proactively prevent resource depletion in highly parallelized and multi-threaded environments.

 As of this release, aRFC processing is turned off by default, but it can be activated when needed. Always increase the default JCo connection pool size before activating aRFC processing. See Enable Business Transaction Correlation with SAP JCo and Troubleshoot Java Agent JCo Plugin.

Resolved Issues and Improvements

ABAP Agent Improvements

  • ASM-1651: Improved performance of event service connection check.

ABAP Agent Fixes

  • ASM-1603: Call graph data assigned to correct SAPGUI session step business transaction.
  • ASM-1641 (SAP-517): Proactive security scan and resolving high priority findings.
  • ASM-1657: Resolve potential dead-lock issue in SAPGUI EUM user info buffer logic. 
  • ASM-1669: Addressed CONTRLRDEV-4600 changes by adding new mandatory HTTP request header to OAuth API call.

Monitoring Improvements

  • ASM-1550: Additional improvements in Monitoring cockpit charts handling under Chromium browser.
  • ASM-1620: New KPI and detail table for HANA table partitions maximum rows added to HANA table sizes collector.
  • ASM-1621: Extended error logging and reporting when reading data from HANA view M_HOST_INFORMATION.
  • ASM-1624: Removed obsolete monitoring area HDB_HA as it is no longer used.
  • ASM-1626: Added authorization S_SPO_ACT to relevant authorization roles so log download logic can also access relevant job spool data.
  • ASM-1627: Added authorization S_ADM_RFC also to optimized authorization role /DVD/MON_BTC_USER.
  • ASM-1632: Added server level KPIs for background job statistics to background job monitoring collector.

Monitoring Fixes

  • ASM-1653: Fixed a bug in Monitoring cockpit aggregated messages view.
  • ASM-1654: Added handling to transport request monitoring collector to prevent errors caused by processing of duplicated transport request records.
  • ASM-1655: Implemented proper handling of ; character custom SQL monitoring collector.
  • ASM-1662: Improved error handling and reporting in RFC call security collector.
  • ASM-1665: Collected detail table data are now saved even if the collector is terminated by an exception.
  • ASM-1667: Collector job status is now correctly updated when using "Stop monitoring" functionality in Monitoring cockpit.
  • ASM-1668 (SAP-517): Proactive security scan and resolving high priority findings.
  • ASM-1675: Fixed a "divide by 0" bug in critical DB table space percentage KPI calculation.