Stage 6 - Minimize overlays (optional)
In stage 6, you can minimize the number of overlays. You should remove all overlays that are the same as the object that they overlay, and all overlays that contain changes that are no longer needed. This reduces the number of customizations that must be maintained during future application upgrades.
Overlays that are identical to their overlaid objects might exist if you converted any prefixed or suffixed objects in stage 3.
If you restored the origin objects to StagingServer (Stage 5), you can compare your overlay to the origin objects.
This figure shows the removal of an unneeded overlay, item 7. Note that removal of the overlay exposes the origin object.
- If you performed the tasks in stage 5, use BMC Remedy Migrator to compare overlaid object to their overlays directly on StagingServer, and then delete the objects that are identical.
If you did not perform the steps in stage 5, then the overlays and overlaid objects on StagingServer are identical, except for those that previously had prefixes or suffixes. Set Migrator difference mask options, and use BMC Remedy Migrator to compare the overlaid objects on StagingServer to the same objects on ReferenceServer. If they are identical, you can remove the overlay on StagingServer.
When removing overlays, be careful of workflow objects. Disabled workflow objects are not identical to enabled ones, even if all other aspects are the same.
- If you have overlays that are not identical to the origin object but that contain changes that you no longer want to keep, delete those overlay objects.
Comparing overlays to overlaid objects on the same server to learn about Migrator difference mask options