Upgrade Introscope Manually

Contents
apmdevops97
Contents
You can upgrade the Enterprise Manager, WebView, and ProbeBuilder manually.
Follow these steps:
  1. Perform a fresh install of Introscope, using the automated installer.
  2. Manually copy and adjust your 9.x configurations into the directories and files that the automated installer created.
Note
: To upgrade an EPAgent, install the new version and copy any configurations manually to the new installation.
Manual Configuration File Upgrade Overview
The following table blow lists the Enterprise Manager files and properties that you need to copy or move to the 9.x files:
File and location, relative to
<EM_Home>
Description
config/Analytics.properties
Prior to upgrade, back up your existing property file.
Upgrade to the new version.
Manually edit the new Analytics.properties file to reflect your previous file values.
config/CustomDBRecordTypes.properties
Copy these files over to the new installation directory, to replace the newly installed versions.
config/agentclusters.xml
Copy these files over to the new installation directory, to replace the newly installed versions.
config/alert-blackout.xml
Copy these files over to the new installation directory, to replace the newly installed versions.
config/domains.xml
Copy these files over to the new installation directory, to replace the newly installed versions.
config/em-jetty-config.xml
Note
: The Jetty configuration files are not updated during the upgrade. Your customizations are retained and they might include unsecured plain text passwords. Be sure to change and secure all passwords. For more information to secure passwords, see the Jetty Documentation Wiki.
Copy these files over to the new installation directory, to replace the newly installed versions.
config/loadbalancing.xml
Copy these files over to the new installation directory, to replace the newly installed versions.
config/server.xml
Copy these files over to the new installation directory, to replace the newly installed versions.
config/webview-jetty-config.xml
Note
: The Jetty configuration files are not updated during the upgrade. Your customizations are retained and they might include unsecured plain text passwords. Be sure to change and secure all passwords. For more information to secure passwords, see the Jetty Documentation Wiki.
Copy these files over to the new installation directory, to replace the newly installed versions.
config/realms.xml
Copy these files over to the new installation directory, to replace the newly installed versions.
config/ResourceMetricMap.properties
Copy these files over to the new installation directory, to replace the newly installed versions.
config/users.xml
Note
: You may need to add CA CEM user and groups definitions to this file to connect to CA CEM. For details, see the
CA APM Security Guide.
Copy these files over to the new installation directory, to replace the newly installed versions.
c
onfig/IntroscopeEnterpriseManager.properties
Copy any customized properties, except for the specified single property and any customized absolute paths.
Handle the following property specially:
introscope.enterprisemanager.webserver.dir
For details, see Upgrading IntroscopeEnterpriseManager.properties.
config/shutoff/
Copy the directory to the new installation, replacing the newly installed version.
Introscope_Enterprise_Manager.lax
Copy any customized properties, except for the specified list of properties. For details, see Upgrading Introscope_Enterprise_Manager.lax.
EMService.conf
Note
: This file has changed location in 9.x. It is now in
<EM_home>
\bin.
Copy any customized properties, except for the specified list of properties. For details, see Upgrading EMService.conf.
product/enterprisemanager/configuration/.settings/users.prefs
Copy the file over to the new installation directory, to replace the newly installed version.
runem.sh
This file is shipped only by .JAR installers (which do not bundle JVMs). During an upgrade, the file is backed up to backup/iscXx and then replaced. The old settings are not preserved.
You must customize the new file with the appropriate JAVA_HOME and any other custom settings.
These Enterprise Manager clamp properties in the IntroscopeEnterpriseManager.properties file:
introscope.enterprisemanager.agent.connection.limit
introscope.enterprisemanager.agent.error.limit
introscope.enterprisemanager.agent.metrics.limit
introscope.enterprisemanager.agent.trace.limit
introscope.enterprisemanager.metrics.live.limit
introscope.enterprisemanager.events.limit
introscope.enterprisemanager.metrics.historical.limit
introscope.enterprisemanager.transactionevents.storage.max.disk.usage
Move the clamp properties to the <
EM_Home
>/config/apm-events-thresholds.xml file.
These CA CEM clamp properties in the tess-defaults.properties file:
maxNumberDomainConfigurationChanges
Autogen.Max.NonIdentifying.Components
maxUserGroups
maxUserRows
Move the clamp properties to the <
EM_Home
>/config/apm-events-thresholds.xml file.
Rename the properties as follows:
maxNumberDomainConfigurationChanges as introscope.enterprisemanager.max.number.domain.configuration.changes
Autogen.Max.NonIdentifying.Components as introscope.enterprisemanager.transaction.discovery.max.nonidentifying.components
maxUserGroups as introscope.enterprisemanager.max.transaction.user.groups
maxUserRows as introscope.enterprisemanager.max.application.user.rows
The following table lists the WebView files that you need to either copy over, or have properties in them moved over to the new 9.x files:
File and location, relative to
<EM_Home>
Description
config/IntroscopeWebView.properties
Copy any customized properties over into the newly installed file.
WVService.conf
Note
: This file has changed location in 9.x. It is now in
<EM_home>
\bin
.
Copy any customized properties, except for the specified list of properties. For details, see Upgrading WVService.conf.
Introscope_WebView.lax
Copy any customized properties, except for the specified list of properties. For details, see Upgrading Introscope_WebView.lax.
Introscope_ProbeBuilder_Wizard.lax
Copy any customized properties, except for the specified list of properties. For details, see Upgrading Introscope_ProbeBuilder_Wizard.lax.
Introscope_WebView
The WebView executable file.
The following EPAgent file must be either copied over, or have properties in them moved over to the new 9.x file: IntroscopeEPAgent.properties.
Upgrade the Enterprise Manager Manually
Follow these instructions to manually upgrade the Enterprise Manager (EM). The instructions will be divided according to files/folders in your Enterprise Manager installation.
Upgrade IntroscopeEnterpriseManager.properties
The following properties require special handling. All other customized property values can be manually copied to the newly installed IntroscopeEnterpriseManager.properties file as is.
  • If the introscope.enterprisemanager.webserver.dir property is configured to a value other than webapps, then:
    • Transfer the property to the IntroscopeEnterpriseManager.properties file in the new 9.x installation.
    • Manually copy all newly installed 9.x web applications from <
      EM_Home
      >/webapps to the custom directory.
  • If you renamed your Introscope directory and your property files used absolute paths to reference files in the Introscope directory, then update these paths manually. CA Technologies recommends using relative paths to refer to any file inside the Introscope root directory.
Upgrading EMService.conf
This file has changed location in 9.x. EMService.conf is now in
<EM_home>\bin.
In previous versions, it was in
<EM_home>
.
Do not transfer the following properties to the newly installed EMService.conf file. The default settings in the new installation should be used instead:
  • wrapper.java.command
  • wrapper.app.parameter.*
  • wrapper.java.classpath.*
  • wrapper.native_library.*
You can transfer all other customized property values from the old file to the newly installed version.
Upgrading Introscope_Enterprise_Manager.lax
Do not transfer the following properties to the newly installed Introscope_Enterprise_Manager.lax file:
  • lax.class.path
  • lax.version
  • lax.main.class
  • lax.command.line.args
  • lax.nl.valid.vm.list
  • lax.nl.message.vm.not.loaded
You can transfer all other customized property values from the old file to the newly installed version.
Manually Upgrading WebView
Follow these instructions to manually upgrade WebView. The instructions will be divided according to files/folders in your installation.
Upgrading IntroscopeWebView.properties
All customized property values in the IntroscopeWebView.properties file can be transferred to the new 9.x version of the file as is.
Upgrading WVService.conf
Do not transfer the following properties to the newly installed WVService.conf file:
  • wrapper.java.command
  • wrapper.app.parameter.*
  • wrapper.java.classpath.*
You can transfer all other customized property values from the old file to the newly installed version.
Upgrading Introscope_WebView.lax
Do not transfer the following properties to the newly installed Introscope_WebView.lax file:
  • lax.class.path
  • lax.version
  • lax.main.class
  • lax.command.line.args
  • lax.nl.valid.vm.list
  • lax.nl.message.vm.not.loaded
You can transfer all other customized property values from the old file to the newly installed version.
Upgrading Introscope_ProbeBuilder_Wizard.lax
Do not transfer the following properties to the newly installed Introscope_ProbeBuilder_Wizard.lax file:
  • lax.class.path
  • lax.version
  • lax.main.class
  • lax.command.line.args
  • lax.nl.valid.vm.list
  • lax.nl.message.vm.not.loaded
You can transfer all other customized property values from the old file to the newly installed version.
Complete the Enterprise Manager Manual Upgrade
Note
: CA APM 8.x is not supported.
To complete the manual upgrade, manually copy certain files from the old Enterprise Manager instance to the new one.
Follow these steps:
  1. Manually copy these components from the previous Enterprise Manager instance to the new Enterprise Manager instance:
    • all customized management modules
    • any custom extensions
    • any custom documents
  2. Manually copy the data or log files you want to retain from the previous Enterprise Manager instance to the new Enterprise Manager instance. The following list has suggestions for files you may want to retain.
    • Enterprise Manager (EM)
      data/*
      traces/*
      perflog.txt
      querylog.txt
    • Enterprise Manager or WebView
      any custom SSL key files
      logs/*.LOG
    • ProbeBuilder
      any custom .PBD files (See Completing the upgrade regarding post-upgrade tasks for .PBD files.)
      any customized system .PBD files
    • EPAgent
      any customized EPAgent files
    To keep data or log files from the old Enterprise Manager instance, manually copy them to the new Enterprise Manager instance.
    If a data file is in a shared directory (for example, \\mySAN\data) you do not need to move the file. Instead, edit the new installation’s IntroscopeEnterpriseManager.properties file to point to the shared location.
  3. If the following SNMP plugin JAR files exist in the <EM_Home>/ext directory, remove them:
    SNMPAlertActionEM.jar
    SNMPAlertActionWS.jar
For support with customizations to PBDs, EPAgent scripts, or JavaScript calculators, contact CA Technologies Professional Services.