Enhancements

General

Agent Dependencies

As of this release, ABAP Agent components are no longer dependent on SNP ReuseLibrary.

ReuseLibrary transport request was excluded from the list of dependencies and it is no longer part of the release bundle.

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.2.1-858
  • SDK Manager - version 24.5.0

Controller connection issue in C++ SDK for Windows was resolved and newest HTTP SDK for Windows is using latest available C++ SDK 24.2.1.858.

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.

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

ABAP Agent

SAP-355 (ASM-1440): Application Event Performance and Refactoring

Several dashboards that were using event tables are now converted to get those data from analytics. This was done to decrease load to event service, while still keeping important information as events. Dashboards in question were changed to accommodate changes for both analytics replication methods (legacy/harmonized). Re-upload of dashboards may be needed.

SAP-435 (ASM-1437, ASM-1450): S/4 HANA 2023 FPS01 Compatibility

As of release 23.11.0, AppDynamics for SAP is compatible with S/4 HANA 2023 FPS01. See SAP Supported Environments.

SAP-451 (ASM-1455, ASM-1456): Business Transaction Correlation for DB Agent and Statement Propagation for HANA

ABAP Agent now propagates SQL statements collected via SAP SQL trace or HANA expensive statements as exit calls to primary database during business transaction providing more detailed view regarding SQL statement execution.

Additionally, for next controller release (24.5) correlation functionality will be available. If database agent is deployed for HANA database that is being monitored by ABAP Agent, SQL statements from business transactions will be correlated allowing user to navigate to database section of controller for more information directly from business transaction snapshot view. See Match Rule Settings.

SAP-463 (ASM-1493) Safety Limit for SAT Traces

SAT traces started by ABAP Agent now have safety limits, preventing scenario where it could start too many trace instances causing performance loss. This safety limit is customizable via expert parameter to adjust for system capabilities. See Expert Settings.

Monitoring

SAP-361 (ASM-1031, ASM-1037) Refactor /DVD/MON* roles

Authorization roles /DVD/MON_ADMIN, /DVD/MON_VIEWER, /DVD/MON_SATELLITE (these are used within CrystalBridge® Monitoring) have been refactored. Excessive and not needed authorization objects were removed, duplicate objects were merged and ambiguous objects have been specified better.

SAP-436 (ASM-1438) ICM Cache Monitoring

ICM Cache related KPIs were added to ICM Monitoring. New metrics added, ICM dashboard has been adjusted (re-import of dashboard is needed for this new feature) and new out of the box alerts created for ICM cache metrics. See ICM Monitor.

SAP-450 (ASM-1410, ASM-1419) ReuseLibrary Dependency Removed

CrystalBridge® Monitoring has been successfully decoupled from ReuseLibrary component, which will decrease size of transport package and significantly reduce import time.

SAP-459 (ASM-1442) Web Dispatcher Monitoring 

Web Dispatcher monitoring is now fully compatible with release 781 and newer. Type G RFC destination can be used to connect to newer Web Dispatcher instances. See Monitor SAP Web Dispatcher.

HTTP SDK

SAP-433 (ASM-1434) C++ SDK and OpenSSL Update

HTTP SDK now uses newest C++ SDK component, which complies with latest security standards and OpenSSL has been updated to 3.0.13.

SAP-462 (ASM-1488) HTTP SDK Deployment for Shared Environments

Local HTTP SDK now supports shared folder deployment, meaning it will be possible to install multiple local HTTP SDK instances on a shared drive.

Resolved Issues and Improvements

ABAP Agent Improvements

  • ASM-1328: SDK Manager was recompiled with newer JDK, allowing usage of TLS1.3.
  • ASM-1473: Added functionality to Housekeep Collector that will trigger automatic trace (ATRA) files sync, due to issue in some SAP releases not executing it after every trace causing storage problems.
  • ASM-1482: ABAP Agent housekeeping logic for SAT ABAP trace now automatically triggers trace directory reorganization to avoid issues documented in SAP note 3246603.

ABAP Agent Fixes

  • ASM-1506: Fixed SQL join issue with S/4 Order to Cash in BIQ default content.
  • ASM-1508: Fixed issue where SDK manager could not access logs for newest HTTP SDK version.

Monitoring Improvements

  • ASM-1351: Added new KPIs to CrystalBridge® Monitoring, measuring HANA CPU thread and core usage.
  • ASM-1409: Added cockpit auto refresh after KPI wizard, allowing to instantly see result of newly defined KPI and detail table.
  • ASM-1412: Added new paging file monitoring KPIs.
  • ASM-1414: Added "Profile" column to excluded KPIs pop-up when starting monitoring.
  • ASM-1427: Added "Top 5 Delayed Jobs" detail table to CrystalBridge® Monitoring Cockpit.

  • ASM-1448: Added prefix “CTS” into descriptions for existing detail tables in the collector for transport requests.

  • ASM-1449: Assignment of the KPI for the duration of the longest-running background job to "Top 5 Delayed Jobs" detail table.

  • ASM-1451: Improved ORACLE KPI long texts.
  • ASM-1474: Optimized qRFC collector data selectors improving performance.
  • ASM-1496: Improved "Display Monitored KPIs" popup for monitoring profile in CrystalBridge® Monitoring cockpit. 

Monitoring Fixes

  • ASM-1365: Consistent time settings across CrystalBridge® Monitoring for central and satellite systems.
  • ASM-1396: Fixed issue with KPI graph display taking too long due to loading KPI data from all servers, instead for only selected servers.
  • ASM-1408: Fixed issue where runtime error collector could not resolve package of specific object types.
  • ASM-1411: Fixed potential SQL injection vulnerabilities.
  • ASM-1418: Fixed issue where SID (System ID) column could be suppressed in detail table view in CrystalBridge® Monitoring cockpit where detail table had this column explicitly defined.
  • ASM-1425: Fixed issue where RFC security collector would crash when incorrect timestamp format was processed.
  • ASM-1428: Fixed possible wrong calculation of KPI BTC_SLR_DELAY_S_TOTAL due to orphaned job.
  • ASM-1432: Fixed issue, where unsupported data types could cause error in custom detail tables.
  • ASM-1444: Fixed issue where runtime of collector run was stored in seconds instead of milliseconds.
  • ASM-1445: Refactored handling of standalone ASSIGN command on dynamic tables to not rely on sy-subrc.

  • ASM-1452: While deleting a detail table, the records about generated versions of the detail table are now also deleted from table /DVD/MON_DETVER.

  • ASM-1473: Fixed time zone issue where RFC Security collector could start failing after moving to daylight savings time.

  • ASM-1476: Fixed issue where collector for qRFC queue details did not load all records from table TRFCQDATA if no corresponding status records existed.

  • ASM-1483: Adjusted URLs into absolute URLs before calling browser functionality from CB Monitoring.