(DI-2305) Installation procedure

Owned by SNP
Last updated: May 03, 2023 by Tomas Hnojcik
3 min read

You need to install the CrystalBridge® Monitoring on the selected SAP system by importing standard SAP transport requests. The installation procedure requires two transport requests to be imported in the correct order to avoid any missing dependencies.

In this section:

Upgrade procedure

If you upgrade to a newer version of CrystalBridge® Monitoring, it is recommended to stop all running collector jobs on the central system before this action. Otherwise, you might experience some errors or short dumps when the collector job is executed during this upgrade process. Also when collector job(s) are not restarted after the upgrade, newly added KPIs will be not correctly included in the monitoring. The upgrade procedure consists of the same steps as the installation procedure, but you will need to import the latest transport requests.

If the import of transport requests ended with an error Component version mismatch, please check the page (DI-2305) Import of installation transport requests ended with an error 'Component version mismatch'. 

We recommend importing 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.

If you upgrade to a newer version, there is always executed the (DI-2305) Upgrade check report automatically after successful import of the CrystalBridge® Monitoring transport request.

Please check the README.txt file included in the release installation zip file for additional details. 

Before importing the SAP transport requests, please check the (DI-2305) SAP System prerequisites. If your SAP system fulfills the prerequisites, you might continue with the installation procedure. 

Installation on central SAP system

The central system serves as a central instance to:

  • Configure the general setup for monitoring  
  • Set up monitoring of other remote SAP and non-SAP systems
  • Collect all data which are saved on the central system   
  • Display collected data 

One central system can monitor multiple remote SAP and non-SAP systems, but the whole configuration needs to be done only on the central system. 


To install the CrystalBridge® Monitoring on the central system, import the following transport requests into the SAP system:

  1. Reuse Library 
  2. CrystalBridge® Monitoring

If you are using other SNP products on the central SAP system, 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 backward compatibility in mind and so older versions of SNP CrystalBridge® Monitoring should still work fine with newer versions of Reuse Library.

You might find additional details about how to check the current installed Reuse Library version in the chapter (DI-2305) Check Reuse Library Version.

In case of compatibility issues or version conflicts, please contact our (DI-2305) Contact Support. 


Component version mismatch

If the import of transport requests ended with an error 'Component version mismatch', please check the page (DI-2305) Import of installation transport requests ended with an error 'Component version mismatch'.

(Optional) Installation on satellite SAP system 

If you want to monitor any other SAP system (which is not the central system), you need to install CrystalBridge® Monitoring on the satellite system. To install CrystalBridge® Monitoring on another remote SAP system, you need to import the same transport requests into the remote SAP system:

  1. Reuse Library 
  2. CrystalBridge® Monitoring

If you are using other SNP products on the satellite SAP system, 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 backward compatibility in mind and so older versions of SNP CrystalBridge® Monitoring should still work fine with newer versions of Reuse Library.

You might find additional details about how to check the current installed Reuse Library version in the chapter (DI-2305) Check Reuse Library Version.

In case of compatibility issues or version conflicts, please contact our (DI-2305) Contact Support. 

The installation transport requests are the same. The only difference is that the satellite system doesn't require any additional setup, but the relevant objects need to be imported there. Otherwise, if CrystalBridge® Monitoring is not installed on the satellite system, it is not possible to execute the monitoring of this system from the central system.