End-to-end tasks for in-place upgrade on a single server with overlays

When viewing the latest version of a product on the Electronic Product Download (EPD) site, you see only the components (including licensed add-ons) that are covered under the licenses associated with your Support ID or EPD profile.

Ensure that you download the latest service pack and patch.

Suspend all administrative operations until the upgrade is complete

This setting enables only administrators and sub-administrators to access BMC Remedy AR System. Users who are not administrators or sub-administrators cannot perform any BMC Remedy AR System operations. Administrator-Only mode is useful during system maintenance. By default, this option is not selected.Only administrators (not sub-administrators) can set Administrator-Only mode. After an administrator sets this option, sub-administrators can access only forms for which they have permission.

To check for differences between two sets of objects, use BMC Remedy Migrator. To examine the different objects to determine whether you will need to merge changes, use BMC Remedy Developer Studio.

To obtain a list of all of the overlay objects that were modified in the latest release, obtain the Snapshot utility (a Developer Studio plug-in). This unsupported utility is available on the BMC Developer Network.

All BMC Atrium Core versions have steps in common. You must comment out the entries in the armonitor and ar configuration files. Also, perform a complete health check of the AR System server and BMC Atrium CMDB.

This procedure installs BMC Atrium CMDB, Reconciliation Engine, and Normalization Engine.

You cannot install BMC Atrium CMDB on a remote AR System server; you must perform the installation on the computer on which BMC Remedy AR System is installed.

When you upgrade from version 7.5 or later, you must choose a new installation directory for the upgrade that is not below the BMC_AR_SYSTEM_HOME directory. 

• If you have installed the earlier version of BMC Atrium Core Web Services on a separate computer, upgrade BMC Atrium Core Web Services on that computer after you have upgraded BMC Atrium CMDB on the primary stack.
• If you have installed the earlier version of BMC Atrium Core Web Services on the same computer on which you have installed BMC Atrium CMDB, BMC Atrium Core Web Services is upgraded when you upgrade BMC Atrium CMDB.

For upgrade from 8.0 to 8.1: Before running the Atrium Integrator server installation program, set Max Attach Size in the AR System Server Information window to 0 MB or 100 MB. If Max Attach Size is set to a value other than 0 MB or 100 MB, the Atrium Integrator server installation does not complete.

For upgrade from 7.6.04 to 8.1: When you upgrade Atrium Integrator 7.6.04 to 8.1, a backup of your old jobs and transformations is created and saved to the ARSystem directory. The upgrade then proceeds like a fresh installation. The backup might complete or fail at times, depending on which you may need to perform additional tasks in case of failure.

Review this section if you are

Review this section if you are

This section provides information about the forms into which BMC Software loads new or modified data and about the ARX files.

As of BMC Remedy ITSM 7.6.04, the field deletion driver scripts have been changed and fields are now deleted using the Cascade option. This option not only deletes referenced fields but it also deletes all associated fields in all join forms.

If you customized the BMC Remedy IT Service Management suite,

before you start the upgrade

If you are using DB2,

• To install the update later, after the upgrade finishes (the installer gives this option if your environment has more than 20 million records)
• To run the multi-tenancy updates against the migrated delta data
• To restart the update utility, if data errors cause the utility to stop running (you must troubleshoot the data errors before restarting the update utility)

If you change the data set before installing or upgrading, you do not need to import the data manually.

The update to the multi-tenancy model is not supported if BMC Service Request Management is installed by itself as a stand-alone product or if BMC Service Request Management is installed on a mixed-version stack. 

The multi-tenancy update utility is integrated with the BMC Remedy IT Service Management suite and application installers. You can also start the multi-tenancy update utility manually in the following situations:

• To install the update later, after the upgrade finishes (the installer gives this option if your environment has more than 20 million records)
• To run the multi-tenancy updates against the migrated delta data
• To restart the update utility, if data errors cause the utility to stop running (you must troubleshoot the data errors before restarting the update utility)

When upgrading from BMC Service Request Management 7.6.04 to 8.1.00, you must reconcile the custom advanced interface form (AIF) workflows.

Importing data from BMC Service Request Management versions earlier than 7.6.03 directly into BMC Service Request Management 8.1.00 is not supported.

To export BMC Service Request Management data from versions earlier than 7.6.03, you must first upgrade the application to BMC Service Request Management 7.6.03 (or later). You can then export the data from that system and import it to a BMC Service Request Management 8.1.00 system.

Perform feature and functionality validation and performance testing

Perform any required changes based on issues found in testing

For known and corrected issues, see:

For troubleshooting tips, see:

For logging information, see:

For error message description, see:

For known and corrected issues, see:

and

For troubleshooting tips, see:

For logging information, see:

For error message descriptions, see:

For known and corrected issues, see:

For troubleshooting tips, see:

For logging information, see:

For error message descriptions, see:

For known and corrected issues, see:

For troubleshooting tips, see:

For logging information, see:

For known and corrected issues, see:

For troubleshooting tips, see:

For logging information, see: