Upgrade from Introscope
If you are upgrading either Introscope-only installations or CA APM, use this information.
apmdevops97
If you are upgrading either Introscope-only installations or CA APM, use this information.
Current and Target Installations
This table lists current and target installations.
Current installation | Target installation |
Introscope only | Introscope only (CA APM without TIMs) |
Introscope only | CA APM |
CA APM Introscope and CA CEM (integrated) | CA APM |
CA APM Introscope and CA CEM (non-integrated) | CA APM |
Other than the addition of the APM database, the rest of the Introscope upgrade is mostly similar to previous upgrades.
In most cases, you can automatically upgrade WebView with the Enterprise Manager. If a component was not installed simultaneously as the Enterprise Manager, manually upgrade that component.
For Workstations and EPAgents, install new ones. You cannot upgrade the prior versions. For any extensions that you want to use, you may have to do some manual configurations before the extensions are ready to use.
We recommended that you upgrade agents one at a time. This way, you can pinpoint errors to a specific agent if something goes wrong with the upgrade. This method can minimize production down time. If desired, you can wait to upgrade the agents, although you cannot access the new functionality.
Verify that the Enterprise Managers, Workstations, and agents run without errors. If you want to continue using Introscope only, you are ready.
Upgrading a Standalone Introscope Architecture Overview
If your current installation uses a standalone Enterprise Manager, the following diagram illustrates the essential parts of the installation. There are one or more agents connected to a single Enterprise Manager. The Introscope Workstation connects to the Enterprise Manager, and the Enterprise Manager contains the SmartStor database.

Post-Upgrade Standalone Introscope Architecture Overview
After the upgrade, the Introscope-only, standalone Enterprise Manager deployment has an architecture that looks like what is shown in the following diagram. The main difference is the addition of the APM database, which the Enterprise Manager connects to and uses for data storage. The CEM console is available as well, for use with agent recording.

Post-Upgrade CA APM from Standalone Introscope Architecture Overview
If you then choose to add the rest of CA APM functionality, the architecture looks like what is shown in the following diagram. There are now at least two Collector Enterprise Managers connecting to a MOM Enterprise Manager. The TIMs connect to one Collector, and the agents connect to a separate Collector. All Enterprise Managers connect to the APM database. There are some Enterprise Manager services that you distribute to Collectors. You use the CEM console to view CA CEM data by way of the MOM, and you use the Introscope Workstation to see Introscope data by way of the MOM. Each Enterprise Manager continues to have its own SmartStor database. The MOM Enterprise Manager connects to the CA Embedded Entitlements Manager, to manage user and group authentication and authorization.

Upgrading a Clustered Introscope Architecture Overview
If your current installation uses a cluster of Enterprise Managers, the following diagram illustrates the essential parts of the installation. There are one or more agents connected to one or more Collector Enterprise Managers. The Introscope Workstation connects to the Enterprise Manager, and each Enterprise Manager has its own SmartStor database.

Post-Upgrade Clustered Introscope Architecture Overview
After the upgrade, the Introscope-only, clustered Enterprise Manager deployment has an architecture that looks like what is shown in the following diagram. The main difference is the addition of the APM database, which each Enterprise Manager connects to and uses for data storage.

Post-Upgrade Clustered CA APM Architecture Overview
The following diagram illustrates how to integrate CA CEM with an upgraded, clustered Introscope, so that you have an integrated CA APM environment. In this diagram, there are two TIMs connected to one of the Collector Enterprise Managers, and the CEM Console is available from the MOM. Each Enterprise Manager has some Enterprise Manager services distributed on it. The Agents report to the other Collectors. The MOM Enterprise Manager connects to the CA Embedded Entitlements Manager, to manage user and group authentication and authorization.

Add CA CEM to an Upgraded Introscope
After you have upgraded and verified your Introscope installation, you can add CA CEM functionality to integrate the rest of CA APM.
Be sure that your Enterprise Manager and APM database computers meet the requirements for the additional load. Follow the instructions to do a new install of a TIM software. The following workflow table lists each step in more detail.
Step | Description | Task Details / More Information |
1 | Decide how many TIMs to install and onto which computers. Verify that the computers meet or exceed the minimum requirements. | For information related to architecture, sizing, and security, consult the following CA APM documentation: CA APM Sizing and Performance APM Security APM Administrating |
2 | Install and configure the TIMs for use with CA CEM. | |
3 | Redistribute services on Enterprise Managers. | Access the MOM to distribute the Enterprise Manager services appropriately. Note : If an Enterprise Manager is running on a computer with a 32-bit operating system, redistribute the Enterprise Manager Services so that the Stats Aggregation Service and TIM Collection Service are assigned to different Enterprise Managers. Assign the DB Cleanup Service to the Enterprise Manager that has the Stats Aggregation Service. |
4 | Perform post-install CA CEM configurations. | Perform specific post-install tasks, such as refining security permissions, verifying age-out and database settings. |