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.

Stage 3 - Upgrade applications and adjust customizations with overlays present

When you upgrade applications or system components, some objects that you have overlaid might be deleted, which means that your overlay is deleted as well. To preserve any such overlays, you must create a copy of your current staging server. This copy is called the upgrade comparison server (UpgradeComparisonServer).

Similarly, some of your customizations might interfere with upgraded behavior. You must adjust these customizations before using the application.

This figure shows the components that are upgraded in stage 3 (in green).

Stages3and7

To upgrade applications and adjust customizations

  1. Create an upgrade comparison server (UpgradeComparisonServer).
    1. On the system that you are going to use as the upgrade comparison server, install BMC Remedy AR System.
    2. Create a copy of the StagingServer database, which is already at the latest version.
    3. Restore the copy of the StagingServer database over the existing database on UpgradeComparisonServer.
  2. On StagingServer, upgrade the applications (BMC Atrium CMDB, BMC Remedy ITSM, and so on).
    This might modify and possibly delete some of your overlaid objects. Modifications to these objects performed by the upgrade do not affect your overlays and custom objects, but deletions do.

    Tip

    Use the Microsoft Excel planning spreadsheet to help you installing these BMC products.

  3. Review the upgraded functionality, and restore deleted objects (if necessary).
    Normally, an overlay that is deleted should not be replaced by a custom object because it will not be used by the upgraded application. If you have overlaid objects you want to preserve, you can save them as custom objects. If any of your customizations were deleted during the upgrade of StagingServer, use Developer Studio to restore them by creating custom objects on StagingServer by using the overlays still present on UpgradeComparisonServer.

    Note

    A custom field on a deleted form is not preserved because there is no form to contain the field.

    Perform steps a and b below to create custom objects for any overlaid objects that were deleted during the upgrade but that you want to preserve.
    1. Compare the overlaid objects on StagingServer against the same objects on UpgradeComparisonServer.

      Note

      Ensure that you have set your BMC Remedy Migrator configuration options before performing the following procedures.

      1. In BMC Remedy Migrator, choose Tools > Options.
      2. In the BMC Remedy Migrator Options dialog box, expand Differences and select Display.
      3. Select the Display all missing objects option, and make sure that all the other options are deselected.
      4. Open a new server window for StagingServer.
      5. In the navigation pane, click StagingServer to list all the objects on this server.
      6. Sort the object list on the Customization Type column, and select all objects with the value Overlay or Custom.
      7. Right-click and select Differences > UpgradeComparisonServer.
        BMC Remedy Migrator generates a difference report.
    2. For every overlaid object that exists on UpgradeComparisonServer, but not on StagingServer, decide whether you need the object. If you need it, use BMC Remedy Developer Studio to duplicate the overlay manually by saving it as a custom object on StagingServer.
  4. If you have overlaid objects that were changed during the upgrade, examine your overlays and add the functionality that was added to the overlaid objects, or remove overlays containing customizations that you no longer want.
    Removing an overlay exposes the upgraded object's functionality. To examine the overlays, compare each upgraded origin object that is overlaid on StagingServer to the same origin object on UpgradeComparisonServer, and compare each overlay and its overlaid origin object. You can then adjust the overlay to achieve the behavior that you want.
    Perform the needed comparisons as follows:
    1. Enable the required masking options.
    2. Use BMC Remedy Migrator to compare overlaid objects on StagingServer and UpgradeComparisonServer to identify which objects were changed and what changes BMC made between the versions, as follows:
      1. Open a new server window for StagingServer.
      2. In the navigation pane, click StagingServer to display all the objects on this server.
      3. Sort the object list on the Customization Type column, and select all objects with the value Overlaid.
      4. Right-click and select Differences > UpgradeComparisonServer.
        BMC Remedy Migrator generates a differences report.
        The differences report provides a list of objects that have changed.
    3. Keep this first instance of BMC Remedy Migrator open to examine objects in this report.
    4. Use a second instance of BMC Remedy Migrator to compare overlays to overlaid objects on UpgradeComparisonServer:

      Note

      You need to have BMC Remedy Migrator installed on a different computer to do this because you can only run one instance of Migrator on a single system.

      1. Open a new instance of BMC Remedy Migrator.
      2. Open a new server window for UpgradeComparisonServer.
      3. In the navigation pane, click nameOfUpgradeComparisonServer to display all the objects on this server.
      4. Sort the object list on the Customization Type column and select objects (in the previously created list) with the value Overlay in this column.
      5. Right-click and choose Differences > UpgradeComparisonServer.
      6. In the Source-Destination Mapping window, click Map Overlay To Base to populate the Destination Object Name column with the corresponding overlaid object for each overlay object.
      7. Click OK to generate the difference report.
    5. For each object in the difference report from step 4b, use the first Migrator instance to identify differences resulting from the upgrade. Use the second instance to see differences between the overlay and the overlaid object.
    6. Based on these differences, use BMC Remedy Developer Studio to delete the overlay or modify it on StagingServer:
      • If you want to use the new features in the latest release, delete the overlay.
      • If you want to retain the customizations in your current production system when you upgrade to the latest release, merge the differences from the origin object into its overlay.

Related topics

Where to go from here

Stage 4 - Test and promote staging server (with overlays) to production

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

  1. Dirk Reuter

    Hi,

    Would you please be so kind as to clarify the sentence in 4.a.:

    "Enable the required masking options if you have not already done so in stage 4."

    How should I have done this already in stage 4 when I am still in Stage 3?

    Thank you in advance.

    Cheers,

    Dirk

    Oct 09, 2014 05:31
    1. Hemant Baliwala

      Hi Dirk, 

      Thanks for your comment.

      This sentence is valid, if you are upgrading from a non-overlay environment. I have updated the sentence to make it more generic.

      -Hemant

       

      Oct 09, 2014 05:50
  2. Mike Brandenburg

    Hi,

    I have a question regarding Step 4a "Enable the required masking options."

    Which masking options we need to enable to continue with step b

    "Use BMC Remedy Migrator to compare overlaid objects on StagingServer and UpgradeComparisonServer to identify which objects were changed and what changes BMC made between the versions, as follows: "

    Thank you in advance

    Mike

    Oct 13, 2014 03:42