Contact Us
How you can contact us:

Upgrading Enterprise Manager

This page summarizes hints on upgrading the Introscope Enterprise Manager (EM). The focus is to run the upgrade in a way to minimize the effort on SAP Solution Manager side.


  1. The default installation folder for Introscope EM 9.x and 10.x is /usr/sap/ccms/apmintroscope.
  2. Installing a new EM on top of an existing installation is not supported.
  3. The procedure described below assumes that you continue to use the same host name and port for the upgraded EM. If you plan to change this there is no way to avoid touching the managed system setup. Furthermore, the Introscope agents accept updates to the EM connection data only with a restart: A restart of the managed systems will be needed.

Procedures for SAP Solution Manager 7.2

With SAP Solution Manager 7.2 you can install the EM into the same folder (after removing the old installation in that folder) or into a new folder. In any case the procedure will be the same:

  1. Stop the existing EM
  2. Windows: Remove the Windows service e.g. via bin/EMCtrl64 unregister.
  3. Move the existing installation to a backup folder.
  4. Perform the installation. Make sure that the same RMI port is used as for the installation of a previous version that should be replaced in SAP Solution Manager (default: 6001).
  5. Remember to install the management module package.
  6. Copy any other files that you want to keep from old EM (see Copy files from the old EM after an upgrade).
  7. In SAP Solution Manager Infrastructure Preparation Step 4 (Define CA Introscope), Discover the new installation. If the same host and port are used the previous version is replaced with the new one. Installation path is updated. Managed systems are connected and assigned to the new EM installation.
  8. In Basic Configuration step "Configure Automatically" perform the activity Push DPC Configuration to CA Introscope. See SAP Note 1751225.

Copy Files from the Old EM after an Upgrade

  1. SmartStor: The Introscope SmartStor contains the collected metrics: The location of SmartStor on disk is specified by properties
      in file <EM_HOME>/config/ (default: <EM_HOME>/data). If you want to keep the already collected metrics move these folders from the old to the new EM. By default the covered historical time range is 31 days. Metric data older than 31 days is dropped anyway automatically by the EM.
  2. The Introscope traces are stored in a folder that is configured with properties in
    <EM_HOME>/config/ (default: <EM_HOME>/traces).  If you want to keep the already collected traces move this folders from the old to the new EM.
  3. Manually transfer any custom management modules (located in <EM_HOME>/config/modules) from the old to the new location. But do not overwrite newly installed standard SAP modules with older versions.
  4. Manually transfer any customization, e.g Java VM parameters or other changed properties. Do not replace the new configuration files with the old copies since you then may loose any newly introduced properties and some settings may not be compatible. Instead, selectively transfer any customization from your old files.
    • <EM_HOME>/Introscope Enterprise Manager.lax (Java VM parameters on Unix platforms). Important: File cannot be reused when upgrading from 10.7 to 10.8 due to incompatible Java VM parameter changes. Adjust changes like -Xmx in the new file.
    • <EM_HOME>/bin/EMService.conf (Java VM parameters for Windows). Important: File cannot be reused when upgrading from 10.7 to 10.8 due to incompatible Java VM parameter changes. Adjust changes like in the new file.
    • <EM_HOME>/config/
    • <EM_HOME>/config/em-jetty-config.xml (important: The file format has changed with Introscope 10.7. See separate page for HTTPS enabling).
    • <EM_HOME>/config/users.xml
    • <EM_HOME>/config/users-sap.xml
    • <EM_HOME>/config/domains.xml
    • <EM_HOME>/config/apm-events-thresholds-config.xml
    • <EM_HOME>/config/loadbalancing.xml
  5. Copy all certificate files used for single sign-on from SAP Solution Manager. You find them in <EM_HOME>/sap/TrustedCerts.
  6. For monitoring capabilities of SAP Solution Manager copy file <EM_HOME>/config/agentclusters.xml from the old to the new location.
  7. Also for monitoring capabilities of SAP Solution Manager copy files <EM_HOME>/sap/<SolMan_SIDs> (see SAP Note 1751225).
  8. If you have a full Introscope license copy this too from folder <EM_HOME>/license and remove the default SAP.em.lic file.
  9. If the Emergency Monitoring feature is activated copy files <EM_HOME>/sap/emon/*.

DO NOT copy the contents of folder sap/plugins. This might cause versioning conflicts. If you copy the complete sap/ folder of your EM installation then make sure to delete the sub folder sap/plugins. It will be re-generated with current plugin versions after restarting the Enterprise Manager.

Example Script

This is an example script fragment illustrating the steps to be executed on Linux to perform the upgrade. It is provided to describe the upgrade activities on code level. It should be considered as pseudo-code and will not work out of the box in your environment. SAP does not provide any support for this script. Input for enhancements is welcome, though - just submit a support ticket.

Manual activities

This script should be considered as pseudo-code and will not work out of the box in your environment, for example:

  • version numbers must be adjusted
  • the file ca-eula.txt must be edited manually
Upgrade EM Script

su - myaccountforrunning Introscope


# Stop EM

cd /usr/sap/ccms/apmintroscope/bin

./ stop


# move to backup

cd /usr/sap/ccms

mv apmintroscope apmintroscope_old


# perform the new installation

mkdir /usr/sap/ccms/inst_EM

cd /usr/sap/ccms/inst_EM

unzip WILYISEM00P_x-*.ZIP


# Edit the ca-eula.txt to accept the license:

# 1. Open the file “ca-eula.txt” in a text editor

# 2. Scroll down to the end of the file

# 3. Accept the terms by setting "CA-EULA=accept" and save the file

chmod +x introscope10.7.0.307linuxAMD64SAP.bin



# extract management modules on top

cd /usr/sap/ccms/apmintroscope

unzip -o WILYISMM00P_8-70005232.ZIP


# transfer files from old installation

mkdir data

cp -R /usr/sap/ccms/apmintroscope_old/data /usr/sap/ccms/apmintroscope/data

mkdir traces

cp -R /usr/sap/ccms/apmintroscope_old/traces /usr/sap/ccms/apmintroscope/traces


# dangerous: copying files instead of manually merging changes may lead to ERRORs

#cp -f /usr/sap/ccms/apmintroscope_old/Introscope_Enterprise_Manager.lax /usr/sap/ccms/apmintroscope/Introscope_Enterprise_Manager.lax

# cp /usr/sap/ccms/apmintroscope_old/config/users.xml /usr/sap/ccms/apmintroscope/config/users.xml

# cp /usr/sap/ccms/apmintroscope_old/config/users-sap.xml /usr/sap/ccms/apmintroscope/config/users-sap.xml

# cp /usr/sap/ccms/apmintroscope_old/config/domains.xml /usr/sap/ccms/apmintroscope/config/domains.xml

# cp /usr/sap/ccms/apmintroscope_old/config/loadbalancing.xml /usr/sap/ccms/apmintroscope/config/loadbalancing.xml

# cp /usr/sap/ccms/apmintroscope_old/config/apm-events-thresholds-config.xml /usr/sap/ccms/apmintroscope/config/apm-events-thresholds-config.xml

# cp /usr/sap/ccms/apmintroscope_old/config/agentclusters.xml /usr/sap/ccms/apmintroscope/config/agentclusters.xml      

# cp /usr/sap/ccms/apmintroscope_old/config/em-jetty-config.xml /usr/sap/ccms/apmintroscope/config/em-jetty-config.xml      

# cp /usr/sap/ccms/apmintroscope_old/sap/* /usr/sap/ccms/apmintroscope/sap/       

# Compare and copy: /usr/sap/ccms/apmintroscope/config/modules  


# start new EM

cd /usr/sap/ccms/apmintroscope/bin

./ start