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:

  • Java Agent JCo Extension - version 20.5.0

  • SDK Manager - version 20.5.0

Components With Different Versions

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

  • C++ SDK - version 21.7.4-283

New Dependency Transport

ABAP Agent dependencies folder in the release zip file now contains a new mandatory transport request "Datavard Insights AppDynamics Content <VERSION>" that needs to be imported after Datavard Insights and before ABAP Agent transports.

The order in which the transport requests must be imported remains the same:

  1. ABAP Agent dependencies,
  2. ABAP Agent (package based on system version),
  3. ABAP Agent BIQ.

Individual packages contain package-specific requirements and relevant information like optional components, links to documentation, etc in included readme.txt file.

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

ABAP Agent

SAP-212 (ASM-825): Removed Version Dependencies

As of release 22.2.0, ABAP Agent should be completely version-independent from Datavard Insights. Part of frequently changed integration logic was moved to a standalone prerequisite transport request. As a result, newer ABAP Agent installations will be possible if older Datavard software versions exist in the SAP systems.

SAP-217 (ASM-849): Match GUI Transaction by Programs

Match rule type for GUI Transaction business transactions was extended to allow matching by SAP Report and Reference Program. This allows the creation of business transactions based on specific reports and programs rather than SAP transaction codes.

Splitting logic remains unchanged. For example, it is not possible to set up splitting by Report or Reference Program name because of Business Transaction limitations and constraints.

Datavard Insights

SAP-210 (ASM-834): Tech Debt Resolution and Usability Improvements 

Multiple technical depth items were addressed in Datavard Insights. Some fixes addressed maintainability of the code base and others helped to improve the usability of the solution. Individual items of this effort are listed under Resolved Issues and Improvements.

SAP-213 (ASM-755): Replicate Remote System Metrics via HTTP SDK

Metrics and events collected from remotely monitored systems can now be replicated to the controller via preexisting HTTP SDK instances when Metric API is set to "SDK" in the Insights Connector Mapping table. This effectively removes all dependencies on the Machine Agent HTTP listener.

With this approach, the metrics are reported under the tier where the used HTTP SDK instance is registered. To make sure that metrics from the local systems don't mix with metrics from the remote systems, ABAP Agent adds a "sub-folder" into the metric path. This can be adjusted using the Custom Path field.

Status check logic was adjusted to check mapping connections based on the selected metric API.

SAP-214 (ASM-832): Hana System Replication Connection Monitoring and Alerting

HANA high availability monitoring was extended to generate error events based on detected incidents and new alerting thresholds were defined for this collector. The alerting thresholds can be used as templates for Health rule generation and will also produce alert events when Datavard Insights issues an alert based on the thresholds.

The collected metrics and events are also available via the updated out-of-box HANA High Availability dashboard. 

SAP-215 (ASM-727, ASM-831): Database Trigger Monitoring 

A new collector for database trigger monitoring was added to the default set of collector jobs. The collected data are also available via an updated out-of-box SAP Database dashboard.

SAP-216 (ASM-727): User Password Monitoring

A new collector for user password monitoring was added to the default set of collector jobs. The collected data are also available via the updated Work Process and User dashboard.

SAP-218 (ASM-829): Option to Copy Default Insights Profiles  

Default Datavard Insights profiles and all their dependencies can now be copied into a custom Z* profile. This is useful when users need to remove or add certain KPIs from the scope of the monitoring profile. See How to exclude default KPIs from default monitoring.

SAP-219 (ASM-844): Replicate Insights Alerts as AppDynamics Events 

Datavard Insights alerting engine is now fully integrated into ABAP Agent Insights integration. When Insights detects an alerting threshold breach, it creates an alert based on predefined criteria.

When alert event replication is active in Datavard Insights Connector Mapping, the alerts are seamlessly replicated as AppDynamics application events of custom event type /DVD/APPD_CC_S_ALERTS.

BiQ

SAP-168 (ASM-861): New Default Content

A new type of default ECC "Procure to Pay" basic business process was added that is focused on individual document items.

SAP-206 (ASM-794): Cluster table support

Simple free-form SQL joins will now work with cluster table types. This use case does not currently support the change document logic.

Resolved Issues and Improvements

ABAP Agent

  • ASM-807: /DVD/APPD_ADMIN role was extended with missing role needed for SAPGUI SAT trace execution.
  • ASM-830: The dashboard upload error log now contains a detailed explanation of why the upload failed.
  • ASM-843: Added handling for special cases when long strings in constructed JSON files are truncated after a '\' character. 
  • ASM-898: Housekeeping logic was extended to handle the Incident Log buffer.

Datavard Insights

  • ASM-757 (SAP-210): A list of all shipped KPIs was reviewed and Insights documentation was updated accordingly.
  • ASM-798 (SAP-210): It is now possible to delete Insights system definitions via right-click menu in the Insights cockpit. See Delete System from Monitoring. 
  • ASM-799 (SAP-210): It is now possible to delete Insights server definitions via right-click menu in the Insights cockpit. See System Tree.
  • ASM-826 (SAP-210): It is now possible to exclude / include servers from the scope of monitoring using right-click menu in the Insights cockpit. See System Tree.
  • ASM-836 (SAP-210): Some KPI descriptions and thresholds were updated.
  • ASM-841 (SAP-219): Review and updates made in the list of default alert thresholds.
  • ASM-852 (SAP-219): Default alert thresholds have been redefined for AppDynamics Insights job profiles.
  • ASM-809: Improved error handling and logging when incorrect user password was entered for PI monitoring connection.
  • ASM-811: Custom CUSTOMER_ID value can no longer be entered using Startup Wizard when no license is installed. When Trial license is active, the wizard step is skipped.
  • ASM-821: Table size statistics collector was adjusted to work correctly on newer HANA DB releases. 
  • ASM-827: HANA Save point performance collector was adjusted to detect save points running longer than the collector period. 
  • ASM-828: Buffer type and buffer size fields are now available in events created by the Number Range Collector.
  • ASM-835: PI Channel collector will now also report channels in error state without error log. Error message will be constructed from a short log string when available.
  • ASM-838: Insights message log no longer displays incorrect messages when a monitored system does not have an active server definition.
  • ASM-839: UI field for storing BOBJ JMX connector encrypted password will no longer truncate longer password strings.
  • ASM-839: Local HANA database can now be monitored using the Insights Native HANA system definition. This did not previously work because of a bug in DB connection processing logic.
  • ASM-846: BOBJ JMX connector java application was rebuilt with simplified logging.
  • ASM-854: Alert threshold maintenance screen now displays the correct threshold definition.
  • ASM-874, ASM-875: KPI Wizard improvements and fixes.