Enhancements

General

Components Without Updates

There are components included in this release that were not updated. The following components report a version where they were last changed:

  • SDK Manager - version 22.8.0

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 23.11.1-753

New HTTP SDK Compatibility Version

Due to recent C++ SDK changes in oldest supported GLIBC and windows C++ runtime library versions, ABAP Agent now 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 C++ runtime versions. Does not support call graphs, but contains features added up to the latest 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-150 (ASM-678): SAP GUI End User Monitoring (Beta)

ABAP Agent now supports End User Monitoring (EUM) for SAP GUI sessions. See SAP GUI End User Monitoring.

Once configured, the SAP GUI EUM data will be available under 'Connected Devices' sections of 'User Experience' area.

SAP-319 (ASM-1325): Deferred Error Reporting

Business Transaction errors and Exit Call errors are now reported at the end of the Business Transaction / Exit Call. If more than one error is detected, all errors are reported using one HTTP SDK call as long as the newest HTTP SDK version is used. If older HTTP SDK version is used, each error is reported using separate HTTP SDK call.

New 'Error Propagation' match rule settings are available. See Match Rule Settings.

SAP-323 (ASM-1345): Custom Naming Logic for Backends

Backend rules can be defined to override default RFC and HTTP backend / remote service naming logic.

Use the new UI to define match conditions and naming conditions. BT Name Filter can be used to apply backend rule only to specific Business Transactions.

See Configure Backend Naming.

SAP-337, SAP-406 (ASM-1317): HTTP SDK Update and TLS 1.2 / 1.3 support

Updated the HTTP SDK components to the latest versions - C++ SDK 23.11..0, OpenSSL 3, CivetWeb 1.16. HTTP SDK now uses TLS version 1.2 / 1.3 by default. 

SAP-363 (ASM-1334): S/4 HANA 2022 FPS02 Compatibility

The latest version of AppDynamics for SAP is compatible with S/4 HANA 2022 up to FPS02. See SAP Supported Environments.

SAP-371 (ASM-1323): Event Limit Parametrization

It is now possible to override default event limit using Expert Settings.

Monitoring

SAP-314, SAP-357 (ASM-1321): Optimization of Monitoring Profiles

Monitoring profiles were harmonized. New profiles were added, redundant profiles are discontinued and periodicity of some metrics was updated. See Mapping Between KPIs and Metrics.

SAP-365 (ASM-1324): Web Dispatcher Compatibility Adjustments

Web Dispatcher monitoring was no longer possible on newer SAP Web Dispatcher releases due to changed documented in SAP note 3277881. As of this release, it is possible to setup Web Dispatcher monitoring for any Web Dispatcher instance that is installed and running on an SAP NetWeaver ABAP application server.

See SAP Web Dispatcher and Monitor SAP Web Dispatcher.

SAP-367 (ASM-952): Background Job Monitoring Performance Tuning

Background job monitoring collector was redesigned for improved performance. New configuration options 'Persist' and 'Persist Period (minutes)' were added to allow the collector to repeatedly report the same delayed / long running job.

See Performance Collector Settings.

SAP-405 (ASM-1210, ASM-1343): Removing Legacy Dependencies

Some legacy Monitoring components are no longer included as of this release. This reduces the size of installation transport requests and decreases the footprint of Monitoring on the SAP system where it is installed.

None of the removed components directly interacted with AppDynamics integration, so no loss of functionality is to be expected.

Resolved Issues and Improvements

ABAP Agent Improvements

  • SAP-402 (ASM-1339): New utility program for merging agent transports into workbench requests was added.
  • ASM-1329: Agent activation logic was isolated from rest of the agent logic. 

ABAP Agent Fixes

  • ASM-1335: Backend declaration will no longer fail due to empty port value.

Monitoring Improvements

  • ASM-1260: Option to download Monitoring logs for standalone installations.
  • ASM-1278: Additional statistics are now collected for failed monitoring jobs.
  • ASM-1289: Improved error handling and logging in the SQL collector.
  • ASM-1294: Background job collector now tracks also delayed jobs with corrupt start conditions.
  • ASM-1295, ASM-1352: Improved error handling and logging for incorrect SAPDBHOST values.
  • ASM-1307: Improved error handling and logging in logic for adding new monitored systems.
  • ASM-1344: Work process monitoring now tracks number of work processes waiting for semaphore.
  • ASM-1347: Full error stack is now available in Monitoring log if a collector fails.
  • ASM-1356: Adjusted system call authority checks to include correct program names and adjusted the authorization roles accordingly.

Monitoring Fixes

  • ASM-1151: Oracle KPI generation program will now be automatically started when local monitored system has Oracle DB.
  • ASM-1203: KPI wizard no longer overwrites retention time.
  • ASM-1290: KPI wizard no longer display input tables from previous wizard execution.
  • ASM-1309: Big monitoring job period will no longer cause arithmetic overflow error. 
  • ASM-1327: Multiple small fixes in RFC security monitoring collector.
  • ASM-1338: Aggregated view will now display monitoring messages correctly for short time frames.
  • ASM-1340: RFC error states are now correctly handled in system log monitoring collectors.
  • ASM-1360: RFC security monitoring collector will now correctly parse timestamp formats in all supported SAP releases.

See SNP CrystalBridge® Monitoring Release 2311.