After the data migration is successfully completed, you must first back up the staging server database and then perform the post-migration steps explained in this section.
Before you begin
Because steps 1 and 2 of the following procedure uses Java, ensure that your JAVA_Home environment variable points to the JDK directory. For example, JAVA_HOME= C:\Program Files\Java\jdk1.8.0_45.
|1.||Update fields in forms for delta data||During the post-upgrade portion of the installation, fields in some forms are updated through a workflow triggered by the MSM:MigrationTasks form. To update the fields for the delta data, complete the described procedures and apply the listed packages to your destination server.|
|2.||Validate the migration||To validate the migration, run the AREntryCounter utility. Alternatively, you can run the SQL scripts that are available for all the products and versions supported by delta data migration.|
|If you are upgrading BMC Knowledge Management from a version prior to 7.6.04, run the BMC Knowledge Management Article Conversion Tool after every delta data migration or, at minimum, after the final delta data migration.|
|4.||Synchronize form IDs to the destination server||An escalation that runs every day cleans up the records in the ID generator forms. Consequently, the ticket number generator form IDs may not be properly synchronized to the destination server if not all of the described parent forms had data in the final production run of the delta data migration.|
|5.||Migrate modified service target or agreement after initial migration||For products included in the BMC Remedy IT Service Management (ITSM) Suite, including BMC Service Request Management and BMC Service Level Management, you might want to migrate a modified service target or agreement after the initial migration. Perform the described tasks before you begin the migration and after you complete the migration.|
If you have upgraded BMC Remedy ITSM Process Designer, then you must run the Update Permissions utility to rectify the migrated data as a post delta data migration activity.
|7.||Update the server names before moving the server to production||You must update the listed forms for fields with AR server name references to the destination server before using the production server.|
|8.||Delete orphan records after delta data migration||You cannot search orphan records by data because it is not possible to tell when a record was deleted. Perform the described procedure to delete the orphan records.|
|9.||Reset the changes you made prior to the delta data migration||None.|
Where to go from here
|Up to process|
When you have finished migrating delta data, return to the Remedy ITSM Suite staged upgrade process for cutover and go live activities.