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.

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 - version 25.4.0-1060
  • SDK Manager - version 24.11.0

ABAP Agent

SAP-548 (ASM-1753): Dedicated HTTP Proxy Settings for Remote HTTP SDK

ABAP Agent configuration now contains dedicated HTTP proxy settings for remote HTTP SDK deployment. See Set Up SAP ABAP Agent.

SAP-555 (ASM-1701): S/4 HANA 2023 FPS03 Compatibility

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

SAP-562 (ASM-1760): SAP S/4 HANA 2023 Cloud Private Edition Certification

AppDynamics for SAP is now recertified by SAP for S/4 HANA 2023 Cloud Private Edition.

Monitoring

SAP-563 (ASM-1688): Extended SAP PI/PO Monitoring

New KPIs for success and waiting PI messages in inbound and outbound queues have been added. New fields for status details, error codes and integration scenarios were added into the existing detail table PI error messages.

Added new detail table PI scenario details for aggregated PI messages per status and configured integration scenarios.

HTTP SDK

SAP-487 (ASM-1741, ASM-1748): FIPS Compliance Adjustments

HTTP SDK and C++ SDK now implement FIPS compliant SSL handling.

Resolved Issues and Improvements

ABAP Agent Improvements

  • ASM-1754: BIQ collector now supports strict SQL mode on 750 and newer SAP_BASIS releases. This allows usage of special keywords and advanced join conditions in defined SQL statements.
  • ASM-1759: Logic in t-code /DVD/APPD_DI_CON was adjusted based on recent /DVD/MON changes.

ABAP Agent Fixes

  • ASM-1749: Expert parameters are now correctly buffered after first access to /DVD/APPD_PARAM table.
  • ASM-1755: Fixed pointer bug in KPI wizard AppDynamics integration step that caused overwriting of previously defined metric mapping.

Monitoring Features

  • ASM-884: KPI Creation wizard supports the SQL statements validation for the external database systems via the configured secondary DB connections.
  • ASM-1168: New self-monitoring KPI to report if the configured RFC user in the used ABAP connection is missing CB Monitoring authorizations. If this RFC user is missing the required authorizations, the respective alert is raised.
  • ASM-1269: Logging key user actions into the application logs for better traceability of executed actions in CB Monitoring, like managing monitored systems, collector jobs or licenses.
  • ASM-1336: New KPIs for reporting the average and total commit times on the monitored database in the Collector for Workload Statistics.
  • ASM-1618: New collector and KPIs to report delta values of SQL inserts, updates and delete operations for table activity available in the transaction ST10.
  • ASM-1672: Collector for RFC ping tests supports wildcards in RFC destination names while defining the input rules for RFC destination(s) monitoring.
  • ASM-1690: New KPIs and collector for HANA logging monitoring, covering HANA log volume usage, backup sizes and average commit times. New KPI for maximum backlog size in HANA system replication, and new detail table for HANA System replication data.
  • ASM-1691: New KPIs for HANA delta merges monitoring to report metrics about the active tasks, execution times, row counts, and error rates using 1-hour rolling averages.
  • ASM-1692: New KPIs for HANA Native Storage Extension (NSE) to monitor and analyze the performance of buffer caches in the HANA system, including metrics about the CS tables and page loadable storage.
  • ASM-1711: Added new check for the system time zone consistency between application server and the OS while starting CB Monitoring on the central system and raising popup in case of any mismatches.
  • ASM-1715: New KPIs for HANA logging to monitor backup catalog performance, including query runtime, total entry count, and age of the oldest record in the backup catalog.
  • ASM-1723: Added new functions to start and stop all collector jobs scheduled on the central system for the easier collector job management, for example in the upgrade procedure.
  • ASM-1736: New collector and KPIs for Oracle database table activity to report metrics about the database block statistics that were changed (modified) on the Oracle database. New detail table Oracle table activity to report the top N objects with the highest activity since the last snapshot.

Monitoring Improvements

  • ASM-1417: Improved messaging for the long-running collectors that were canceled or switched into the asynchronous mode execution.
  • ASM-1453: Collector for table sizes calculates and reports also LOB sizes into the existing detail table DB table size statistics on HANA, Oracle and DB6 databases.
  • ASM-1556: Button for displaying DB connection details while adding a new system is shown only if the user has required permissions for such action.
  • ASM-1625: Enhanced authorization roles to contain required authorizations for the remote function calls introduced on the newer SAP releases (750).
  • ASM-1631: Improvement to allow system node selection, even no KPI data is available, to ensure the visibility of the possible raised messages by the executed collector jobs.
  • ASM-1659: KPI Info popup shows additional information about the collector, scheduling frequency and monitoring status, including currently running monitoring profiles with the last KPI value collection timestamp per monitored system.
  • ASM-1660: Detail table info popup shows additional information about the collector, assigned KPIs, assigned profiles, and message occurrence statistics for the assigned collector.
  • ASM-1689: Reorganized HANA related KPI groups and KPI descriptions for better readability, consistency and clarity.
  • ASM-1706: Changed field name for DB trigger's creation time in the existing detail table DB trigger details to clarify that the value originates from the database.
  • ASM-1714: Improved validation logic for collected data availability per monitored system to report health status of the monitoring based on thresholds defined for the occurred error messages and collected KPI values in the last 24 hours.
  • ASM-1726: Created predefined list of forbidden user actions in CB Monitoring, if no valid license is installed. For example, it's not possible to start/resume the collector jobs or add new systems.
  • ASM-1728: Improved performance and clarity of KPI chart rendering by removing data point markers from jqCharts, and enhanced error handling in jqCharts processing logic.
  • ASM-1729: CB Monitoring logs were included into the AppDynamics ABAP Agent logs to ensure the consistent logs are downloaded from the monitoring across various versions.
  • ASM-1734: Check connection functionality in the System info tab executes additional validation checks to show the current health status of the monitoring on the respective SAP system. For non-SAP systems, the original connection check remains the same.
  • ASM-1737: Possibility to suppress popups when starting the collector jobs outside the dedicated monitoring GUI, for example from the other SNP products.
  • ASM-1739: Enhanced collector for IDocs to support the reporting details for successful IDocs, if configured in the dedicated input table according to the custom requirements.
  • ASM-1752: Added new check for specific HANA version into the collector for HANA Native Storage Extension (NSE) to avoid potential interference with unload behavior on older HANA systems.

Monitoring Fixes

  • ASM-1504: Correct value of the configuration property is retrieved, if this property is manually disabled by setting the initial/empty value.
  • ASM-1622: KPI Creation wizard does not add extra space character while splitting the long SQL strings in the text editor.
  • ASM-1634: SQL-based calculation KPIs do not raise any error messages if their source KPIs are not monitored within the same profile, but the last collected KPI value for the source KPI is used within the calculation function.
  • ASM-1658: Displaying correct collector job status Running if the previous run of the long-running collector job is not finished yet.
  • ASM-1702: Message that no KPI found for the monitoring is not raised anymore if the collector jobs have been started from a different application server due to buffer desynchronization.
  • ASM-1703: Collector for number ranges handles the last snapshot data overlapping, if data collected from more central systems, by defining the caller ID field for data selection.
  • ASM-1705: Integration logic correctly identifies the central system ID, even if the RFC destination differs from NONE.
  • ASM-1709: DB hosts for Oracle based systems are detected even if the required statistics are not defined on the lower Oracle database releases.
  • ASM-1718: Correct message that user is not authorized to update system definition is raised, if the monitoring user is missing the required authorization.
  • ASM-1720: Removed obsolete buffer reset logic for the monitoring tables that are no longer buffered to not raise misleading errors into the system trace during the monitoring.
  • ASM-1722: Collector jobs are reliably stopped after license expiration and do not remain active after calling stop functionality in the background processing.
  • ASM-1724: Resolved runtime error STRING_TOO_LONG while concatenating the qRFC parameters in the Collector for qRFC Queue details by defining the maximum string limit length.
  • ASM-1732: Collector for HANA threads skips the data collection for connections, if no connection ID was identified and collects remaining HANA thread related metrics instead of its termination.
  • ASM-1733: Collector for Oracle alert logs does not report duplicated records into the details and data is selected based on the last collector execution timestamp instead of a hardcoded 1-day window.
  • ASM-1735: Changes in the user settings for the checkbox Chromium compatibility (wait for JS event) retains the same after restarting the CB Monitoring.
  • ASM-1743: Collector for request queues is now compatible with older SAP releases, where the required parameters of called function to get data are missing.
  • ASM-1756: All paused collector jobs still remain in paused status after upgrading monitoring into the newer version.
  • ASM-1757: Improved KPI chart rendering to properly handle special characters in KPI descriptions and prevent jqCharts from freezing.