Changes for page R21 - Double lane
Last modified by Erik Bakker on 2025/06/30 09:54
From version 17.1
edited by Carlijn Kokkeler
on 2024/01/18 11:42
on 2024/01/18 11:42
Change comment:
There is no comment for this version
To version 18.1
edited by Erik Bakker
on 2025/06/30 09:54
on 2025/06/30 09:54
Change comment:
There is no comment for this version
Summary
-
Page properties (3 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -R2 0- Double lane1 +R21 - Double lane - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. CarlijnKokkeler1 +XWiki.ebakker - Content
-
... ... @@ -1,19 +1,17 @@ 1 - Non-service affectingR20template that improvesauto healing.More information on whatautohealinginvolvescanbefound [[here>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Fundamentals/fundamental-emagiz-cloud-inner-workings||target="blank"]].1 +**Service affecting** template to use the R21 single lane release. 2 2 3 3 **Process** 4 - WeupgradeinonestepsetheR20release ofthe cloud template. Thisstepisnon-service affecting.4 +To use the new R21 template on your environment, we replace all connections to activate the new configuration. This update is service affecting and aims to enable data traffic via our new carwash. 5 5 6 6 **Overview** 7 - Thisversioncontainsautohealingperformanceimprovements.7 +* New connections to a **new** carwash. 8 8 9 -**Updates** 10 -* Update including auto healing performance improvements. 11 -* This upgrade is non-service affecting. 12 - 13 13 **Update Steps** 14 -* Use the final template (non-service affecting) 10 +* Use the final template (service affecting)(duration: < 10 minutes) 11 +** This step will replace all connections. 12 + 15 15 * User actions after applying the final template: 16 -** Check if all runtimes are rea chablebyDeploy Architecture.17 -** Check if all flows have been installed according to the active release.18 -** Check if messages pass through the model by verifying a critical message flow in external systems .14 +** Check if all runtimes are up via the runtime dashboard or Deploy Architecture 15 +** Check if all runtimes have been installed according to the active release 16 +** Check if messages pass through the model by verifying a critical message flow in external systems 19 19