Changes for page Failover - Configuration
Last modified by Erik Bakker on 2024/09/27 14:06
From version 27.5
edited by Danniar Firdausy
on 2024/09/13 09:32
on 2024/09/13 09:32
Change comment:
There is no comment for this version
To version 27.8
edited by Danniar Firdausy
on 2024/09/25 10:59
on 2024/09/25 10:59
Change comment:
Update document after refactoring.
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - Flow Configuration1 +intermediate-grouping-and-failover-setting-up-failover-design-phase - Content
-
... ... @@ -103,12 +103,14 @@ 103 103 == 4. Key takeaways == 104 104 105 105 * Grouping is beneficial when external systems go through maintenance or downtime. 106 -* Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time 106 +* Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time. 107 107 * The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work. 108 108 * For the infra configuration of the failover setup, we have a store item that you can use. 109 109 110 110 == 5. Suggested Additional Readings == 111 111 112 +If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links: 113 + 112 112 * [[eMagiz Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]] 113 113 ** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]] 114 114 *** [[Active/Passive Failover (Explanation)>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]]