Overview of the Approval upgrade utility
BMC Remedy Approval Server provides an approval upgrade utility that populates data for newer enhancements. This utility runs automatically as part of installation. However, if you apply an approval server patch by using the file replacement method, you need to run the approval upgrade utility manually. To run the approval upgrade utility manually, see Running the approval utilities.
Before running this utility, or before upgrading your approval server, you need to set the Max-Entries-Per-Query setting in the ar.cfg file to 0. If this is not done and you have more AP:Detail records than the size specified in the Max-Entries-Per-Query setting, not all records will be updated. The zero value defines this as no server defined maximum, so all records are updated.
The following table lists the fields whose values the approval upgrade utility populates when upgrading from an earlier release:
Fields populated by the approval upgrade utility
7.1.00 or later
7.5.00 or later
Full Name (ID 14201)
7.6.xx or later
Recent History Time (ID 14105)
|7.6.04 or later||AP:Form|
The syntax of the approval upgrade utility is as follows:
upgrade -d <ARSystemInstallDir> [-l <logFileDestinationPath>]
Approval server upgrade utility parameters
(mandatory) The location of the AR System installer. For example, C:\Program Files\BMC Software\ARSystem.
(optional) By default, the AR System suite installer places the approval-utils.log file in ARSystemServerInstallDir/approval/bin. If you run the approval upgrade utility manually, you can use this parameter to specify the name and location for the log file.
If the approval upgrade utility fails during installation or upgrade, run the utility manually. Then, you restart the approval server or wait for the cache to be refreshed for the changes to be visible. Even if the approval upgrade utility fails, no data is lost.