Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.31
edited by Danniar Firdausy
on 2024/09/25 14:08
Change comment: There is no comment for this version
To version 28.23
edited by Danniar Firdausy
on 2024/09/25 13:41
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -22,14 +22,20 @@
22 22  
23 23  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-create-settings.png]]
24 24  
25 -By pressing the "Transfer failover" button, eMagiz will regenerate the connector infra flow of that system as well as update the exit and entry flows connected to that system with the required settings. We will discuss these required settings and what components are affected in the following section.
25 +By pressing the "Transfer failover" button, eMagiz will
26 26  
27 -== 3.2 Flow Configurations ==
27 +== 3.2 Design Architecture ==
28 28  
29 -As mentioned just now, by pressing that button in Create>Settings, eMagiz will configure the correct settings for you, so then you do not have to configure them manually by yourself. With that being said, this section focuses on showing you the components that are affected and keep you informed of the required components for the failover functionality to work correctly.
29 +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).
30 30  
31 -The first setting that eMagiz configure for you takes place in the connector infra flow of the system that you enable for failover. The configuration in this infra flow requires of at least three separate support objects. Two support objects will be added here, which are the Infinispan Cache Manager and Clustered Lock Registry. The other one that is also added is the Leader Initiator support object, which is required per unique group that you will have within the context of your runtime.
31 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-design-architecture.png]]
32 +
33 +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 ... .
32 32  
35 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-routers.png]]
36 +
37 +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.
38 +
33 33  == 4. Key takeaways ==
34 34  
35 35  * Grouping is beneficial when external systems go through maintenance or downtime.