Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 28.94
edited by Danniar Firdausy
on 2024/09/26 10:58
Change comment: There is no comment for this version
To version 28.93
edited by Danniar Firdausy
on 2024/09/26 10:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -30,10 +30,8 @@
30 30  
31 31  == 3.2 Deployment Plan ==
32 32  
33 -If this is the first time that you configure your failover setup, then the next step in Deploy is to check the Deployment Plan. Here, you can add a deployment step called "Balance failover", which, when executed, will trigger the failover container(s) to be running on its preferred machine as you previously configured them in Deploy>Architecture. See the screenshot below.
33 +If this is the first time that you configure your failover setup, then the next step in Deploy is to check the Deployment Plan. Here, you can add a deployment step called "Balance failover", which, when executed, will trigger the failover container(s) to be running on its preferred machine as you previously configured them in Deploy>Architecture. (Next to that, you can also find the "Group" deployment step. Discuss this step here.)
34 34  
35 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-setting-up-failover-deploy-phase-balance-failover.png]]
36 -
37 37  == 3.3 Deploy Release ==
38 38  
39 39  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).