On this page:

Related pages:

This page explains how to upgrade or uninstall the monitoring solution.

Upgrade Procedure

The following procedures explain how to upgrade the monitoring solution.

Import SAP transport requests into production systems when the traffic and load are minimal. It is recommended to import SAP transport requests outside of business hours or during weekends. ABAP Agent takes advantage of several enhancements placed in standard objects that trigger the recompilation of these objects during import. This affects SAP standard HTTP client, HTTP server, SOAP handler, BSP controllers, UI5 apps, WebDynpro pages, WebGUI pages, SAP Gateway/Backend, ST05 trace, Application Log, and Read Access Log.

Stop the ABAP Agent Services

To stop all the services before the upgrade, : 

  1. Deactivate the instrumentation in transaction /DVD/APPD_CUST.

    SAP system upgrade steps

    If you are using SAP standard report BTCTRNS1 (suspend released background jobs) during your upgrade procedures, deactivate ABAP Agent integration before executing this report. Do not deactivate ABAP Agent integration if suspended jobs with status code Z exist in table TBTCO to avoid deletion of these records.

    If suspended jobs with status code Z exist in table TBTCO, deactivate ABAP Agent integration after executing SAP standard report BTCTRNS2 (release suspended background jobs). Release version 21.2.0 contains hotfix transport requests for every release affected by critical bug ASM-585 that could lead to deletion of suspended jobs when the recommended upgradation steps are not followed. You must import the hotfix transport request before any upgrade activities, if you are using ABAP Agent version from 4.5.1902.0 to version 20.11.0. When applying this hotfix, downtime and ABAP Agent deactivation is not necessary. See Release Notes Version 21.2.0.

  2. Stop all performance metric collectors in transaction /DVD/APPD_DI_CON.

  3. Stop the HTTP SDK instances in transaction /DVD/APPD_STATUS.

  4. Stop the SDK manager, when a separate Linux machine is used for HTTP SDK instances. 

    A single Linux machine and SDK manager instance can be shared by multiple SAP systems. Ensure that you implement step 1 to step 3 along with all the other steps for all SAP systems that use the same SDK manager instance.

Update the ABAP Agent

You must import all transport requests in the following order:

  1. SNP Reuse Library
  2. SNP CrystalBridge® Monitoring
  3. AppDynamics ABAP Agent

Regenerate profiles for all /DVD/APPD* authorization roles in transaction PFCG after the ABAP Agent is imported, 

If you are using other Datavard or SNP products, it is recommended to have all the components on the same version. If a newer version of Reuse Library is already installed on the system, ensure that you do not overwrite it with an older version. Reuse Library is developed with backwards compatibility in mind and so older versions of SNP CrystalBridge® Monitoring (formerly known as Datavard Insights) and ABAP Agent should still work fine with newer versions of Reuse Library.

In case of compatibility issues or version conflicts, please contact AppDynamics support.

If you are using other SNP products, it is recommended to have all components on the same version. If a newer version of Reuse Library or CrystalBridge® Monitoring (formerly known as Datavard Insights) is already installed on the system, ensure that you do not overwrite it with an older version. ABAP Agent should still work fine with newer versions of Reuse Library and CrystalBridge® Monitoring. To know more about how to check the currently installed versions, see Check Reuse Library Version.

In case of compatibility issues or version conflicts, contact AppDynamics support.

Update the HTTP SDK

To update the HTTP SDK:

  1. Perform the following steps, if HTTP SDK instances are running directly on SAP application servers:
    1. Update ABAP agent.
    2. Use the AppDynamics HTTP SDK Installation Manager to update HTTP SDK. See Installing HTTP SDK Automatically.
  2. Perform the following steps if HTTP SDK instances and SDK manager are running on separate Linux machines:
    1. Unzip the contents of the downloaded file.
    2. Update the HTTP SDK manually, see Installing HTTP SDK Manually.

Start all ABAP Agent Services

To start ABAP agent services:

  1. Start the SDK manager when a separate Linux machine is used for HTTP SDK instances.
  2. Start the HTTP SDK instances in transaction /DVD/APPD_STATUS.
  3. Activate the instrumentation in transaction /DVD/APPD_CUST.
  4. Start all performance metric collectors in transaction /DVD/APPD_DI_CON.

Uninstall Procedure

To uninstall the monitoring solution perform the following steps.

Stop the ABAP Agent Services

Stop all the service before the uninstallation:

  1. Deactivate the instrumentation in transaction /DVD/APPD_CUST.
  2. Stop all performance metric collectors in transaction /DVD/APPD_DI_CON.
  3. Stop all HTTP SDK instances in transaction /DVD/APPD_STATUS.

Uninstall the ABAP Agent and SNP CrystalBridge® Monitoring

To uninstall, import deletion transport requests into the SAP system, in the following order:

  1. Uninstall transport for: AppDynamics ABAP agent.
  2. Uninstall transport for: SNP CB: Monitoring and RL.
  • A deletion transport request is a regular SAP transport request (workbench request) that contains a list of repository objects flagged for deletion. When importing these transport requests, the objects from the list are removed from the system, including data in the database tables. These transport requests are created based on original installation requests (same list of objects) and when you uninstall they have to be imported in reverse order as installation transports.
  • If you are using other Datavard or SNP products, ensure that you don't follow step 2 to uninstall transport for SNP CrystalBridge® Monitoring with Reuse Library (formerly known as Datavard Insights with Reuse Library) unless you plan to uninstall all Datavard or SNP products from your SAP system. Reuse Library is used by most of Datavard product components and some SNP product components. Uninstalling it may directly affect all Datavard products and some SNP products installed on your SAP system.
  • If you still want to uninstall both ABAP Agent and SNP CrystalBridge® Monitoring, please contact AppDynamics support.


Uninstall the HTTP SDK

When a separate Linux machine is used for HTTP SDK instances, make sure that no more SAP systems are using this system and stop the SDK manager.

To uninstall the HTTP SDK, delete <appdynamics>/appdhttpsdk folder. 

Default path is /opt/appdynamics/appdhttpsdk (for Linux) and C:\AppDynamics\appdhttpsdk (for Microsoft Windows).

Uninstall the Machine Agent

To stop the machine agent, see: Start and Stop the Machine Agent.

To uninstall the agent, delete the installation directory.

System Refresh Steps

As of release 20.11.0, new ABAP Agent t-codes are available. T-code /DVD/APPD_REF_EXPORT is used for backing up all ABAP Agent settings before a SAP system refresh. T-code /DVD/APPD_REF_IMPORT is used to restore all ABAP Agent settings if 'Export to ZIP file' method was used. See Restore Settings After System Refresh for more details.  

Disable and Enable Enhancements

From release 20.11.0, the release zip file contains new transport requests placed in X-Enhancements-<version> sub-folder. Please check included readme.txt file for exact transport request names.

  • Uninstall transport: AppDynamics ABAP agent enh <version> - Intended to remove all enhancements installed by ABAP Agent transport requests.
  • Transport requests for enhancement reinstallation are component specific:
    • AppDynamics ABAP agent CORE <version> enhancements - Used to reinstall all enhancements contained in 'ABAP agent CORE <version>' transport request.
    • AppDynamics ABAP agent BEP <version> enhancements - Used to reinstall all enhancements contained in 'ABAP agent BEP <version>' transport request.
    • AppDynamics ABAP agent RAL <version> enhancements - Used to reinstall all enhancements contained in 'ABAP agent RAL <version>' transport request.
    • AppDynamics ABAP agent 740 <version> enhancements - Used to reinstall all enhancements contained in 'ABAP agent 740 <version>' transport request.
    • AppDynamics ABAP agent <version> all enhancements - Used to reinstall all enhancements after they were removed by the enhancement uninstallation transport request. This transport request can be used when ABAP Agent 740 + IS-U is installed on the system.

Use this method in the following scenarios:

  • ABAP Agent enhancements (/DVD/APPD* or /DVD/MON*) are blocking SPAU_ENH step of SAP system upgrade.
  • SAP support refuses to proceed with support activities because of the presence of these enhancements.

Carry out steps from the upgrade procedure before import (Stop the ABAP Agent Services) and after import of these transport requests (Start the ABAP Agent Services). See Upgrade Procedure.