When upgrading from a version earlier than 7.6.04, to preserve your customizations for future upgrades, you must copy your existing customizations, including customizations to the BMC Remedy Action Request (AR) System server and all other applications and components, into overlays and custom objects.
You can create overlays using the Best Practice Conversion Utility (BPCU).
The following tables lists the different stages and the tasks you must perform to create overlays.
Stage 1: Set up the infrastructure
|1.||Set up the reference server||The reference server will have only unmodified origin objects from the BMC released software, with no customizations|
|2.||Proceed till the stage where you have restored the production database on the staging environment||Refer to the steps for upgrading from a version earlier than 7.6.04.|
Stage 2: Export system forms
|1.||Export system forms||Certain AR System server definitions might be lost or overwritten when you upgrade from earlier versions of AR System server (assuming that you select only AREA LDAP during installation). If you have modified any of these objects, save a copy and restore your changes after upgrading the server.|
Stage 3: Prepare to create overlays
|1.||Updates to the BPCU (BPCUFile_Master.zip) and the Overlay hash file (OverlayHashFile_Master.zip) between patch releases are posted to the BMC Communities.|
|2.||Configure your system for BPCU||Ensure that your CLASS path and Oracle Java Runtime Engine (JRE) are correctly configured to support the BPCU.|
|3.||Generate difference reports using BPCU||Run the BPCU in ReportDiff mode to compare objects between the overlay hash file and an AR System server, and generate difference reports.|
|4.||Fix nonpermitted modifications||It is assumed that modified objects are on StagingServer and unmodified origin objects of the same version are on ReferenceServer.|
Stage 4: Create overlays
|1.||Create overlays for modified legacy objects|
In Overlay mode, the BPCU compares objects in an overlay hash file with the objects on a server, generates a report of their differences, and performs the following tasks based on the contents of the report:
|2.||Review the BPCU log information||When the BPCU is first run on a server, it creates the BPCU-Log form. The form records information about each run of the utility, such as the run date, run mode, and return code. The form also stores the log file and the difference report that are associated with the run as attachments.|
Stage 5: Migrate base objects from reference server to staging server
|1.||Set BMC Migrator options before migration||You need to update the <migratorInstallDir>\Migrator Configuration.xml file.|
|2.||View differences between objects||The BPCU generates a differences report that identifies objects that differ from the origin objects. However, the differences are not described. In this step, you view the difference between objects.|
|3.||Acquire origin objects||You acquire unmodified origin objects and then compare them to the overlays on your server to see exactly what has changed in any object.|
|4.||Restore origin objects to the staging server||This step replaces the origin objects on the staging server with the unmodified origin objects from the reference server.|
Stage 6: Remove identical overlay objects
|1.||Minimize 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.|
|2.||Compare overlays to overlaid objects on the same server||Before comparing overlays to overlaid objects, you must set certain difference mask options in addition to the default mask options so that BMC Remedy Migrator only compares differences that affect the operation of your application.|
Stage 7: Complete other upgrades
|1.||Upgrade AR System server on the reference server||None|
Stage 8: Reconcile overlays on the staging server
|1.||View differences between objects|
Update overlays on the staging server for overlaid objects that were changed during the upgrades.
Stage 9: Proceed with the upgrade
|1.||Restore the upgraded database on other staging servers||The next stage in the upgrade process.|