Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.56
edited by Danniar Firdausy
on 2024/09/25 15:55
Change comment: There is no comment for this version
To version 28.36
edited by Danniar Firdausy
on 2024/09/25 14:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -28,18 +28,13 @@
28 28  
29 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.
30 30  
31 -The first setting that eMagiz configures for you takes place in the connector infra flow of the system that you enable for failover from the previous step. 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. From the screenshot below, you can see that eMagiz, by default, will give the "Cluster name" in the Infinispan Cache Manager as {{code}}failover-<system technical name>{{/code}}. 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. eMagiz also automatically provides the "Role" name in this support object. It will be filled in with the same value as the "Cluster name" later when you have moved to the Deploy phase (e.g., {{code}}failover-xctnln{{/code}} in the example below).
31 +The first setting that eMagiz configures for you takes place in the connector infra flow of the system that you enable for failover from the previous step. 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. From the screenshot below, you can see that for the example that we have so far, eMagiz by default will give the "Cluster name" as {{code}}failover-<system technical name>{{/code}}.
32 32  
33 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-connector-infra.png]]
34 34  
35 -The second setting that eMagiz configures for you happens in the exit and entry flows that are connected to that system. Here, eMagiz configures for you (parts of) your flow(s) with the required setting to enable grouping for the failover functionality on the flow level. The configurations for grouping consist of the "Group" name and "Auto startup", which are available for all inbound components. See the screenshot below as an example of an inbound component that has its "Group" name and "Auto startup" configured by eMagiz automatically when enabling the failover functionality.
34 +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.
36 36  
37 -{{info}}The grouping functionality here is relevant when faced with maintenance and outages of systems connected to your model.{{/info}}
36 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-connector-infra.png]]
38 38  
39 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-exit-entry.png]]
40 -
41 -Again, in this part, you do not have to make any changes yourself. Once you are satisfied with the settings that eMagiz has configured for you, then you are finished in the Create phase and can move on to the Deploy phase that will be discussed in the next microlearning.
42 -
43 43  == 4. Key takeaways ==
44 44  
45 45  * Grouping is beneficial when external systems go through maintenance or downtime.