Verify the application migration
In this article:
Important items to verify
After you perform all the migration steps and bring the application online, the final step is verifying the migration was performed successfully, using various tests. Obviously, the most reliable and thorough verification would be to exercise the destination system for a period of time, to see if any problems emerge. Note that these tests require you to create a report that contains all of your dimensions, models and associated items. These tests can be time consuming, depending on the size of your organization’s application data.
Recommended verification tests include the following tasks:
Using PerformancePoint Add-in for Excel, (see Microsoft TechNet article, PerformancePoint Add in for Excel for more information) perform these tasks:
Design a report containing all dimensions loaded. Note all dimensions for later verification.
Create a report for each model loaded. Note all models for later verification.
Verify that you can receive assignments Note all assignments for later verification.
Confirm that you can launch jobs and check the status for each job that runs. Note all jobs and the status for later verification.
Using Planning Business Modeler and the notes you took in previous steps, confirm this information on the source system:
Verify dimension and member set counts.
Verify measure group counts.
Verify associations in the table of contents and migrated associations in each site.
You should note this information before you start the migration process. If the source application is deployed correctly, this information should be accurate.
Using the Planning Administration Console, verify these tasks:
Verify that you can connect to the server.
Verify that you can open the migrated application for editing.
Verify that you can open the model sites for editing.
Confirm that the associations in your source application and target application have the same mappings.
Important items to verify
Dimension member properties and default values
After you have migrated application metadata, it is important to keep in mind that the migrated values will not be the same. Application migration does not migrate the Member ID. The Member ID on the source application will always be different than on the target application. The default value is stored by the referenced dimension’s MemberID. Keep in mind that the MemberID will almost always refer to a different member on the destination server. After migration of metadata and reloading all dimension data, use Planning Business Modeler to verify and update the default value for all member properties that refer to other dimensions.
The default value must be verified after every migration, as it will be migrated from the source system with each migration.
When migrating reference and fact data, the member property values that refer to other dimensions are migrated correctly if the dimensions are migrated based on their dependency order. For the default NONE member, the member property values that refer to other dimensions are not migrated. After migration of metadata and reloading all dimension data, use Planning Business Modeler to verify and update the values for member properties if required. The only time you will need to change the member properties is if you use ScoreCards with KPIs that are based on the MemberIDs. This changes the member properties and you will need to use Planning Business Modeler to manually change them. Otherwise, there is nothing wrong with the MemberIDs that have changed.
Data sources and data destinations are migrated during the application migration. However, the related databases are not migrated. After the migration process is complete, migrated data sources and data destinations should be verified in Planning Administration Console and new data destination databases must be created as required.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for PerformancePoint Planning Server.