Upgrading Run-Time Nodes

Important: Upgrade the GR node and any IDE-only nodes before upgrading run-time nodes.

After you upgrade the GR and IDE, all run-time nodes continue to run. This enables you to upgrade the run-time nodes individually when it is convenient.

Important: After you have upgraded the GR node, and you have migrated the galaxy, you will not be able to deploy or undeploy from the GR node to remote nodes which have not yet been upgraded. Once remote node upgrade is complete, deployment functionality returns. Also, an upgraded IDE node will not be able to connect to a GR node that has not been upgraded.

Upgrading a run-time node will remove (undeploy) any deployed Platforms from that node.

After you upgrade and then deploy a run-time node, it continues to function with other run-time nodes as long as the other nodes are the current version or from the previous version.

The run-time node does not function while you are upgrading it. You cannot roll back the upgrade.

After you upgrade the run-time node and all hosted objects, you need to redeploy the WinPlatform and all hosted objects to the node.

The GR node migration fails if the GR node is used as a run-time node for another GR.

To upgrade a run-time node

1. Run Setup.exe from the DVD. See Upgrading the Wonderware System Platform for information about the installation process.

   When the Installation Complete dialog box appears, click Configure to continue.

2. Configuration: Configure licensing, the System Management Server, and other installed features, such as the Historian and the InTouch Web Client.

   • Configure the System Management Server to point to the GR node. See Configuring the System Management Server for additional information.

   • Configure the AVEVA System Monitor to point to the System Monitor Manager node. By default, this is the GR node. See Advanced System Monitor Configuration for additional information.

3. When prompted, click Restart Now to complete the upgrade.