Changes for page Failover - Configuration

Last modified by Erik Bakker on 2024/09/27 14:06

From version 28.15

edited by Danniar Firdausy
on 2024/09/25 17:12

Change comment: There is no comment for this version

To version 28.18

edited by Danniar Firdausy
on 2024/09/26 09:30

Change comment: There is no comment for this version

Summary

Page properties

Content

@@ -41,10 +41,10 @@
  == 4. Key takeaways ==
--* Grouping is beneficial when external systems go through maintenance or downtime.
--* 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.
--* The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work.
--* For the infra configuration of the failover setup, we have a store item that you can use.
++* The inbound components of eMagiz flows can be grouped, allowing for centralized control, particularly beneficial during system maintenance or outages.
++* By enabling multiple runtimes across different machines, you can configure groups to operate in active/passive failover mode, ensuring continued operation during connection failures, system maintenances, or outages.
++* Setting up the failover functionality requires configuration in the Design phase, where you enable multiple runtimes and set up failover options in both the Solution Design and Architecture sections.
++* In the Design Architecture, router containers are added to manage communication between the lead and backup runtimes, ensuring smooth transitions when a failover runtime becomes inactive or joins a group.
  == 5. Suggested Additional Readings ==