Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ System Platform

TABLE OF CONTENTS

Basic upgrade sequence

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJan 23, 2025
  • 2 minute read

Important: Back up the Galaxy before starting an upgrade. Also, upload any run-time changes for critical objects. You cannot upload any run-time change from non-upgraded nodes after you upgrade the system.

.NET Framework 4.8 is installed if it or a later version is not already present. You may be prompted to restart your computer after the .NET framework is installed.

The basic upgrade steps are:

  1. Upgrade your hardware and prerequisite software such as the operating system or Microsoft SQL Server to the required versions. For information on hardware and software requirements, see the System Platform Readme file.

    If you are upgrading the SQL Server database on the GR node, you must undeploy the GR node before starting the SQL Server upgrade.

  2. Upgrade and configure the GR node. If you are upgrading from System Platform 2017 Update 2 or a prior version, the Common Platform System Management Server is automatically installed on the GR node. For more information, see Upgrade a Galaxy Repository node.

  3. Upgrade and configure at least one IDE installation. If you upgrade the GR node, that IDE installation is upgraded. However, if you have any IDE-only nodes, you will have to upgrade them separately. For more information, see Upgrade an IDE-only node.

  4. Migrate the Galaxy database. Connect to the upgraded GR node from the upgraded IDE to migrate the galaxy to the new version automatically.

  5. Deploy the GR Platform.

  6. Upgrade and configure run-time nodes.

If you upgrade a remote Platform node before you migrate the Galaxy database, the remote Platform and hosted objects show the software upgrade pending icon after you migrate and deploy the Galaxy. To resolve this, undeploy and redeploy the remote Platform.

Important: After you have upgraded the GR node to Application Server 2023 R2 SP1, you will not be able to deploy or undeploy from the GR node to non-upgraded remote nodes. Also, an IDE node that has been upgraded will not be able to connect to a GR node that has not been upgraded.

Note: As long as the operating system and SQL requirements are met, upgrade is supported.

TitleResults for “How to create a CRG?”Also Available in