Changes for page Failover - Deploy Possibilities

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -22,19 +22,17 @@
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 of that system as well as update the exit and entry flows connected to that system with the required settings.
	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.
26	26
27		-== 3.2 Design Architecture ==
	27	+== 3.2 Flow Configurations ==
28	28
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).
	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		-[[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 ... .
	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, which will be filled in with the same value as the "Cluster name", i.e., {{code}}failover-<system technical name>{{/code}} later when you have moved to the Deploy phase.
34	34
35		-[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-routers.png]]
	33	+[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-connector-infra.png]]
36	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.
	35	+The second setting that eMagiz configures for you happens in the exit and entry flows that are connected to that system.
38	38
39	39	== 4. Key takeaways ==
40	40