This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Creating overlays with the Best Practice Conversion Utility

The Best Practice Conversion Utility (BPCU) helps preserve customizations when upgrading. The utility converts objects in earlier versions of BMC Remedy AR System components and applications as follows:

  • BMC objects that you modified (customizations) are converted to overlays.
  • User-created objects that you added to your setup (extensions) are converted to custom objects.

BPCU enables you to analyze objects in your current environment with the out-of-the-box objects in 7.6.04 and higher, and convert them into overlays or custom objects.

BPCU does not save customizations to objects that are not meant to be customized and that can be replaced during an application installation or during the normal process of running an application. These are referred to as non-permitted customizations (that is, customizations that are not permitted in overlays).

BPCU operates in the following modes:

  • ReportDiff – Generates a report of differences between the objects in an overlay hash file and the objects on a server. See Using BPCU to generate difference reports.
  • Overlay – Based on a differences report, converts customized AR System objects into overlays, and converts user-created objects into custom objects.

Before upgrading applications or creating overlays, use BPCU to determine which objects have been modified in ways that are not permitted in overlays.

The following table lists the BMC products in which the BPCU preserves customizations and the related exceptions.

Customizations preserved by BPCU

{table:border=1} {tr:align=center} {td:valign=top|}{*}BMC products{*}{td} {td:valign=top|}{*}Exceptions{*}{td} {tr} {tr} {td:valign=top|colspan=2|}{*}AR System components* {td} {tr} {tr} {td:valign=top|}BMC Remedy Approval Server {td} {td:valign=top|}Filters that BMC Remedy Approval Server workflow creates at runtime, whose names begin with *AP:Notify-0* {td} {tr} {tr} {td:valign=top|}BMC Remedy Assignment Engine {td} {td:valign=top|}None {td} {tr} {tr} {td:valign=top|}BMC Remedy Email Engine {td} {td:valign=top|}None {td} {tr} {tr} {td:valign=top|}AREA LDAP plug-ins {td} {td:valign=top|}None {td} {tr} {tr} {td:valign=top|}ARDBC LDAP plug-ins {td} {td:valign=top|}None {td} {tr} {tr} {td:valign=top|colspan=2|}{*}BMC Atrium CMDB* {td} {tr} {tr} {td:valign=top|}BMC Atrium CMDB {td} {td:valign=top|}The BMC Atrium CMDB upgrade program takes care of preserving customizations made to forms and workflow objects. BPCU ignores the following forms and their related workflow objects and workflow guides: Forms that belong to the BMC:Atrium CMDB application Forms that do not belong to the BMC:Atrium CMDB application, but whose names are listed in the OBJSTR:Class form (*:* ) {td} {tr} {tr} {td:valign=top|colspan=2|}{*}AR System applications* {td} {tr} {tr} {td:valign=top|}BMC Remedy ITSM Suite {td} {td:valign=top|}Application forms that use BMC Atrium CMDB forms as self-join forms (MemberA and MemberB are the same) {td} {tr} {tr} {td:valign=top|}BMC Service Level Management {td} {td:valign=top|}Filters with the *zSLMGen:* prefix that BMC Service Level Management workflow creates at runtime Forms that BMC Service Level Management creates at runtime, whose names end with *\_SLA*, and their related workflow objects and workflow guides {td} {tr} {tr} {td:valign=top|}BMC Service Request Management {td} {td:valign=top|}Filters with the *zAPR* prefix that BMC Service Level Management workflow creates at runtime {td} {tr}{table}

Warning

The utility does not preserve customizations to forms and workflows installed with the AR System server unless customizations are present when the utility is run.

You should upgrade to the current release of BMC Remedy AR System before running BPCU. This upgrade replaces the system forms, so reapply the customizations to system forms before running BPCU.

Related topics

Where to go from here

Setting BMC Migrator options before migration

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.

Comments