Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 33.1
edited by Bouke Reitsma
on 2024/03/15 09:40
Change comment: There is no comment for this version
To version 39.1
edited by Erik Bakker
on 2024/03/25 09:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.BoukeReitsma
1 +XWiki.ebakker
Content
... ... @@ -3,7 +3,7 @@
3 3  (((
4 4  eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. How to configure this is explained [[here>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]. This functionality is mainly beneficial when faced with substantial maintenance or outage of systems connected to your eMagiz model.
5 5  
6 -Building on this functionality, you can even configure the group to run in an active/passive failover mode when you activate the multiple runtimes option on your runtime, and each separate runtime is deployed on another machine. The failover functionality is not only relevant in cases of server maintenance. It can also assist you when you want to exchange data with a system that allows only one active connection. Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).
6 +Building on this functionality, you can even configure the group to run in an active/passive failover mode when you activate the multiple runtimes option on your runtime, and each separate runtime is deployed on another machine. The failover functionality is not only relevant in cases of server maintenance. It can also assist you when you want to exchange data with a system that allows only one active connection. Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).
7 7  
8 8  In this microlearning, we will focus on configuring the deployment plan to control various inbound compoments in a normal and in a failover configuration.
9 9  
... ... @@ -23,21 +23,27 @@
23 23  
24 24  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
25 25  
26 +{{info}}Note that when you activate the stop action in a failover setup (on the leader container), it will activate the failover behaviour on the follower container{{/info}}
27 +
26 26  == 4. Failover Deployment Step ==
27 27  
28 -The configuration of a failover deployment step is similar as for the Group deployment step. The only difference is the action you can activate. The stop group actions make the inbounds of the currently selected container stop. If this group is the leader of the failover group. It will deactivate this group and start orignal follower group. However, it disables failover. Therefore, from this point were are running in a dubble setup in which we have single node leaders.
30 +The configuration for a failover deployment step is the same as for the group deployment step. The only difference is the action you can activate. The stop group action stops the inbounds of the selected container. It will also disable the failover, so if a follower is configured, it will **not** take over. Instead, from this point, we are running in a standard multi-container setup in which we have single-node leaders.
29 29  
30 30  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-disabled-failover.png]]
31 31  
32 -The start group step with failover will activate the current container as the leader of the failover setup. Therefore, resembling group names on other containers will become the followers. If these flows were running, they will be stopped.
34 +The start group step with failover will activate the current container as the leader of the failover setup. Therefore, group names resembling those on other containers will become the followers. If these flows were running, they will be stopped.
33 33  
34 34  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-failover-deployment-step.png]]
35 35  
38 +=== 4.1 Failover Status Explained ===
39 +
40 +To get
41 +
36 36  == 5. Key takeaways ==
37 37  
38 38  * Grouping is beneficial when external systems go through maintenance or downtime.
39 39  * 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
40 -* The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work.
46 +* The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
41 41  * You can control group and failover steps from the deployment plan
42 42  
43 43  == 6. Suggested Additional Readings ==