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

If you are using other SNP products, it is recommended to have all components on the same version. If a newer version of CrystalBridge® Monitoring 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.

From the Agent version 24.5.0, SNP ReuseLibrary is no longer part of Agent dependencies and it is removed from the release bundle.

You must import all transport requests in the following order:

  1. Pre-upgrade cleanup for the Agent version >= 25.2.0.
  2. SNP Reuse Library only for the Agent version <=24.4.0.
  3. SNP CrystalBridge® Monitoring.
  4. Splunk AppDynamics Monitoring Content.
  5. Splunk AppDynamics ABAP Agent Enhancements for Agent version >= 25.2.0.

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

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.

Re-upload application dashboards

Due to occasional changes in metric reporting or dashboard adjustments it is recommended to re-upload default dashboards after performing ABAP Agent upgrade.

  1. Delete old dashboards from controller. See, Manual Deletion of Dashboards.
  2. Upload default dashboards again in transaction /DVD/APPD_DASHBOARD. See, Direct Dashboard Upload to the Controller.

Uninstall Procedure

To uninstall the monitoring solution perform the following steps.

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

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. Recommended: Pre-upgrade cleanup for the Agent version >= 25.2.0.
  2. Uninstall transport: AppDynamics ABAP agent.
  3. Uninstall transport: SNP CB: Monitoring and RL.
  4. Optional: Uninstall transport: SNP CB: Reuse Library.
  • A deletion transport request is a regular SAP transport request (workbench request or transport of copies) 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 SNP products and the Agent version is <= 24.5.0, ensure that you don't follow step 3 to uninstall transport for SNP CrystalBridge® Monitoring with Reuse Library unless you plan to uninstall all SNP products from your SAP system. Reuse Library is used by some SNP product components. Uninstalling it may directly affect SNP products installed on your SAP system.
  • Uninstall transport from step 3 still includes SNP Reuse Library objects flagged for deletion up to the Agent version <= 24.5.0. This is intended for installations that previously used Agent version <= 24.2.0 where SNP Reuse Library was still included. From the Agent version >= 24.8.0, optional step 4 was added for SNP Reuse Library uninstallation and step 3 no longer contains any SNP Reuse Library objects flagged for deletion.
  • If you still want to uninstall both ABAP Agent, and SNP CrystalBridge® Monitoring and SNP Reuse Library, 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

Please check included readme.txt file for exact transport request names and more details.

  • In the Agent version <= 24.11.0, the release zip file contains transport requests intended for enhancement uninstallation and enhancement reinstallation placed in X-Enhancements-<version> sub-folder.
  • As of the Agent version >= 25.2.0, the enhancement uninstallation transport is repurposed as pre-upgrade cleanup transport request and is moved to 0-AbapAgentUpgrade-<version> sub-folder.
  • As of the Agent version >= 25.2.0, enhancements are no longer included in the Agent installation transport requests, but are separated into individual transport requests and moved to 3-AbapAgentEnhancements-<version> sub-folder. These can also be used for enhancement reinstallation process. 

Transport request for enhancement uninstallation and pre-upgrade cleanup:

  • Uninstall transport: AppDynamics ABAP agent enh <version> - Intended to remove all enhancements installed by ABAP Agent transport requests. As of the Agent version >= 25.2.0, also intended as first step of ABAP Agent upgrade and ABAP Agent uninstall procedure. 
  • Transport requests for enhancement (re)installation are component specific - only use enhancement transports intended for ABAP Agent components that you are currently using:
    • AppDynamics ABAP agent CORE <version> enhancements - Used to  (re)install enhancements intended for 'ABAP agent CORE <version>' components.
    • AppDynamics ABAP agent BEP <version> enhancements - Used to (re)install enhancements intended for 'ABAP agent BEP <version>' components.
    • AppDynamics ABAP agent RAL <version> enhancements - Used to (re)install enhancements intended for 'ABAP agent RAL <version>' components.
    • AppDynamics ABAP agent 740 <version> enhancements - Used to reinstall all enhancements contained in 'ABAP agent 740 <version>' transport request.
    • AppDynamics ABAP agent IS-U <version> enhancements - Used to (re)install enhancements intended for IS-U specific functionality.

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.
  • When upgrading the Agent to version >= 25.2.0 - uninstall all enhancements before upgrade, reinstall relevant enhancements based on used ABAP Agent components after upgrading ABAP Agent upgrade.
  • When uninstalling the Agent version >= 25.2.0 - uninstall all enhancements before uninstalling ABAP Agent and other components to reduce timeframe of potential impact on the SAP system that can be caused by enhancement removal.

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.