Upgrade or Update APM

Upgrade or Update APM to V4.6.10.0.0

Upgrading or updating and configuring APM includes completing multiple steps, which are outlined in the tables in this section. This section of the documentation provides all the information that you need to upgrade or update and configure the basic system architecture to V4.6.10.0.0.

After you have completed these steps, you will need to perform additional steps required to upgrade any modules that were deployed on your previous version. If you have purchased additional modules for use with APM, then you will also need to consult the first-time deployment documentation for each of those modules and features.

The person responsible for completing each task may vary within in your organization. We recommend, however, that the steps be performed in relatively the same order in which they are listed in the table.

Upgrade from any version V4.6.0.0.0 through V4.6.9.0.0

If your current version is APM V4.6.0.0.0 through V4.6.9.0.0, then updating the basic system architecture to V4.6.10.0.0 requires only that you complete the steps that are outlined in the table in this section.
StepTaskNotes
1Create a backup of your database and configuration files (.conf) that exist in the following directories:
  • C:\Program Files\Meridium
  • C:\ProgramData\Meridium
This step is not mandatory, but is recommended by APM. Updates may include changes to configuration files and database elements. If any problems occur during the update, the configuration files and database can be restored to their original states from the backup copies.
2Stop all the APM services.This step is required.
3On each APM server, including both dedicated and supporting instances, uninstall the APM Server and Add-ons component.This step is required.
4On each APM server, including both dedicated and supporting instances, install and configure the APM Server software and Add-ons.This step is required.
5Install the latest version of APM on mobile devices using the iOS, Android, or Windows operating system.This step is required if you want to use APM on a mobile device.
6Start all the services in the following order:
  • Redis
  • ActiveMQ
  • Elastic Search and Search Service
  • All other services (no specific order)
This step is required.

Upgrade from any version V4.5.0.0.0 through V4.5.0.0.21

If your current version is APM V4.5.0.0.0 through V4.5.0.0.20, then updating the basic system architecture to V4.6.10.0.0 requires only that you complete the steps that are outlined in the table in this section.
StepTaskNotes
1Create a backup of your database and configuration files (.conf) that exist in the following directories:
  • C:\Program Files\Meridium
  • C:\ProgramData\Meridium
This step is not mandatory, but is recommended by APM. Updates may include changes to configuration files and database elements. If any problems occur during the update, the configuration files and database can be restored to their original states from the backup copies.
2 Update the APM Server and Add Ons software on the APM Server(s).This step is required. This procedure includes updating your data sources for V4.6.10.0.0.
3Install Redis on the GE Vernova Redis server (Linux server).This step is required.
4Upgrade the APM adapter for SSRS.This step is required.
5Upgrade the APM database.This step is required.
6If you want to activate non-English translations in APM, then deploy translations.This step is required only if you are deploying translations for the first time or if you want to utilize and redeploy updated translations.
7As needed, configure one of the virtual machine to execute all the scheduled jobs.This step is required only if you have deployed APM in a clustered environment and you want to dedicate a virtual machine to run all the scheduled jobs.
8As needed, deploy the APM mobile application on mobile devices.This step is required only if you are deploying the APM mobile application on mobile devices.

Upgrade from any version V4.4.0.0.0 through V4.4.0.0.16

If your current version is APM V4.4.0.0.0 through V4.4.0.0.16, then updating the basic system architecture to V4.6.10.0.0 requires only that you complete the steps that are outlined in the table in this section.

Step

Task

Notes
1Create a backup of your database and configuration files (.conf) that exist in the following directories:
  • C:\Program Files\Meridium
  • C:\ProgramData\Meridium
This step is not mandatory, but is recommended by APM. Updates may include changes to configuration files and database elements. If any problems occur during the update, the configuration files and database can be restored to their original states from the backup copies.
2 Update the APM Server and Add Ons software on the APM Server(s).This step is required. This procedure includes updating your data sources for V4.6.10.0.0.
3Install Redis on the GE Vernova Redis server (Linux server).This step is required.
4Upgrade the APM adapter for SSRS.This step is required.
5Upgrade the APM database.This step is required.
6If you want to activate non-English translations in APM, then deploy translations.This step is required only if you are deploying translations for the first time or if you want to utilize and redeploy updated translations.
7As needed, configure one of the virtual machine to execute all the scheduled jobs.This step is required only if you have deployed APM in a clustered environment and you want to dedicate a virtual machine to run all the scheduled jobs.
8As needed, deploy the APM mobile application on mobile devices.This step is required only if you are deploying the APM mobile application on mobile devices.

Upgrade from any version V4.3.0.0.0 through V4.3.1.0.11

If your current version is APM V4.3.0.0.0 through V4.3.1.0.11, then updating the basic system architecture to V4.6.10.0.0 requires only that you complete the steps that are outlined in the table in this section.

Step

Task

Notes
1Create a backup of your database, and create a backup of any configuration files that exist in your pre-updated system.This step is not mandatory, but is recommended by APM. Updates may include changes to configuration files and database elements. If any problems occur during the update, the configuration files and database can be restored to their original states from the backup copies.
2 Update the APM Server and Add Ons software on the APM Server(s).This step is required. This procedure includes updating your data sources for V4.6.10.0.0.
3Install ActiveMQ on a dedicated server.This step is required. You must install ActiveMQ on a server in your environment.
4If you want to activate non-English translations in APM, then deploy translations.This step is required only if you are deploying translations for the first time or if you want to utilize and redeploy updated translations.
5As needed, configure one of the virtual machine to execute all the scheduled jobs.This step is required only if you have deployed APM in a clustered environment and you want to dedicate a virtual machine to run all the scheduled jobs.
6As needed, deploy the APM mobile application on mobile devices.This step is required only if you are deploying the APM mobile application on mobile devices.

Upgrade from a version prior to version V4.3.0.0.0

If your current version is a version prior to APM V4.3.0.0.0, then updating the basic system architecture to V4.6.10.0.0 requires only that you complete the steps that are outlined in the table in this section.

Step

Task

Notes
1Ensure that your system meets the hardware and software requirements for the basic APM system architecture.This step is required.
2Ensure that all existing APM Security Users have been assigned time zones. Refer to your pre-upgraded system documentation for information on managing APM Security Users.This step is required. If there are APM Security Users to whom time zones have not been assigned, a failure will occur during the database upgrade process.
3If you intend to upgrade the Production Loss Analysis (PLA) module from a starting version prior to V3.6.0.0.0, then import the required baseline rules.
Important:

This step is required only if you intend to upgrade the Production Loss Analysis (PLA) module from a starting version prior to Meridium Enterprise APM V3.6.0.0.0. If you intend to upgrade PLA in this manner, this procedure must be completed before upgrading the APM Server and Add Ons software on the APM Server. This procedure is part of the upgrade Production Loss Analysis workflow.

4

Create a backup of any configuration files that exist in your pre-upgraded system which you may want to retain post-upgrade.

This step is required only if you want to retain customizations that you have made to your existing configuration files.

5

Upgrade the APM Server and Add Ons software on the APM Server.

This step is required. Consult the documentation on Redis for information about its incorporation into server configurations.
6

Install Elasticsearch on its own, dedicated server.

This step is required

Note:

You must install Elasticsearch on a server in your environment.

For optimum system performance, APM recommends that you install Elasticsearch on its own, dedicated server that contains no APM components.

7Install ActiveMQ on a dedicated server.This step is required. You must install ActiveMQ on a server in your environment.

8

Upgrade the SQL Server Report Server.

This step is required.

9

Upgrade the APM Database Server.

This step is required.
10If you want to use non-English translations in APM, then deploy translations.This step is required only if you are deploying translations for the first time or if you want to utilize and redeploy updated translations.
11If required, configure one of the virtual machine to execute all the scheduled jobs.This step is required only if you have deployed APM in a clustered environment and you want to dedicate a virtual machine to run all the scheduled jobs.
12If required, deploy the APM mobile application on mobile devices.This step is required only if you are deploying the APM mobile application on mobile devices.
13If required, enable single sign-on for on-site or off-site authentication.This step is required only if you are enabling single sign-on.