Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.43
edited by Danniar Firdausy
on 2024/09/25 14:26
Change comment: There is no comment for this version
To version 28.44
edited by Danniar Firdausy
on 2024/09/25 14:26
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -28,7 +28,7 @@
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 this example).
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).
32 32  
33 33  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-connector-infra.png]]
34 34