Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.91
edited by Danniar Firdausy
on 2024/09/26 10:46
Change comment: There is no comment for this version
To version 28.89
edited by Danniar Firdausy
on 2024/09/26 10:44
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -44,7 +44,7 @@
44 44  
45 45  == 3.3 Trigger Failover ==
46 46  
47 -Once you have successfully deployed and run your release with the failover connector runtimes, then you can observe the follower and leadership status of your failover connector runtimes in your Deploy>Architecture. There, if you right-click your external machines (which have the failover connector runtimes) and select [["Start/Stop flows" (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]], under the "Groups" tab, you will find the "Group name", "Failover status", as well as the "State" the connector runtime is in at the moment (whether it is now On or Off). See the screenshot below as an example.
47 +Once you have successfully deployed and run your release with the failover connector runtimes, then you can observe the follower and leadership status of your failover connector runtimes in your Deploy>Architecture. There, if you right-click your external machines (which have the failover connector runtimes) and select "Start/Stop flows", under the "Groups" tab, you will find the "Group name", "Failover status", as well as the "State" the connector runtime is in at the moment (whether it is now On or Off). See the screenshot below as an example.
48 48  
49 49  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-start-stop.png]]
50 50  
... ... @@ -52,7 +52,6 @@
52 52  
53 53  == 4. Key takeaways ==
54 54  
55 -* 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.
56 56  * In the Deploy>Architecture section, users can configure the router containers and set preferred machines for failover runtime leadership. This ensures that systems are prepared to handle failover scenarios.
57 57  * If users assigned the failover IP addresses and Ports properties as global properties, users must configure a "Balance failover" deployment step to trigger the failover container(s) to be running on its preferred machine as you previously configured them in Deploy>Architecture.
58 58  * After deployment, users can monitor the failover status, including leadership roles, in Deploy>Architecture, and can manually switch between active (Leader) and backup (Follower) runtimes if needed.
... ... @@ -61,9 +61,6 @@
61 61  
62 62  If you are interested in this topic and want more information, please read the help text provided by eMagiz and check out these links:
63 63  
64 -* [[Intermediate Level (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.WebHome||target="blank"]]
65 -** [[eMagiz Runtime Management (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.WebHome||target="blank"]]
66 -*** [[Start/Stop Flows (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Runtime Management.intermediate-emagiz-runtime-management-start-stop-flows.WebHome||target="blank"]]
67 67  * [[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"]]
68 68  )))
69 69  (((