Changes for page Failover - Deploy Possibilities
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.95
edited by Danniar Firdausy
on 2024/09/26 16:18
on 2024/09/26 16:18
Change comment:
There is no comment for this version
To version 28.96
edited by Danniar Firdausy
on 2024/09/26 16:19
on 2024/09/26 16:19
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -37,7 +37,6 @@ 37 37 To make sure that this functionality works correctly, then this step should be placed at the end of your deployment plan (i.e., after the deployment of all runtimes and ensure that all of the failover connector runtimes are up and running). See the screenshot below as an example. 38 38 39 39 [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-deployment-plan.png]] 40 - 41 41 == 3.3 Deploy Release == 42 42 43 43 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 becomes natural that 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).