Upgrade tasks on the test environment

Step 1: Apply the custom upgrade to the test environment

You need to apply the newly-created custom upgrade to your test system for user acceptance testing.

To upgrade the custom upgrade, follow these steps:

1. On the test system, which is a copy of your production system, complete all the preparation tasks in Upgrade tasks on the development environment.

2. Load the preupg.bin file using Service Manager Database Manager, and then restart the client.

   Note Instead of using the file that you extracted from the product installation package, you must use the preupg.bin file in your CustomUpgrade folder.

   Note The AppUpgVersion.txt file does not exist in the CustomUpgrade folder. Do not copy the file to this folder.

   Caution Before loading these files, you also need to disable the Client side load/unload option from Window > Preferences > Service Manager.

3. From the System Navigator, click System Administration > Ongoing Maintenance > Upgrade Utility > Apply Upgrade to launch the Upgrade Utility.

4. In the text box, type the fully qualified path to the CustomUpgrade folder, and then click Next.

   Note Instead of using the file that you extracted from the product installation package, you must use your CustomUpgrade folder.

   Example:

   Windows: c:\temp\upgrade\

   Linux: ~/upgrade/

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

5. The loading process may take a long time. Wait until the file is loaded and the system displays the Transfer files loaded message.

6. The system displays a series of information for your verification, including Applications version upgrading from, Applications version upgrading to, Applications base version, Full path to the Upgrade Utility files and Language(s) to be upgraded. Verify these information and then click Next to continue.

   Note If this screen does not display the correct information, do not continue with the upgrade. Instead contact Micro Focus Software Customer Support.

7. When you are asked whether you want to proceed, click Yes.
8. The Upgrade Utility displays the status when the upgrade is being processed.

9. When you receive an "UPGRADE IS COMPLETE" message, the Upgrade Utility has finished the data processing and you can follow the instructions in the message to complete the next steps. After you click Finish, you are automatically logged out.

10. Restart the server and log back in to the client.
11. Open the scversion table in the Database Manager, and verify that the Application Version field is 9.61.00xx. If this field displays a value other than 9.61.00xx, check the log files to identify the issue that occurred.

Note how long it takes to apply the custom upgrade, so you will know how long the production system will be unavailable during the production upgrade. You can check the log file for an estimate.

Upgrade Utility logs and error messages

When applying the custom upgrade to the test system, the Upgrade Utility creates a set of log files, which reside in the log directory.

The contents of these log files are similar to those in the log files when running an out-of-box upgrade. See Upgrade Utility logs and error messages.

Tables and records that are not upgraded by the Upgrade Utility

The Upgrade Utility does not automatically upgrade all tables and records. The patches record lists the tables and records that are packaged into the custom upgrade. Customizations made to any other tables or records will not be part of the custom upgrade. To make sure that the objects that you have reconciled are moved to the production system, verify the following scenarios:

• If an object is in the patches record, and the Result field of its related “upgraderesults" record displays “Already Current”, "Kept Customer” or “Kept Customer Non-OOB”, change the Result field to “Reconciled”.

  For example, follow these steps after you have modified the cm.open.display_newphase displayoption record:

  1. From the System Navigator, click System Administration > Ongoing Maintenance > Upgrade Utility > View/Merge Results.

  2. Type displayoption in the Object Type field, type cm.open.display_newphase in the Object Name field, and then click Search.

     Note Some object names consist of multiple key fields, you can find the definitions in the signaturemake record.

  3. If the Result field in the search results is “Already Current”, “Kept Customer”, “Kept Customer Non-OOB”, manually change the Result field to “Reconciled”
• If an object is in the patches record, and the Result field of its related “upgraderesults" record is not “Already Current”, "Kept Customer” or “Kept Customer Non-OOB”, no additional task is needed.

• If an object is not in the patches record, do one of the following:

  • Create an unload file containing those objects by adding them to an unload script or using the standard Service Manager Unload/Export Facility,
  • Make the same changes manually by directly modifying the objects on the production system. For records that you might have deleted, you can either build a purge script for those records or delete the records manually on the production system.

Resolve Process Designer related data

To resolve the Process Designer related data, follow these steps:

1. From the System Navigator, click System Administration > Ongoing Maintenance > Upgrade Utility > View/Merge Results.
2. Click the Expert Search button from the More Actions menu, type version.reconciled#"PD Enable" in the Query field, and then click Search.

3. In the search result, resolve the data by following the actions described in the table below.

   Reconciled Version	Result	Action
   PD Enable: Need to be removed	Any	Remove the objects manually.

Step 2: Perform additional manual tasks

This section lists changes that cannot be automated by the Upgrade Utility and changes that are required only for certain customers. Make these changes before testing and backing up your system. For detailed instructions, refer to Step 10: Perform additional manual tasks.

Step 3: Migrate Process Designer data

See Step11: Migrate Process Designer data for more information.

Step 4: Test the test environment

After you apply the custom upgrade on the test environment, perform user acceptance testing and load testing for all features, especially customized applications. Test the upgraded system with the new Service Manager client to verify any changes you have made in reconciliation. If the upgrade process has any problems, you need to contact Micro Focus Customer Support. After you complete testing of the upgraded system, you can use it to upgrade your production system.

To test the test environment, follow these steps:

1. Return the system to a normal operating environment.
2. Install and configure the Service Manager client for the target version (see instructions in Service Manager Installation).
3. Use the new Service Manager client to log on.
4. Review the features described in the Service Manager 9.61 Help Center.
5. Use the new Service Manager client to thoroughly test the upgraded system. Test all features that your users will access. Pay particular attention to areas that were modified on your system.