Asset Health Manager Upgrade

Upgrade or Update Asset Health Manager to V5.2.1.0.0

The following table provides you the reference to procedures to upgrade from an earlier APM version to the latest version.

Upgrade from Upgrade to Procedure
V5.2.xV5.2.1.0.0
V5.1.xV5.2.1.0.0
V5.0.xV5.2.1.0.0
V4.6.2 or a later V4.6.x releaseV5.2.1.0.0
  1. Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0
  2. Upgrade from any version V5.0.1.0.0 through V5.0.6.0.0
V4.6.1.x or earlierV5.2.1.0.0
  1. Upgrade from any version V4.6.1.x or earlier to V4.6.2.0.0 or a later V4.6.x release
  2. Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0
  3. Upgrade from any version V5.0.1.0.0 through V5.0.6.0.0
Note: For more information on upgrading to APM V4.6.2.0.0 or a later V4.6.x release, refer to the Upgrade documentation for the corresponding version.

Upgrade from any version V5.2.0.0.0 through V5.2.0.1.0

This module will be upgraded to V5.2.1.0.0 automatically when you upgrade the components in the basic APM system architecture. No additional steps are required.

Upgrade from any version V5.1.0.0.0 through V5.1.3.1.0

The baseline query Health Overview - Status by Asset in the Public\Meridium\Modules\AHI\Queries catalog folder has been modified to enhance performance.

This query will be updated automatically when you upgrade the components in the basic APM system architecture. No additional steps are required. If you have modified the baseline query, then you will need to manually update the query to incorporate the changes.

Upgrade from any version V5.0.1.0.0 through V5.0.6.0.0

This module will be upgraded to V5.2.1.0.0 automatically when you upgrade the components in the basic APM system architecture. No additional steps are required.

Upgrade from any version V4.6.2.0.0 through V4.6.10.0.0

The following tables outline the steps that you must complete to upgrade this module to V5.2.1.0.0. These instructions assume that you have completed the steps for upgrading the basic APM system architecture.

These tasks may be completed by multiple people in your organization. We recommend, however, that the tasks be completed in the order in which they are listed.

StepTaskNotes
1Upgrade from PDI to OT Connect This step is required only if you are using Content Map records as health indicators sources.
2 Resync Health Indicators

Depending on the status of potential health indicator sources in your database, the resync will result in one or both of the following scenarios:

  • If health indicators do not already exist for sources that are included as health indicators, the resync creates health indicators for those sources.
  • If health indicators exist for sources that are excluded as health indicators, the resync deletes health indicators for those sources.

    Additionally, if the exclusion table contains extraneous entries, the resync removes those entries.

This step is optional.