Skip to end of metadata
Go to start of metadata

Upgrade Introscope 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, also on Solution Manager side.

Traps

  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 Solution Manager 7.2

With 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 previous installation that should be replaced in 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 below Copy files from the old EM after an upgrade).
  7. In 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 so-called Introscope SmartStor contains the historical data for collected metrics: The location of SmartStor on disk is specified by properties
    1. introscope.enterprisemanager.smartstor.directory
    2. introscope.enterprisemanager.smartstor.directory.archive
      in file <EM_HOME>/config/IntroscopeEnterpriseManager.properties. 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.
  2. The Introscope traces are stored in a folder that is configured with property introscope.enterprisemanager.transactionevents.storage.dir in <EM_HOME>/config/IntroscopeEnterpriseManager.properties.  If you want to keep the already collected traces move this folders from the old to the new EM.
  3. 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 of existing configuration files. Do not completely replace the new configuration files with the old copies since you then may loose any newly introduced properties. Instead, selectively copy and paste any customization from your old files. Examples to be adjusted:
    1. Java VM parameters in file Introscope Enterprise Manager.lax or EMService.conf
    2. Other modified properties in files <EM_HOME>/config/IntroscopeEnterpriseManager.properties
    3. HTTPS configuration in <EM_HOME>/config/em-jetty-config.xml. Note: Starting with Introscope 10.7 the format of this file has been substantially changed - due to the switch to Jetty 9.4.x. Copying directly from 10.5 or earlier will fail. See SSL Communication for Introscope Enterprise Manager for details.
    4. Users and permissions in <EM_HOME>/config/users.xml, <EM_HOME>/config/users-sap.xml, <EM_HOME>/config/domains.xml,
    5. Thresholds for number of metrics, agents: <EM_HOME>/config/apm-events-thresholds-config.xml,
    6. Cluster load balancing: <EM_HOME>/config/loadbalancing.xml.
  5. Copy all certificate files used for single sign-on from SolutionManager. You find them in <EM_HOME>/sap/TrustedCerts.
  6. For monitoring capabilities of SAP SolutionManager and Focused Run:
    1. copy file <EM_HOME>/config/agentclusters.xml from the old to the new location.
    2. copy files <EM_HOME>/sap/<SolMan_SIDs>.e2emai.properties respectively <EM_HOME>/sap/<FRUN_SIDs>_srsm.e2emai.properties for FRUN (see SAP note 1751225).
  7. Only if you have a full Introscope license: Copy this too from folder <EM_HOME>/license and delete the default license SAP.em.lic. There must be exactly one license file in this folder.
  8. If Emergency Monitoring feature available starting with Introscope version 9.7 is activated copy files <EM_HOME>/sap/emon/*.
  9. 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.

Warning

This script is provided to describe the upgrade activities on code level. It is not expected to work out of the box in your environment and SAP does not provide any support for this script. Input for enhancements is welcome, though - just leave a comment.


Upgrade EM script
su - myaccountforrunning Introscope

# Stop EM
cd /usr/sap/ccms/apmintroscope/bin
./EMCtrl.sh 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 ca-eula.txt
chmod +x introscope10.7.0.307linuxAMD64SAP.bin
./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/*.e2emai.properties /usr/sap/ccms/apmintroscope/sap/		
#Compare and copy: /usr/sap/ccms/apmintroscope/config/modules	

# start new EM
cd /usr/sap/ccms/apmintroscope/bin
./EMCtrl.sh start

# To be done later
rm -rf /usr/sap/ccms/apmintroscope_old



  • No labels

1 Comment

  1. Procedures for Solution Manager 7.2 → Step 6 If the same host and port, and installation path is used (same username and password), just click refresh.