(DI-2202) Release Notes

Owned by SNP
Feb 08, 2022
3 min read

New features

  • ASM-798 - Added new item into System context menu to delete selected system (more details)

  • Added new context menu for server node with the following functionalities: (more details)

    • ASM-799 - Possibility to delete not monitored and excluded server (obsolete server)

    • ASM-826 - Possibility to exclude server from the monitoring or include into monitoring

  • ASM-832 - Added new detail table to the collector for HANA Replication Details monitoring (more details)

Improvements

  • ASM-809 - Enhanced check and displayed message when using a user with initial password in configured HTTP Destination for PI Monitoring (more details)

  • ASM-835 - Collector for SAP PI Channels Monitoring reports all error PI Channels into detail table (also in case when this PI channel does not have any process log filled) (more details)

    • added new parameter ‘INCLUDE_ERROR_LOGS_TO_DETAILS’ to define whether process log records should be reported into a detail table or not

  • ASM-836 - Added new Alert thresholds for the following default KPIs:

    • BAT_DB_INSERT_AG - “Average DB insert [ms]”

    • BAT_DB_SELECT_AG - “Average DB select [ms]”

    • DB_TRIGGER_CNT_INVALID - “Number of Invalid DB Triggers [count]”

    • ENQ_ENTR_P - “Usage of SAP lock table [%]”

    • HDB_ALERT_ERROR - “HANA alert type - error [count]”

    • HDB_ALERT_HIGH - “HANA alert type - high [count]”

    • HDB_CPU_UTIL_P - “Total CPU utilization (avg 5 mins) [%]”

    • STAT_DB_DIALOG_AVG - “Average Response Time for Users on Database [ms]”

    • STAT_DB_RESP_AVG - “Average Response Time on Database [ms]”

    • WP_COMMIT - “Number of WP in COMMIT state [count]”

  • ASM-828 - Added new fields for buffer type and buffer size into detail table “Number range info” (more details)

  • ASM-839 - Extended password length for the SAP BO user to 100 characters (more details)

  • ASM-842 - Created a new report to generate custom KPIs for transactional workload monitoring (more details)

  • ASM-846 - Adjustments in Java application to execute JCO Service for JMX Connection for SAP BO System monitoring (more details)

    • Removed dependencies on Log4j libraries, usage of own logging mechanism

    • When starting the JCO service, all logs are automatically written into the log file, for easier root cause investigation when the JCO service has not started as expected (more details)

    • Added scripts (for Unix/Windows) to start the JCO Service for JMX Connection (to be able to handle java dependent errors)

Heatmap

  • Obsolete Basis and ETL Analyses for Fiori application are not included in the standard package anymore

Resolved issues

  • ASM-811 - Possibility to define a custom ID of the customer through Startup wizard. Customer ID can be only retrieved from the installed valid license (more details)

  • ASM-821 - Failure of the Collector for Table size statistics on higher HANA releases

  • ASM-827 - Collector for HANA Save Points (SPs) performance did not collect the long running SPs (running longer than collector job’s period) (more details)

  • ASM-829 - Alert thresholds not copied correctly, when copying the content of default profile to any custom profile (more details)

  • ASM-838 - Incorrect message displayed when no server defined for the monitoring of the system

  • ASM-840 - Not possible to monitor local HANA Database with ‘DEFAULT’ DB Connection on HANA system

  • ASM-854 - If more Alert thresholds are defined for one KPI, invalid Alert threshold details are displayed when selected through the KPI context menu

  • ASM-873 - Assignment of not existing (obsolete) Monitoring area(s) to the newly added SAP System on the central system

  • ASM-874 - Incorrect message displayed in KPI Wizard when SQL is valid, but detail table name does not start with Z* or Y*

  • ASM-875 - Missing authorization to test SQL statement on a remote system with Satellite user defined in RFC destination