Learn how to upgrade CA APM to the current version.
Upgrade earlier supported versions of CA APM or Introscope to the latest CA APM version to obtain maximum monitoring performance with reduced overhead. The first steps of the upgrade process are to assess your monitoring requirements and resize the APM deployment to meet your needs. Properly size your APM deployment as your business needs change.
Use one of three upgrade methods. The interactive upgrade provides a graphical user interface (GUI) to guide you through the process. The difference between using the GUI and console is minimal and depends primarily on your OS and your familiarity with each method. Experienced users can use the console method. The silent method lets you create scripts that you can use multiple times to automate the upgrade.
Use the interactive upgrade method to upgrade all your components when you are unfamiliar with the process. Interactive upgrade uses the APM installer wizard. The wizard shows the default settings and prompts you to provide settings and parameters. The advantages of the interactive upgrade are as follows:
- Likelier to achieve a successful installation.
- Easier to use in a Windows environment.
- Provides a GUI with menu options, including default settings, that you can change.
- Speeds the process and provides you with choices when installing components.
Use the console to upgrade components when you are familiar with the components and the process. You must provide all the correct settings and parameters. Any unspecified settings use the default values. The advantages of the console upgrade are as follows:
- Easier in a Linux or UNIX environment.
- Follows a workflow.
- Avoids the overhead with UNIX that is present when using the Interactive Upgrade.
- Provides all options, including default settings, that you can change.
Use the silent upgrade when you want to use a script. Use this method only if you are familiar with APM and you know the settings to apply to the upgraded components. You can schedule the scripts to run the upgrade when traffic is at its lowest. Silent upgrade requires you to specify the settings and defaults in the response file and verify the results in the install log. For more information about the upgrade commands in the response file, see Install APM in Silent Mode. The advantages of the silent upgrade are as follows:
- Allows you to run the script multiple times.
- Allows you to use one script for all upgrade tasks.
- Enables you to schedule the script to run during off-peak hours.
All monitoring components in an APM solution are based on Enterprise Managers. Enterprise Managers in a standalone or cluster configuration must run on the same version of the Enterprise Manager software. Upgrade Enterprise Managers individually to complete the upgrade process. You can upgrade Enterprise Managers in parallel. During Enterprise Manager upgrade, your monitoring solution is inactive and you cannot collect monitoring data.
To upgrade your Enterprise Managers, download and run the APM installer on each Enterprise Manager server. The installer identifies the existing Enterprise Manager and offers you the option to upgrade the Enterprise Manager. During the upgrade, the installer upgrades the Enterprise Manager files and transfers your existing settings and customizations. After the Enterprise Manager is upgraded, restart the server. The other components in the monitoring environment reconnect to Enterprise Manager. When all components are connected, Enterprise Manager begins collecting data.
During the upgrade, the APM installer performs the following tasks:
- Creates a backup of the CA APM configuration and Enterprise Manager.
- Replaces all Introscope program files.
- Leaves intact all SmartStor data and log files.
- Logs customizations to<EM_HOME>/installfile.
- Upgrades or overwrites configuration files and startup scripts.
- Performs the upgrade tasks.
After the upgrade, the APM installer performs the following tasks:
- Moves obsolete files to<EM_Home>/backup/<iscXx>.
- Logs customizations that were not carried forward after the upgrade. The logs are stored in<EM_HOME>/install.