Changes for page Failover - Deploy Possibilities

Summary

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

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-Setting up Failover - Create Phase
	1	+Setting up Failover - Deploy Phase

Content

...	...	@@ -2,7 +2,7 @@
2	2	{{container layoutStyle="columns"}}
3	3	(((
4	4
5		-In the previous microlearning, we discussed what situation that failover mode will be beneficial as well as the settings that need to be configured in the Design phase. Next to that, we also discussed that setting up this failover functionality in your model requires you to first execute some steps in your Design, Create, and lastly Deploy phase. Picking up from what we have discussed previously in the Design phase, in this microlearning, we will focus on configuring your setup in the Create phase if you want to activate the active/passive failover configuration.
	5	+In the previous microlearning, we discussed what needs to be done in the Create phase to enable failover for systems that are configured to have them in the Design phase. Next to that, we also discussed that setting up this failover functionality in your model requires you to execute some steps in your Design, Create, and lastly Deploy phase. Picking up from what we have toggled in the Create phase, in this microlearning, we will focus on the steps and configurations that you have to make in the Deploy phase to activate the active/passive failover functionality.
6	6
7	7	Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
8	8
...	...	@@ -12,30 +12,26 @@
12	12
13	13	== 2. Key concepts ==
14	14
15		-This microlearning describes what configuration that you will have to do in the Create phase, based on what you have configured in the Design phase, to enable failover for systems connecting with your model. The grouping and failover functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists in that case and allows you to have a fallback option on an active connection.
	15	+This microlearning describes what configuration that you will have to do in the Deploy phase, based on what you have configured in the Design and Create phase, to enable failover for systems connecting with your model. The grouping and failover functionality is relevant when faced with maintenance and outages of systems connected to your model. The failover functionality assists in that case and allows you to have a fallback option on an active connection.
16	16
17		-== 3. Create Phase Configuration ==
	17	+== 3. Deploy Phase Configuration ==
18	18
19		-== 3.1 Settings ==
	19	+== 3.1 Deploy Architecture ==
20	20
21		-After finishing up your configuration in the Design phase, you can then go to the Settings page on the top right corner of the Create phase. In this page, under the "Failover systems" tab in the "Transfer settings from design" section, you will find the system connector(s) that you can transfer the failover settings from Design.
	21	+After finishing up your configuration in the Create phase, you can then move to your Deploy>Architecture. Here, you will see the new router containers, which we have seen in the Design>Architecture, to be added to your external machines. When you press "Start Editing" in this page, and then press "Apply to environment", you will be faced with a pop-up page that informs you that these router containers will be created for this specific environment as shown in the screenshot below.
22	22
23		-[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-create-phase-create-settings.png]]
	23	+[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-router-containers.png]]
24	24
25		-{{info}}Systems with the failover option enabled must have "Number of runtimes" exactly 2 and must be placed on an external machine in the Architecture panel.{{/info}}
	25	+Once you have applied the changes, if you go to the "Details" of each of those machines via right-cliking them, then you can find and set, for each failover runtime, the preferred machine to be the leader. As an example shown in the screenshot below, there are two runtimes that are enabled for failover and you can select whether that runtime running in that "External 01" machine is the preferred leader or the backup, or if you want to reset it back to "None".
26	26
27		-== 3.2 Design Architecture ==
	27	+[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-preference.png]]
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	+When you have made your decision, and assuming that your machines are already deployed and running, then you can move to the other page discussed in the next section.
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	+== 3.2 Deployment Plan ==
34	34
35		-[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-design-phase-routers.png]]
	33	+== 3.3 Deploy Release ==
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.
38		-
39	39	== 4. Key takeaways ==
40	40
41	41	* Grouping is beneficial when external systems go through maintenance or downtime.