Migrate CA APM Release 11.3.4 to the Current Release
To migrate CA APM data, perform these steps:
To migrate CA APM data, perform these steps:
As a system administrator, you perform the data migration when you want to move CA APM data from Release 11.3.4 to the current release . After you install the current release of CA APM, the CA Management Database (CA MDB) structures are upgraded and you are prompted to migrate your data.
Use the current release of CA APM to migrate objects that were not migrated with Release 14.1. These objects are costs and payments extensions and audits, custom relationships and audits, and relationship extensions and audits. With this release, all relationships are migrated, including custom relationships and relationships that were not product-provided. If you previously migrated your data from Release 11.3.4, you can migrate the data for just these objects. You do not need to perform the complete data migration again.
Installing the upgrade and migrating your data are separate processes:
- Upgrade: Updates the application and database structures to a newer version.
- Migrate. Transforms or moves the data from previous database structures to new database structures, which were created during the upgrade.
The CA APM Migration Toolkit contains the following tools to assist you with migrating your data from Release 11.3.4 database structures to the current release database structures:
- Migration Documentation: Provides the instructions for generating the migration reports, running the Migration Utility, and manually migrating objects.
- Migration Reporting: Generates reports that help you during the migration process. Generate the pre-migration reportsbeforeyou run the Migration Utility to avoid potential problems during the migration. You can generate the post-migration reportsafteryou run the Migration Utility. The post-migration reports help you manually migrate legacy database structures that cannot be migrated using the Migration Utility.
- Duplicate Asset Name Configurator: Specifies the renaming configuration to apply to duplicate Asset Names.
- Migration Utility: Provides automated steps to move the selected objects in your legacy database structures to new database structures.
The following diagram illustrates how a system administrator migrates data.
Example: Migrate CA APM Data from Release 11.3.4 to Current Release
Miriam is the CA APM system administrator at Document Management Company. She wants to upgrade CA APM Release 11.3.4 to the current release and migrate the data from legacy data structures to the upgraded data structures. Miriam reviews the prerequisites to start the migration and upgrades to the new release.
Miriam starts the CA APM Migration Toolkit. First, she generates and reviews the pre-migration reports. The reports help identify objects that she has to correct in the legacy data structures before successfully running the Migration Utility. She sets some of the reports aside to use later to configure new names for assets that have the same name and to perform manual migrations.
After Miriam makes the corrections to the legacy data structures, she reviews the Duplicate Asset Name Report to identify non-unique Asset Names. Miriam opens the Duplicate Asset Name Configurator and selects a renaming configuration for duplicate Asset Names. These assets are renamed when Miriam runs the Migration Utility.
Miriam opens the Migration Utility. She tests the database connection, which confirms that the correct CA APM legacy database version is being migrated to the correct new release database version.
Miriam selects the objects to migrate and runs the Migration Utility. She monitors the migration process by reading the progress and status messages. When all of the objects are migrated, the Audit History object becomes available for migration. She selects the Audit History object and reruns the Migration Utility.
When the Migration Utility process finishes, Miriam generates the post-migration reports. The reports specify the data that was successfully migrated and the data that was not migrated. Miriam has to migrate manually the data that was not migrated.
Manual migrations are performed using the upgraded CA APM current release web interface. Miriam starts the web interface. She performs the manual migrations using the post-migration report information. She verifies the migrated data to complete the migration process.