Changes for page Failover - Configuration
Last modified by Erik Bakker on 2024/09/27 14:06
From version 28.20
edited by Danniar Firdausy
on 2024/09/27 09:24
on 2024/09/27 09:24
Change comment:
There is no comment for this version
To version 28.15
edited by Danniar Firdausy
on 2024/09/25 17:12
on 2024/09/25 17:12
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -Failover - Configuration1 +Setting up Failover - Design Phase - Content
-
... ... @@ -41,10 +41,10 @@ 41 41 42 42 == 4. Key takeaways == 43 43 44 -* The inbound components of eMagizflowscanbegrouped, allowing for centralizedcontrol, particularlybeneficialduringsystem maintenance or outages.45 -* By enabling multipleuntimesacrossdifferentmachines, you canconfigure groupstooperatein active/passivefailovermode,ensuringcontinuedoperationduringconnectionfailures, systemmaintenances,or outages.46 -* Setting up thefailoverfunctionality requiresconfiguration in theDesign phase, where youenable multiple runtimesandset upfailoveroptions inboththeSolution DesignandArchitecturesections.47 -* IntheDesignArchitecture,routercontainers are added to manage communicationbetweenthe leadand backupruntimes, ensuringsmoothtransitions whenafailoverruntimebecomesinactiveorjoinsa group.44 +* Grouping is beneficial when external systems go through maintenance or downtime. 45 +* 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. 46 +* The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work. 47 +* For the infra configuration of the failover setup, we have a store item that you can use. 48 48 49 49 == 5. Suggested Additional Readings == 50 50