You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/upgrade-guides/upgrade-cortex/2024.9.25161-to-2025.3/multiple-server-with-ha/_index.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,3 +4,7 @@ linkTitle: "Multiple Server - With HA"
4
4
description: "Upgrade instructions for multiple on-premise servers with high availability (HA)."
5
5
weight: 10
6
6
---
7
+
8
+
{{% alert title="Warning" color="warning" %}}
9
+
This upgrade guide is only applicable if upgrading from 2024.9.25161.
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/upgrade-guides/upgrade-cortex/2025.1-to-2025.3/multiple-server-with-ha/_index.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,3 +4,7 @@ linkTitle: "Multiple Server - With HA"
4
4
description: "Upgrade instructions for multiple on-premise servers with high availability (HA)."
5
5
weight: 10
6
6
---
7
+
8
+
{{% alert title="Warning" color="warning" %}}
9
+
Due to breaking changes required for upgrading RabbitMQ from version 3 to version 4 the Application Servers need to be reinstalled rather than upgraded. As a result packages will need to be republished and Config Store data will need to be backed up and restored. Other data stored in Reliable Collections (e.g., data storage collections and semaphores) will be lost.
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/upgrade-guides/upgrade-cortex/2025.1-to-2025.3/multiple-server-with-ha/pre-upgrade.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,8 +13,15 @@ This guide describes how to perform the steps required before starting the upgra
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/upgrade-guides/upgrade-cortex/2025.1-to-2025.3/multiple-server-with-ha/upgrade/upgrade-application-and-loadbalancer-servers.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,10 @@ weight: 30
9
9
10
10
This guide describes how to upgrade the Application Servers and Load Balancer Server from 2025.1 to 2025.3. Please ensure that the [Pre-Upgrade][PreUpgrade] steps have been completed before starting this upgrade.
11
11
12
+
{{% alert title="Warning" color="warning" %}}
13
+
Due to breaking changes required for upgrading RabbitMQ from version 3 to version 4 the Application Servers need to be reinstalled rather than upgraded. As a result packages will need to be republished and Config Store data will need to be backed up and restored. Other data stored in Reliable Collections (e.g., data storage collections and semaphores) will be lost.
14
+
{{% /alert %}}
15
+
12
16
## Configure Upgrade Script
13
17
14
18
1. In the `Cortex Innovation 2025.3 - App Server Install Scripts\Upgrade Application Server` folder, locate the `Cortex.Innovation.Upgrade.ps1` script and open it with a text editor.
Copy file name to clipboardExpand all lines: content/en/docs/2025.3/Guides/upgrade-guides/upgrade-cortex/2025.1-to-2025.3/multiple-server-with-ha/upgrade/upgrade-web-application-server/upgrade-gateway.md
+40Lines changed: 40 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,6 +17,45 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2025.1 to 2025.3. P
{{< alert type="note" title="Note" >}} This only needs to happen for upgrading to this release version as breaking changes were introduced as part of the RabbitMQ upgrade.{{< /alert >}}
23
+
24
+
1. Open a web browser.
25
+
1. Navigate to `https://server.domain.com:9080/Explorer`, where `server.domain.com` is the fully qualified domain name of one of the application servers. Replace `9080` with new `httpGatewayEndpointPort` value if it was changed during configuration of the original installation.
26
+
1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution`.
27
+
1. For all old execution applications:
28
+
* Click on the drop down menu and select `Delete Application`. Confirm application deletion by following the on-screen instructions.
29
+
* Give this a few minutes. If the application does not delete:
30
+
* Expand `Nodes`
31
+
* For each node:
32
+
* Expand the node and select the application that matches the engine version number of the application that is being attempted to be deleted.
33
+
* Expand each level up to and including `Code Packages`.
34
+
* Click on the drop down menu for `Code` and select `Restart`. Confirm application restart by following the on-screen instructions.
35
+
* Give this a few minutes. Once all nodes have been restarted the application should be deleted and disappear from the list of applications.
36
+
37
+
Repeat the above instructions for the `Flow Debugger`. In step 2 `server.domain.com` is the fully qualified domain name of the web application server.
38
+
39
+
## Republish Packages
40
+
41
+
{{< alert type="note" title="Note" >}} This only needs to happen for upgrading to this release version as breaking changes were introduced as part of the RabbitMQ upgrade.{{< /alert >}}
42
+
43
+
1. Log in to Gateway with a user that has the `Admin` role.
44
+
1. Click on the `Admin` charm, then `Packages`.
45
+
1. In the `Package Definitions` grid, select `Is Published` filter option on the `Is Published` column to show all published packages.
46
+
1. For each published package version:
47
+
* Select the package.
48
+
* Click `Unpublish` at the bottom of the `Definition` tab and click `Unpublish` on the confirmation pop-up dialog. A success message should appear. If it doesn't it means that there is a problem with the configuration in the `web.config` file for {{% ctx %}} Gateway, or the Application Services aren't healthy
49
+
* Click `Create New Version` then click `Save` and wait for the new version to be created.
50
+
* Click `Publish`. A success message should appear. If it doesn't it means that there is a problem with the configuration in the `web.config` file for {{% ctx %}} Gateway, or the Application Services aren't healthy.
51
+
* Sometimes the list of published packages in the `Package Definitions` grid disappears. To fix, set the `Is Published` filter in the `Package Definitions` grid to blank option and then set the filter to `Is Published` option again to show all published packages.
52
+
53
+
## Restore Config Store Data
54
+
55
+
If using the {{% ctx %}} Config Store, the data will need to be restored.
56
+
57
+
For further assistance, please raise a case in the [{{% ctx %}} Service Portal][].
58
+
20
59
## Preserve installation files
21
60
22
61
{{< section "/preserve-installation-files.md" >}}
@@ -25,5 +64,6 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2025.1 to 2025.3. P
description: "Information about upgrading the Web Application Server from 2025.1 to 2025.3."
5
+
weight: 30
6
+
---
7
+
8
+
# {{% param title %}}
9
+
10
+
This guide describes how to upgrade {{% ctx %}} Gateway from 2025.1 to 2025.3. Please ensure that the [Upgrade Application Server][] has been completed before starting this upgrade.
0 commit comments