Upgrade > Upgrade the applications from a version earlier than 9.60 > Upgrade tasks on the development environment > Step 15: Build a custom upgrade

Step 15: Build a custom upgrade

If you have followed all the steps to this point, you have already run the upgrade against the duplicate system you created of your production system, and you have performed reconciliation for that system. This section describes how to build a custom upgrade, which is then applied to your test system and production system.

To build the custom upgrade, follow these steps:

  1. Log on to the reconciled development system.
  2. Before you begin to build the custom upgrade, you need to back up (or duplicate) the production system. For information on duplicating your system, see Step 1: Duplicate the production environment.

  3. (Optional) You may need to exclude certain records on the production system from being built to the custom upgrade package. To do so, follow these steps:

    1. Click Tailoring > Differential Upgrade > Patch Records to open the Patch Maintenance page.
    2. Select SM96 from the drop-down list, and then press Enter.
    3. You can update the query definition as required. To remove an entry, clear the Dbdict field, the Add Only check box, and its corresponding query.
    4. Save your changes.

  4. Create a folder for the custom upgrade on the Service Manager server. You can assign any name you like to this folder. However, for documentation purposes, this folder will be referred to as the CustomUpgrade folder. Ensure that the CustomUpgrade folder is empty.

    Note If you are connecting to the Service Manager server from a client that is installed on a remote client computer, make sure that the folder is created on the Service Manager server instead of the client computer.

  5. From the System Navigator, click System Administration > Ongoing Maintenance > Upgrade Utility > Create Custom Upgrade.

  6. The Upgrade Utility automatically checks for duplicate records prefixed with "PRE", "NEW" or "OLD".

  7. The system displays the patch file name and all the supported languages that are installed on your Service Manager system. Review these information, and then click Next.

  8. Type a name for the custom upgrade package in the The name of this release field. For example, SM960.

  9. Type the fully-qualified path to the folder where the Upgrade Utility should create files in the The path to export the upgrade files field. This should be the path to the empty CustomUpgrade folder that you created in step 3. For example, C:\MicroFocus\ServiceManager\CustomUpgrade.

    Note You must have read, write, and execute permission to the folder.

  10. Click Next.
  11. The system displays Service Manager Upgrade Builder is now ready to build the upgrade. Click Next to continue.
  12. When you receive a "Finished creating the transfer files for the upgrade" message, the Upgrade Utility has finished the data packaging.

Upgrade Utility logs and error messages

When building the custom upgrade, the Upgrade Utility creates a set of log files, which reside in the same directory as the upgrade files. The following table describes the contents of the log files during this step.

List of upgrade logs
Log file Contents
detail.log

This file contains specific information about the upgrade, including the following:

  • All information in transfer.log and upgrade.log
  • Name of the file being purged. For example, “2017-09-20 13:58:32 dbdict: upgradestatus is purged.”
  • Progress of signature creation. For example, “2017-09-20 14:47:36 Created 100 signatures for Object on version SM960”
  • Building distribution information. For example, “2017-09-20 14:55:07 Building Distribution object for Applications Cluster Action.run”
transfer.log

This file contains information about the object being transferred by the upgrade. For example, “2017-09-20 15:12:27 Initiating an export of scmessage on query "((class="error" and message.id isin {"10"})) and syslanguage~="xxx""”

upgrade.log

This file contains information about where the upgrade is at any point, including the following:

  • Starting and ending of each sub-phase. For example, “2017-09-20 14:47:32 **** Start Phase [Pre Create Action Check] ****”
  • Main activities during each sub-phase. For example, “2017-09-20 14:47:35 Signaturing records.”
  • Name of the file being exported. For example, “2017-09-20 15:11:37 Exporting: table = Object query = 'true'”