Best Practice Conversion Utility
The following topics are provided:
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.
The 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.
The 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).
The 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 figure shows how the Best Practices Conversion Utility (BPCU) is used to create overlays and custom objects from your existing objects. If you customized a workflow by copying and disabling an application object, you need to run BPCU twice. Otherwise, you need to run it only once.
The figure depicts the following examples:
- The upper plane shows the overlay group, which contains overlays, custom objects, and origin objects that have not been overlaid.
- The lower plane shows the base group, which contains only origin objects.
- Object 1 is a customized version of workflow object 2, so object 1 is converted into an overlay of object 2.
- Because object 3 is a modified application object, object 7 (a new object), is created as an overlay of object 3.
- Object 6, which was created in the production environment is converted into a custom object.
BMC products in which the BPCU preserves customizations, and related exceptions
The following table lists the BMC products in which the BPCU preserves customizations, and related exceptions.
Customizations preserved by BPCU
|AR System components|
|BMC Remedy Approval Server||Filters that BMC Remedy Approval Server workflow creates at runtime, whose names begin withAP:Notify-0|
|BMC Remedy Assignment Engine||None|
|BMC Remedy Email Engine||None|
|AREA LDAP plug-ins||None|
|ARDBC LDAP plug-ins||None|
|BMC Atrium CMDB|
|BMC Atrium CMDB|
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:
|AR System applications|
|BMC Remedy ITSM Suite||Application forms that use BMC Atrium CMDB forms as self-join forms (MemberA and MemberB are the same)|
|BMC Service Level Management||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|
|BMC Service Request Management||Filters with the zAPR prefix that BMC Service Level Management workflow creates at runtime|
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.