Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
Hide last authors
Erik Bakker 10.1 1 {{container}}
2 {{container layoutStyle="columns"}}
3 (((
Erik Bakker 43.1 4 eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. Configuring 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.
eMagiz 1.1 5
Erik Bakker 43.1 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 relevant not only in cases of server maintenance but also in that it can 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).
Erik Bakker 14.1 7
Erik Bakker 43.1 8 This microlearning will focus on configuring the deployment plan to control various inbound components in a typical group and failover configuration.
Erik Bakker 14.1 9
Erik Bakker 43.1 10 If you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].
eMagiz 1.1 11
12 == 1. Prerequisites ==
13
14 * Intermediate knowledge of the eMagiz platform
15
16 == 2. Key concepts ==
17
Erik Bakker 43.1 18 This microlearning describes how to configure (parts of) your deployment plan to set up the grouping and, if needed, the failover functionality. The grouping functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists and allows you to have a fallback option on an active connection.
eMagiz 1.1 19
Danniar Firdausy 46.2 20 == 3. Deploy Possibilities ==
21 === 3.1. Group Deployment Step ===
eMagiz 1.1 22
Erik Bakker 43.1 23 To configure a Group deployment step, add a new one and choose Step type "Group". More information is required to configure the step. A container should be selected for which the inbounds will be stopped. The second requirement is the **exact** name of the group that should be affected by the deployment step. An action should be picked for the selected group. The options for a "Group" deployment step are to start or stop the inbound components within the group. Optionally, a description can be added.
Erik Bakker 11.1 24
Bouke Reitsma 27.1 25 [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
Erik Bakker 14.1 26
Erik Bakker 43.1 27 {{info}}Note that when you activate the stop action in a failover setup (on the leader container), it will trigger the failover behavior on the follower container{{/info}}
Bouke Reitsma 37.1 28
Danniar Firdausy 46.2 29 == 4. Key takeaways ==
eMagiz 1.1 30
Erik Bakker 17.1 31 * Grouping is beneficial when external systems go through maintenance or downtime.
Danniar Firdausy 46.11 32 * 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.
Bouke Reitsma 34.1 33 * The role naming in both grouping and failover is crucial. The group name needs to match **exactly** to make it work.
Bouke Reitsma 41.1 34 * You can control group and failover steps from the deployment plan.
35 * Container inbounds can have a different failover status.
eMagiz 1.1 36
Danniar Firdausy 46.2 37 == 5. Suggested Additional Readings ==
eMagiz 1.1 38
Danniar Firdausy 46.3 39 If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links:
40
Danniar Firdausy 46.8 41 * [[eMagiz Store (Menu)>>doc:Main.eMagiz Store.WebHome||target="blank"]]
42 ** [[Accelerators (Navigation)>>doc:Main.eMagiz Store.Accelerators.WebHome||target="blank"]]
43 *** [[Active/Passive Failover (Explanation)>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]]
Carlijn Kokkeler 44.1 44 * [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
45 ** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
Carlijn Kokkeler 46.1 46 *** [[Deploy a release (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-execute-deployment-plan-gen3.WebHome||target="blank"]]
Danniar Firdausy 46.4 47 *** [[Setting up a deployment plan (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-setup-deployment-plan-gen3||target="blank"]]
Danniar Firdausy 46.9 48 * [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
Danniar Firdausy 46.6 49 ** [[Grouping and Failover (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.WebHome||target="blank"]]
50 *** [[Flow Configuration (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]]
Danniar Firdausy 46.4 51 * [[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"]]
52
53 )))
Erik Bakker 10.1 54 (((
55 {{toc/}}
56 )))
57 {{/container}}
58 {{/container}}