Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.71
edited by Danniar Firdausy
on 2024/09/25 17:05
Change comment: There is no comment for this version
To version 28.66
edited by Danniar Firdausy
on 2024/09/25 16:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -18,14 +18,11 @@
18 18  
19 19  == 3.1 Deploy Architecture ==
20 20  
21 -After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture. Here, you will see the new router containers, which we have seen in the Design>Architecture, to be added to your external machines. When you press "Start Editing" in this page, and then press "Apply to environment", you will be faced with a pop-up page that informs you that these router containers will be created for this specific environment as shown in the screenshot below.
21 +After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture. Here, you will see the new router containers, which we have seen in the Design>Architecture, to be added to your external machines.
22 22  
23 23  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-router-containers.png]]
24 24  
25 -Once you have applied the changes, if you go to the "Details" of each of those machines via right-cliking them, then you can find and set for each failover runtime the preferred machine to be the leader. As an example shown in the screenshot below,
26 26  
27 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-preference.png]]
28 -
29 29  == 4. Key takeaways ==
30 30  
31 31  * Grouping is beneficial when external systems go through maintenance or downtime.