Skip to Content

Changes for page Failover - Configuration

Last modified by Erik Bakker on 2024/09/27 14:06
From version 28.8
edited by Danniar Firdausy
on 2024/09/25 12:39
Change comment: There is no comment for this version
To version 28.17
edited by Danniar Firdausy
on 2024/09/26 09:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -32,9 +32,9 @@
32 32  Once the previous step is done, the next step is to configure your Design>Architecture. Here, you first need to "Start Editing" and then press "Apply settings" on your bottom left corner. Afterward, you will be faced with a pop-up page informing you that failover will be enabled on the system connector containers that you have previously toggled in Design>Solution Design (see the screenshot below as an example).
33 33  
34 34  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-design-architecture.png]]
35 +
36 +Once you applied the changes, then your Design>Architecture in that environment, will get new router containers placed in your external machines (see the screenshot below as an example). These router containers are responsible for keeping track of the existing group names (in which, runtime containers set to failover are part of those groups) and routing communication between two runtimes (e.g., lead and backup). Next to that, they also facilitate the communication between runtimes when a runtime joins a group (e.g., during startup) or leaves a group (e.g., when becoming inactive).
35 35  
36 -Once you apply the changes, then your Design>Architecture, in that environment, will get new router containers placed in your external machines (see the screenshot below as an example). These router containers are responsible for ... .
37 -
38 38  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-routers.png]]
39 39  
40 40  When you have done that and satisfied with your landscape configuration, then you are finished in the Design phase and can proceed to the next configuration in the Create phase.
... ... @@ -41,26 +41,15 @@
41 41  
42 42  == 4. Key takeaways ==
43 43  
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.
44 +* The inbound components of eMagiz flows can be grouped, allowing for centralized control, particularly beneficial during system maintenance or outages.
45 +* 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.
46 +* 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.
47 +* 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.
48 48  
49 49  == 5. Suggested Additional Readings ==
50 50  
51 51  If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links:
52 52  
53 -* [[eMagiz Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]]
54 -** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]]
55 -*** [[Active/Passive Failover (Explanation)>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]]
56 -* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
57 -** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
58 -*** [[Support objects - Introduction (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]]
59 -*** [[Promote flows to deploy (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-promote-flows-to-deploy||target="blank"]]
60 -* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]]
61 -** [[Grouping and Failover (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]]
62 -*** [[Deploy Possibilities (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]]
63 -** [[eMagiz Cloud Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.WebHome||target="blank"]]
64 64  * [[Failover (Search Results)>>url:https://docs.emagiz.com/bin/view/Main/Search?sort=score&sortOrder=desc&highlight=true&facet=true&r=1&f_space_facet=0%2FMain.&l_space_facet=10&f_type=DOCUMENT&f_locale=en&f_locale=&f_locale=en&text=%22Failover%22||target="blank"]]
65 65  )))
66 66  (((