Wiki source code of Setting up Failover - Design Phase
Version 28.8 by Danniar Firdausy on 2024/09/25 12:39
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{container}} | ||
| 2 | {{container layoutStyle="columns"}} | ||
| 3 | ((( | ||
| 4 | eMagiz flows, or more specifically, the flows' inbound components, can be grouped. The benefit from this is that you can later in [[Deploy>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]], control them as one entity. This is mainly beneficial when faced with substantial maintenance or outage of systems connected to your eMagiz model. | ||
| 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). | ||
| 7 | |||
| 8 | Setting up this failover functionality in your model requires you to first execute some steps in your Design, Create, and lastly Deploy phase. In this microlearning, we will focus on configuring your setup in the Design phase if you want to activate the active/passive failover configuration. | ||
| 9 | |||
| 10 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. | ||
| 11 | |||
| 12 | == 1. Prerequisites == | ||
| 13 | |||
| 14 | * Intermediate knowledge of the eMagiz platform. | ||
| 15 | |||
| 16 | == 2. Key concepts == | ||
| 17 | |||
| 18 | This microlearning describes how to configure (parts of) of your Design phase to enable failover for systems connecting with your model. The grouping and failover functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists in that case and allows you to have a fallback option on an active connection. | ||
| 19 | |||
| 20 | == 3. Design Phase Configuration == | ||
| 21 | |||
| 22 | == 3.1 Solution Design == | ||
| 23 | |||
| 24 | To configure failover for systems that are connecting with your model, we first need to go to the Design phase. In your Design>Solution Design, find and open the details of the system that you want to enable failover for. Once you do that, then you need to make sure that "Multiple runtimes" option is selected for this system, which is logical since we want to have a second runtime running in case of failover situations (e.g., outage, maintenance, etc.). Afterward, you will see the "Number of runtimes" and "Run in failover" fields. To enable failover, make sure that you fill in 2 as the "Number of runtimes", before selecting the "Run in failover" checkbox. See the screenshot below as an example. | ||
| 25 | |||
| 26 | [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-solution-design.png]] | ||
| 27 | |||
| 28 | {{info}}Systems with the failover option enabled must have "Number of runtimes" exactly 2 and must be placed on an external machine in the Architecture panel.{{/info}} | ||
| 29 | |||
| 30 | == 3.2 Design Architecture == | ||
| 31 | |||
| 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 | |||
| 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 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 | [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-routers.png]] | ||
| 39 | |||
| 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 | |||
| 42 | == 4. Key takeaways == | ||
| 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. | ||
| 48 | |||
| 49 | == 5. Suggested Additional Readings == | ||
| 50 | |||
| 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 | |||
| 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 | * [[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 | ))) | ||
| 66 | ((( | ||
| 67 | {{toc/}} | ||
| 68 | ))) | ||
| 69 | {{/container}} | ||
| 70 | {{/container}} |