Upgrading the Systems in Distribution (Hierarchical and Fully Meshed)
Perform the following procedures to upgrade a hierarchical or fully meshed distributed system.
Scenario:
You want to upgrade an existing hierarchical distributed system deployed on 3 separate systems (for example, Server 1, 2 and 3) to the latest version.
For this, you must first de-link each system in distribution by stopping the respective project on the system, upgrade it individually and then bring it again back in the distribution. You should start this activity by de-linking the supervised systems first, in this case Server 2 and Server 3. This is because these systems have limited dependency and are local systems. Next, de-link the supervising system (Server 1) and upgrade each system one by one before finally bringing them back in distribution.
It is recommended to de-link each system in distribution and thereafter upgrade it individually to reduce the down time of the overall distributed system.
Prerequisites:
- You have taken a backup of the project and HDB before proceeding with the upgrade.
- Before upgrading the live system, you have conducted the upgrade on a different system and ensured that the upgrade is successful. After upgrade, you are able to access the partner systems and view the data on the partner systems as a global user.
Perform the following steps exactly in the given order.
- To de-link and upgrade Server 2, do the following:
a. From the Projects node, select the project and stop it. See Stop a Project in Server Projects Configuration Procedures.
b. (Optional) Stop the history database linked to the project. See Stop an HDB in Restoring and Upgrading the History Database.
c. Upgrade the management platform along with project and HDB and so on using either custom, semi-automatic, or silent installation mode along with the post installation steps.
- Project 2 in Server 2 is removed from distribution and the management platform along with the project, linked database, website, web applications are upgraded to the latest version. The logon dialog box displays and prompts you to provide password to logon.
- Repeat substeps of step 1 in the same order to remove project 3 from distribution and then upgrade it.
- Project 3 in Server 3 is removed from distribution and the management platform along with the project, linked database, website, web applications are upgraded to the latest version. The logon dialog box displays and prompts you to provide password to logon.
- Similarly, repeat the substeps of step 1 in the same order to remove project 1 for the Supervising system, Server 1 from the distribution and then upgrade it.
- Project 1 in Server 1 is removed from distribution and the management platform along with the project, linked database, website, web applications are upgraded to the latest version. The logon dialog box displays and prompts you to provide password to logon.
- Navigate to SMC on the supervising system, Server 1 and select project 1.
- In the Distribution Participants expander, click Sync to sync the partner projects with details on the originator projects.
- Navigate to the participating projects, Project 2 and Project 3 and restart these projects.
- The hierarchical distributed system is upgraded and back in distribution.
- Verify that the entire distributed system works as expected.
Testing the System after an upgrade
Perform the following activities to test that the upgrade to the distributed system is successful:
- View all the connected partner systems from the system on which you are logged in with global user.
- Verify that the drivers in the supervised and supervising systems are in correct state, networks are in connected state, and devices and points are also in connected state.
- Verify that applications such as trends, graphics and so on are loading and displaying correctly in their respective applications.
Scenario:
You want to upgrade an existing fully meshed distributed system deployed on 3 separate systems (for example, Server 1, 2 and 3) to the latest version.
For this, you must first de-link each system in distribution by stopping the respective project on the system, upgrade it individually and then bring it back again in the distribution. You should start this activity by de-linking the systems according to their criticality levels, starting with the system that has the lowest level of criticality. For this scenario, we consider that Server 3 has the highest level of criticality, followed by Server 2 and Server1, therefore we start with the de-linking and upgrade of Server 1 followed by Server 2 and finally the most critical system Server 3. After de-linking each system in the order of their criticality, we upgrade each system one by one before finally bringing them back in distribution.
It is recommended to de-link each system in distribution and thereafter upgrade it individually to reduce the down time of the overall distributed system.
Prerequisites:
- You have taken a backup of the project and HDB before proceeding with the upgrade.
- Before upgrading the live system, you have conducted the upgrade on a different system and ensured that the upgrade is successful. After upgrade, you are able to access the partner systems and view the data on the partner systems as a global user.
Perform the following steps exactly in the given order.
- To de-link and upgrade Server 1, do the following:
a. From the Projects node, select the project and stop it. See Stop a Project in Server Projects Configuration Procedures.
b. (Optional) Stop the history database linked to the project. See Stop an HDB in Restoring and Upgrading the History Database.
c. Upgrade the management platform along with project and HDB and so on using either custom, semi-automatic, or silent installation mode along with the post installation steps.
- Project 1 in Server 1 is removed from distribution and the management platform along with the project, linked database, website, web applications are upgraded to the latest version. The logon dialog box displays and prompts you to provide password to logon.
- Repeat the substeps of Step 1 in the same order to remove project 2 from distribution and then upgrade it.
- Project 2 on Server 2 is removed from distribution and the management platform along with the project, linked database, website, web applications are upgraded to the latest version. The logon dialog box displays and prompts you to provide password to logon.
- Similarly, repeat the substeps of Step 1 in the same order to remove project 3 from the distribution and then upgrade it.
- Project 3 in Server 3 is removed from distribution and the management platform along with the project, linked database, website, web applications are upgraded to the latest version. The logon dialog box displays and prompts you to provide password to logon.
- Navigate to SMC on Server 3 and select project 3.
- In the Distribution Participants expander, click Sync to sync the partner projects with details on the originator projects.
- Navigate to Project 1 and Project 2 and restart them.
- The fully meshed distributed system is upgraded and back in distribution.
- Verify that the entire distributed system works as expected.
Testing the System after an upgrade
Perform the following activities to test that the upgrade to the distributed system is successful:
- View all the connected partner systems from the system on which you are logged in with global user.
- Verify that the drivers in the systems in distribution are in correct state, networks are in connected state, and devices and points are also in connected state.
- Verify that applications such as trends, graphics and so on are loading and displaying correctly in their respective applications.
