Skip to Content

Changes for page Failover - Configuration

Last modified by Erik Bakker on 2024/09/27 14:06
From version 28.12
edited by dfirdausy
on 2024/09/25 16:19
Change comment: There is no comment for this version
To version 28.10
edited by dfirdausy
on 2024/09/25 12:39
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -33,7 +33,7 @@
33 33  
34 34  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-design-architecture.png]]
35 35  
36 -Once you applied 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 keeping track of the existing group names in which runtime containers are part of those groups, and routing the communication between two runtimes (e.g., lead and backup runtimes) to inform when one of the runtimes joins a group (e.g., starting up) or leaves a group (e.g., being non-active).
36 +Once you applied 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 37  
38 38  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-routers.png]]
39 39