The following tables outline the steps that you must complete to upgrade this module to V4.3.0.5.0. These instructions assume that you have completed the steps for upgrading the basic GE Digital 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.
If your system architecture contains multiple servers to process policy executions, these steps assume that you have configured them according to your company's preference for server load-balancing.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
If you are upgrading from V4.1.5.x and you used Policy Recommendations for the first time in V4.1.5.x, after you upgrade your database, use the State Management option in the Revert to Baseline feature to apply the correct State Configuration for the Policy Recommendation Family.
When you do so, you will need to provide mappings from the incorrect states to the corresponding correct states, as shown in the following table:
Custom (incorrect)
Baseline
(correct)
Accepted
by ASM
Completed
Closed
Completed
Consolidated
Superseded
Open
Proposed
Pending
Pending
Approval
Superseded
Superseded
This step is necessary because an incorrect baseline State Configuration was delivered for the Policy Recommendation family in V4.1.5.0. The baseline configuration was corrected in V4.1.6.0.
The correct baseline state configuration must be applied for various queries and lists in GE Digital APM to function as expected.
You do not need to complete this step if:
You never used V4.1.5.x
-or-
You never used Policy Recommendations
-or-
You used Policy Recommendations in a version prior to V4.1.5.x
2
On the GE Digital APM Server, start or restart the Policy Execution Service.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
5
On the GE Digital APM Server, reset IIS.
This step is required.
6
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
7
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
6
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
4
On the GE Digital APM Server, reset IIS.
This step is required.
5
On the Process Data Integration Server, start (or restart if it is already started) the Meridium Process Data Integration
Service.
This step is required only if you want to use OPC Tag records in your policies.
7
Review the Policy Upgrade Utility log files, and, as needed, manually update policy schedules.
This step is required.
You may review the log files for this service at C:\ProgramData\Meridium\Logs.
If your database contained policies with execution schedules containing invalid times for the most recent Next Date or Last Date (for example, between 2:00 A.M. and 3:00 A.M. on the morning of daylight savings time), these fields were left blank during the upgrade. To ensure that your scheduled policies execute as expected, review the log, and update policy schedules in Policy Designer as needed.
