Changes for page Failover - Deploy Possibilities
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.110
edited by Danniar Firdausy
on 2024/09/27 08:55
on 2024/09/27 08:55
Change comment:
There is no comment for this version
To version 28.112
edited by Danniar Firdausy
on 2024/09/27 08:56
on 2024/09/27 08:56
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -42,11 +42,13 @@ 42 42 43 43 == 3.3 Deploy Release == 44 44 45 -Once you have configured your Deployment Plan, then it is time to create a new release for your updated flows in the Deploy>Release page. As you might have noticed in the Deploy>Architecture earlier when opening the "Failover" tab in your machines' "Details", there are properties regarding the machines' "Internal IP address" and "Failover port". It is then becomesnatural thatyou first need to fill in these property values in the environment that you are working on at the moment (i.e., Testing, Acceptance, Production). If you are unsure on how to do this, please refer to this [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] microlearning.The idea here is that you fill in the IP address and the (open) port of the external machines. Thus, based on the example in the screenshot above, you can search for the keyword "external01.failover.internal-ip" and then select it. Afterward, you can set this property as global for simplicity and fill in the correct value. Once you have done so, then you can do the same for the other property (i.e., "external01.failover.port") and as well as the properties for the second machine.45 +Once you have configured your Deployment Plan, then it is time to create a new release for your updated flows in the Deploy>Release page. As you might have noticed in the Deploy>Architecture earlier when opening the "Failover" tab in your machines' "Details", there are properties regarding the machines' "Internal IP address" and "Failover port". Thus, you first need to fill in these property values in the environment that you are working on at the moment (i.e., Testing, Acceptance, Production). If you are unsure on how to do this, please refer to this [[Property Management>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-deploy-property-management-new.WebHome||target="blank"]] microlearning. 46 46 47 +The idea here is that you fill in the IP address and the (open) port of the external machines. Thus, based on the example in the screenshot above, you can search for the keyword "external01.failover.internal-ip" and then select it. Afterward, you can set this property as global for simplicity and fill in the correct value. Once you have done so, then you can do the same for the other property (i.e., "external01.failover.port") and as well as the properties for the second machine. 48 + 47 47 [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-failover-properties.png]] 48 48 49 -When you are done, then you can save your changes, and proceed with creating a new release. For this, you will need to create a new release from your "Create phase", in orderto include all configurations that eMagiz has provided in your now failover-enabled Create phase. Once you have done this, give the release a name and save it, then you can proceed with activating the release and deploy it.51 +When you are done, then you can save your changes, and proceed with creating a new release. For this, you will need to create a new release from your "Create phase", to include all configurations that eMagiz has provided in your now failover-enabled Create phase. Once you have done this, give the release a name and save it, then you can proceed with activating the release and deploy it. 50 50 51 51 == 3.3 Trigger Failover == 52 52