This documentation applies to the 8.1 version of Remedy ITSM Deployment, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Creating overlays

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. 

 Click here to view the sequential list of the stages

Stage 1: Set up the infrastructure

StepActionAdditional information
1.Set up the reference serverThe 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 environmentRefer to the end-to-end steps.

Back to top

Stage 2: Export system forms

StepActionAdditional information
1.Export system formsCertain 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.

Back to top

Stage 3: Prepare to create overlays

StepActionAdditional information
1.Upgrade BMC Remedy AR System serverYou must install the AR System server on the staging server to obtain the BPCU.

Obtain the following items:

Updates to the BPCU ( and the Overlay hash file ( between patch releases are posted to the BMC Communities.
3.Configure your system for BPCUEnsure that your CLASS path and Oracle Java Runtime Engine (JRE) are correctly configured to support the BPCU.
4.Generate difference reports using BPCURun the BPCU in ReportDiff mode to compare objects between the overlay hash file and an AR System server, and generate difference reports.
5.Fix nonpermitted modificationsIt is assumed that modified objects are on StagingServer and unmodified origin objects of the same version are on ReferenceServer.

Back to top

Stage 4: Create overlays

StepActionAdditional information
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:

  • For permitted customizations, the BPCU generates an overlay by creating a copy of each object, and sets its Overlay property to Overlay.
  • For permitted extensions, the BPCU generates a custom object and sets the Overlay property to Custom.
2.Review the BPCU log informationWhen 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.

Back to top

Stage 5: Migrate base objects from reference server to staging server

StepActionAdditional information
1.Set BMC Migrator options before migrationYou need to update the <migratorInstallDir>\Migrator Configuration.xml file.
2.View differences between objectsThe 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 objectsYou 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 serverThis step replaces the origin objects on the staging server with the unmodified origin objects from the reference server

Back to top

Stage 6: Remove identical overlay objects

StepActionAdditional information
1.Minimize overlaysYou 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 serverBefore 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.

Back to top

Stage 7: Complete other upgrades

StepActionAdditional information
1.Upgrade AR System server on the reference serverNone

Upgrade remaining platform components and BMC Remedy ITSM suite applications on the staging server


Back to top

Stage 8: Reconcile overlays on the staging server

StepActionAdditional information
1.View differences between objects

Update overlays on the staging server for overlaid objects that were changed during the upgrades.

  1. Use BMC Remedy Migrator to compare overlaid objects on the staging and primary servers. Create a list of objects that were changed.
  2. Use one copy of BMC Remedy Migrator with this list to compare overlaid objectson the staging and primary servers.
  3. Use one copy of BMC Remedy Migrator with this list to compare overlays to overlaid objects on the reference server.
  4. Using differences in the copies of BMC Remedy Migrator, either delete the overlay or modify it on the staging server.

Back to top

Stage 9: Proceed with the upgrade

StepActionAdditional information
1.Restore the upgraded database on other staging serversThe next stage in the upgrade process.

Back to top

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.