From 388450a44143c1c020e2c6a6f123c7ceb9e121eb Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 12:55:36 +0100 Subject: [PATCH 01/14] added re-publish packages section --- .../upgrade-web-application-server.md | 4 ++++ .../upgrade-web-application-server/republish-packages.md | 9 +++++++++ 2 files changed, 13 insertions(+) create mode 100644 content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md index d8b1671fa..716b6bc40 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md @@ -26,6 +26,10 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P {{< section "/upgrade/2024.9/upgrade-web-application-server/run-gateway-script.md" >}} +## Republish packages + +{{< section "/upgrade/2024.9/upgrade-web-application-server/republish-packages.md" >}} + ## Preserve installation files {{< section "/preserve-installation-files.md" >}} diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md new file mode 100644 index 000000000..7f1f6d88e --- /dev/null +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -0,0 +1,9 @@ +1. Unpublish existing published packages and create new versions + * Log in to Gateway with a user that has the `Admin` role. + * Click on the `Admin` charm, then `Packages`. + * In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. + * For each published package version + * Select the package. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. + * Click `Create New Version` then click `Save` and wait for the new version to be created. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. \ No newline at end of file From 31a28491db31e94727ece7a484ae78ff6a68f43c Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 12:59:52 +0100 Subject: [PATCH 02/14] added note to steps --- .../2024.9/upgrade-web-application-server/republish-packages.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md index 7f1f6d88e..22bda84b0 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -1,4 +1,6 @@ 1. Unpublish existing published packages and create new versions +{{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} + * Log in to Gateway with a user that has the `Admin` role. * Click on the `Admin` charm, then `Packages`. * In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. From dbe123f49a1a8927a15bf4f47f358bbda0b30aae Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 13:33:50 +0100 Subject: [PATCH 03/14] updated format of notes --- .../upgrade-web-application-server.md | 2 +- .../delete-old-execution-services.md | 11 +++++++++++ .../republish-packages.md | 18 ++++++++---------- 3 files changed, 20 insertions(+), 11 deletions(-) create mode 100644 content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md index 716b6bc40..4eca3ed44 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md @@ -27,7 +27,7 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P {{< section "/upgrade/2024.9/upgrade-web-application-server/run-gateway-script.md" >}} ## Republish packages - + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} {{< section "/upgrade/2024.9/upgrade-web-application-server/republish-packages.md" >}} ## Preserve installation files diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md new file mode 100644 index 000000000..22bda84b0 --- /dev/null +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -0,0 +1,11 @@ +1. Unpublish existing published packages and create new versions +{{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} + + * Log in to Gateway with a user that has the `Admin` role. + * Click on the `Admin` charm, then `Packages`. + * In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. + * For each published package version + * Select the package. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. + * Click `Create New Version` then click `Save` and wait for the new version to be created. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. \ No newline at end of file diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md index 22bda84b0..6f7c3b607 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -1,11 +1,9 @@ -1. Unpublish existing published packages and create new versions -{{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} - * Log in to Gateway with a user that has the `Admin` role. - * Click on the `Admin` charm, then `Packages`. - * In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. - * For each published package version - * Select the package. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. - * Click `Create New Version` then click `Save` and wait for the new version to be created. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. \ No newline at end of file +1. Log in to Gateway with a user that has the `Admin` role. +1. Click on the `Admin` charm, then `Packages`. +1. In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. +1. For each published package version + * Select the package. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. + * Click `Create New Version` then click `Save` and wait for the new version to be created. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. From b84856b5ba0eb5e8724ab0d7c8f6db01066373b6 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 13:55:28 +0100 Subject: [PATCH 04/14] added notes for deleting the old applications --- .../delete-old-execution-services.md | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md index 22bda84b0..33f927c11 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -1,11 +1,10 @@ -1. Unpublish existing published packages and create new versions -{{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} - * Log in to Gateway with a user that has the `Admin` role. - * Click on the `Admin` charm, then `Packages`. - * In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. - * For each published package version - * Select the package. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. - * Click `Create New Version` then click `Save` and wait for the new version to be created. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. \ No newline at end of file +1. Navigate to the service fabric explorer. +1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution` +1. For all old execution applications + * Click on the drop down menu and select `Delete Application` + * Give this a few minutes. If the application does not delete + * Expand `Nodes` and select the application that matches the engine version number of the application that is being attempted to be deleted + * Expand each level up to `Code Packages` + * Click on the drop down menu for `Code` and select `Restart`. + * Give this a few minutes. The application should be deleted and disappear from the list of applications. From 4114d632f5c1097b3da95c3d70132af3857940bb Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 13:56:25 +0100 Subject: [PATCH 05/14] using the new file in the upgrade gateway section --- .../upgrade-web-application-server.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md index 4eca3ed44..31ef438ff 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md @@ -30,6 +30,10 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} {{< section "/upgrade/2024.9/upgrade-web-application-server/republish-packages.md" >}} +## Delete old execution service + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} +{{< section "/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md" >}} + ## Preserve installation files {{< section "/preserve-installation-files.md" >}} From dbddff2d6d38f6a08895fea8537523bdee784058 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:05:46 +0100 Subject: [PATCH 06/14] added same instructions to multi server --- .../upgrade-web-application-server/upgrade-gateway.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md index c0d2d2848..c958814ac 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md @@ -17,6 +17,14 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P {{< section "/upgrade/2024.9/upgrade-web-application-server/run-gateway-script.md" >}} +## Republish packages + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} +{{< section "/upgrade/2024.9/upgrade-web-application-server/republish-packages.md" >}} + +## Delete old execution service + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} +{{< section "/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md" >}} + ## Preserve installation files {{< section "/preserve-installation-files.md" >}} From 80965603bb6c08c1e00cdc185ac1055bdae473c8 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:13:02 +0100 Subject: [PATCH 07/14] broken down further --- .../delete-old-execution-services.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md index 33f927c11..0b0b6ca63 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -1,10 +1,12 @@ -1. Navigate to the service fabric explorer. +1. Navigate to the service fabric explorer in a web browser. 1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution` 1. For all old execution applications * Click on the drop down menu and select `Delete Application` * Give this a few minutes. If the application does not delete - * Expand `Nodes` and select the application that matches the engine version number of the application that is being attempted to be deleted - * Expand each level up to `Code Packages` - * Click on the drop down menu for `Code` and select `Restart`. - * Give this a few minutes. The application should be deleted and disappear from the list of applications. + * Expand `Nodes` + * For each node + * select the application that matches the engine version number of the application that is being attempted to be deleted + * Expand each level up to `Code Packages` + * Click on the drop down menu for `Code` and select `Restart`. + * Give this a few minutes. The application should be deleted and disappear from the list of applications. From dcad4c8ee8bf651d7b885c91dea526890c148d77 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:17:26 +0100 Subject: [PATCH 08/14] added instruction for repeat steps 1-3 --- .../delete-old-execution-services.md | 4 +++- .../upgrade-web-application-server/republish-packages.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md index 0b0b6ca63..5a1d125c1 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -6,7 +6,9 @@ * Give this a few minutes. If the application does not delete * Expand `Nodes` * For each node - * select the application that matches the engine version number of the application that is being attempted to be deleted + * Select the application that matches the engine version number of the application that is being attempted to be deleted * Expand each level up to `Code Packages` * Click on the drop down menu for `Code` and select `Restart`. * Give this a few minutes. The application should be deleted and disappear from the list of applications. + +Repeat these instructions for the flow debugger. diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md index 6f7c3b607..bc2c3f607 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -6,4 +6,4 @@ * Select the package. * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. * Click `Create New Version` then click `Save` and wait for the new version to be created. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. \ No newline at end of file From a1b576a861e9fdec2cd0ebbb99504f6a12aa97a1 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:18:30 +0100 Subject: [PATCH 09/14] not needed for this section --- .../upgrade-web-application-server.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md index 31ef438ff..bd510b2b2 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md @@ -26,10 +26,6 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P {{< section "/upgrade/2024.9/upgrade-web-application-server/run-gateway-script.md" >}} -## Republish packages - {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} -{{< section "/upgrade/2024.9/upgrade-web-application-server/republish-packages.md" >}} - ## Delete old execution service {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} {{< section "/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md" >}} From 30315b2524359de524edd6f0cec05a8ac6a9f1bb Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:21:26 +0100 Subject: [PATCH 10/14] only relevant for multi node --- .../upgrade-web-application-server/upgrade-gateway.md | 1 + .../delete-old-execution-services.md | 4 +--- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md index c958814ac..44a037294 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md @@ -24,6 +24,7 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P ## Delete old execution service {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} {{< section "/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md" >}} +Repeat these instructions for the `Flow Debugger`. ## Preserve installation files diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md index 5a1d125c1..3effee98d 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -9,6 +9,4 @@ * Select the application that matches the engine version number of the application that is being attempted to be deleted * Expand each level up to `Code Packages` * Click on the drop down menu for `Code` and select `Restart`. - * Give this a few minutes. The application should be deleted and disappear from the list of applications. - -Repeat these instructions for the flow debugger. + * Give this a few minutes. The application should be deleted and disappear from the list of applications. \ No newline at end of file From 6ada48dd170f5fa6a0d8580e904b9ab20e174d0b Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:23:44 +0100 Subject: [PATCH 11/14] : missing from syntax --- .../delete-old-execution-services.md | 4 ++-- .../upgrade-web-application-server/republish-packages.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md index 3effee98d..59afaaad4 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -1,11 +1,11 @@ 1. Navigate to the service fabric explorer in a web browser. 1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution` -1. For all old execution applications +1. For all old execution applications: * Click on the drop down menu and select `Delete Application` * Give this a few minutes. If the application does not delete * Expand `Nodes` - * For each node + * For each node: * Select the application that matches the engine version number of the application that is being attempted to be deleted * Expand each level up to `Code Packages` * Click on the drop down menu for `Code` and select `Restart`. diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md index bc2c3f607..e75ad8311 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -2,7 +2,7 @@ 1. Log in to Gateway with a user that has the `Admin` role. 1. Click on the `Admin` charm, then `Packages`. 1. In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. -1. For each published package version +1. For each published package version: * Select the package. * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. * Click `Create New Version` then click `Save` and wait for the new version to be created. From d2a996013bd9906f9d3e0f5188047f9198111ec8 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 14:45:30 +0100 Subject: [PATCH 12/14] needed full stops --- .../delete-old-execution-services.md | 12 ++++++------ .../republish-packages.md | 5 +++-- 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md index 59afaaad4..01a34a339 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md @@ -1,12 +1,12 @@ 1. Navigate to the service fabric explorer in a web browser. -1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution` +1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution`. 1. For all old execution applications: - * Click on the drop down menu and select `Delete Application` - * Give this a few minutes. If the application does not delete + * Click on the drop down menu and select `Delete Application`. + * Give this a few minutes. If the application does not delete. * Expand `Nodes` * For each node: - * Select the application that matches the engine version number of the application that is being attempted to be deleted - * Expand each level up to `Code Packages` + * Expand the node and select the application that matches the engine version number of the application that is being attempted to be deleted. + * Expand each level up to `Code Packages`. * Click on the drop down menu for `Code` and select `Restart`. - * Give this a few minutes. The application should be deleted and disappear from the list of applications. \ No newline at end of file + * Give this a few minutes. The application should be deleted and disappear from the list of applications. diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md index e75ad8311..ff69e346c 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -1,9 +1,10 @@ 1. Log in to Gateway with a user that has the `Admin` role. 1. Click on the `Admin` charm, then `Packages`. -1. In the `Package Definitions` grid, select `Is Published` filter on the `Is Published` column to show all published packages. +1. In the `Package Definitions` grid, select `Is Published` filter option on the `Is Published` column to show all published packages. 1. For each published package version: * Select the package. * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. * Click `Create New Version` then click `Save` and wait for the new version to be created. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. \ No newline at end of file + * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. + * Sometimes the list of published packages in the `Package Definitions` grid disappear. 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. From cbed61d3bb52b78b09e59de63dee4445ad1bef29 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Tue, 8 Oct 2024 16:55:22 +0100 Subject: [PATCH 13/14] typo --- .../upgrade-web-application-server/republish-packages.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md index ff69e346c..8cf2dbe0f 100644 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md @@ -4,7 +4,9 @@ 1. In the `Package Definitions` grid, select `Is Published` filter option on the `Is Published` column to show all published packages. 1. For each published package version: * Select the package. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. + * 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. See [Troubleshooting][] for more information. * Click `Create New Version` then click `Save` and wait for the new version to be created. - * 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 CORTEX Gateway, or the Application Services aren’t healthy. See Troubleshooting for more information. - * Sometimes the list of published packages in the `Package Definitions` grid disappear. 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. + * 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. See [Troubleshooting][] for more information. + * 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. + +[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}} From aa55ed60d4ebbfb4048a1437df50b695f65bc298 Mon Sep 17 00:00:00 2001 From: cortex-bt Date: Wed, 9 Oct 2024 10:45:23 +0100 Subject: [PATCH 14/14] no longer shared as there are differences --- .../upgrade-gateway.md | 37 +++++++++++++++---- .../upgrade-web-application-server.md | 19 ++++++++-- .../delete-old-execution-services.md | 12 ------ .../republish-packages.md | 12 ------ 4 files changed, 45 insertions(+), 35 deletions(-) delete mode 100644 content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md delete mode 100644 content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md index 44a037294..c10bf9752 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/multiple-server-with-ha/upgrade-web-application-server/upgrade-gateway.md @@ -17,14 +17,35 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P {{< section "/upgrade/2024.9/upgrade-web-application-server/run-gateway-script.md" >}} -## Republish packages - {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} -{{< section "/upgrade/2024.9/upgrade-web-application-server/republish-packages.md" >}} - -## Delete old execution service - {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} -{{< section "/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md" >}} -Repeat these instructions for the `Flow Debugger`. +## Republish Packages + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues.{{< /alert >}} +1. Log in to Gateway with a user that has the `Admin` role. +1. Click on the `Admin` charm, then `Packages`. +1. In the `Package Definitions` grid, select `Is Published` filter option on the `Is Published` column to show all published packages. +1. For each published package version: + * Select the package. + * 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 + * Click `Create New Version` then click `Save` and wait for the new version to be created. + * 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. + * 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. + +## Delete Old Execution Services + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues.{{< /alert >}} + +1. Open a web browser. +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. +1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution`. +1. For all old execution applications: + * Click on the drop down menu and select `Delete Application`. Confirm application deletion by following the on-screen instructions. + * Give this a few minutes. If the application does not delete: + * Expand `Nodes` + * For each node: + * Expand the node and select the application that matches the engine version number of the application that is being attempted to be deleted. + * Expand each level up to and including `Code Packages`. + * Click on the drop down menu for `Code` and select `Restart`. Confirm application restart by following the on-screen instructions. + * Give this a few minutes. Once all nodes have been restarted the application should be deleted and disappear from the list of applications. + +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. ## Preserve installation files diff --git a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md index bd510b2b2..2d32c13df 100644 --- a/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md +++ b/content/en/docs/2024.9/Guides/upgrade-cortex/2024.7-to-2024.9/single-server-without-ha/upgrade-web-application-server.md @@ -26,9 +26,22 @@ This guide describes how to upgrade {{% ctx %}} Gateway from 2024.7 to 2024.9. P {{< section "/upgrade/2024.9/upgrade-web-application-server/run-gateway-script.md" >}} -## Delete old execution service - {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues. This step should not be required in future upgrades.{{< /alert >}} -{{< section "/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md" >}} +## Delete Old Execution Service + {{< 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 cleanup of the NServiceBus endpoint and RabbitMQ queues.{{< /alert >}} + +1. Open a web browser. +1. Navigate to `https://server.domain.com:9080/Explorer`, where `server.domain.com` is the fully qualified domain name of the server. Replace `9080` with new `httpGatewayEndpointPort` value if it was changed during configuration of the original installation. +1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution`. +1. For all old execution applications: + * Click on the drop down menu and select `Delete Application`. Confirm application deletion by following the on-screen instructions. + * Give this a few minutes. If the application does not delete: + * Expand `Nodes` + * For each node: + * Expand the node and select the application that matches the engine version number of the application that is being attempted to be deleted. + * Expand each level up to and including `Code Packages`. + * Click on the drop down menu for `Code` and select `Restart`. Confirm application restart by following the on-screen instructions. + * Give this a few minutes. Once all nodes have been restarted the application should be deleted and disappear from the list of applications. + ## Preserve installation files diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md deleted file mode 100644 index 01a34a339..000000000 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/delete-old-execution-services.md +++ /dev/null @@ -1,12 +0,0 @@ - -1. Navigate to the service fabric explorer in a web browser. -1. Expand `Cluster` then `Applications` then `Cortex.Innovation.Execution`. -1. For all old execution applications: - * Click on the drop down menu and select `Delete Application`. - * Give this a few minutes. If the application does not delete. - * Expand `Nodes` - * For each node: - * Expand the node and select the application that matches the engine version number of the application that is being attempted to be deleted. - * Expand each level up to `Code Packages`. - * Click on the drop down menu for `Code` and select `Restart`. - * Give this a few minutes. The application should be deleted and disappear from the list of applications. diff --git a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md b/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md deleted file mode 100644 index 8cf2dbe0f..000000000 --- a/content/en/docs/2024.9/_shared/upgrade/2024.9/upgrade-web-application-server/republish-packages.md +++ /dev/null @@ -1,12 +0,0 @@ - -1. Log in to Gateway with a user that has the `Admin` role. -1. Click on the `Admin` charm, then `Packages`. -1. In the `Package Definitions` grid, select `Is Published` filter option on the `Is Published` column to show all published packages. -1. For each published package version: - * Select the package. - * 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. See [Troubleshooting][] for more information. - * Click `Create New Version` then click `Save` and wait for the new version to be created. - * 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. See [Troubleshooting][] for more information. - * 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. - -[Troubleshooting]: {{< url path="Cortex.Reference.Troubleshooting.Upgrade.TroubleshootingDuringUpgrade" >}}