Skip to Content
Last modified by Danniar Firdausy on 2024/09/27 09:18
From version 24.1
edited by Bouke Reitsma
on 2024/03/01 15:25
Change comment: There is no comment for this version
To version 26.1
edited by Bouke Reitsma
on 2024/03/01 15:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -15,14 +15,12 @@
15 15  
16 16  == 2. Key concepts ==
17 17  
18 -This microlearning describes how to configure (parts of) your flow(s) to set up the grouping and, if needed, the failover functionality on the flow level. The grouping 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.
18 +This microlearning describes how to configure (parts of) your deployment plan to set up the grouping and, if needed, the failover functionality. The grouping 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.
19 19  
20 -== 3. Flow Configuration ==
20 +== 3. Group Deployment Step ==
21 21  
22 -== 3.1 Grouping ==
22 +To configure a Group deployment step, you need to add a new deployment step and choose Step type "Group". To configure the step more information is required. A container should be chosen for which the inbounds will be stopped. The second requirement is the **exact** name of the group that should be affected by the deployment step. An action should be picked for the selected group. For a "Group" deployment step the options are to start or to stop the inbound components within the groupname. Optionally, a description can be added.
23 23  
24 -To configure grouping, we need to open the flow designer of the flow in Create. We want to edit and enter "Start Editing" mode. On the inbound component(s) in the flow, we now have an "Advanced" tab that allows you to configure the grouping information.
25 -
26 26  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-starting-point.png]]
27 27  
28 28  {{info}}Note that the options above are available in all inbound components. The one chosen above is simply an illustration of how to configure.{{/info}}
... ... @@ -41,7 +41,7 @@
41 41  
42 42  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-other-group.png]]
43 43  
44 -== 3.2 Failover ==
42 +== 4. Failover Deployment Step ==
45 45  
46 46  If you want to expand the grouping functionality to include an active/passive failover component, you need to change the settings on the inbound component. Apart from specifying the group name, you need to configure the auto-startup option on "No" so the failover configuration can take the correct actions in all situations.
47 47  
... ... @@ -91,7 +91,7 @@
91 91  
92 92  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-leader-initiator-basic.png]]
93 93  
94 -== 4. Key takeaways ==
92 +== 5. Key takeaways ==
95 95  
96 96  * Grouping is beneficial when external systems go through maintenance or downtime.
97 97  * Failover can have the additional benefit of having a fallback scenario while still adhering to the requirement that there can only be one active connection at a time
... ... @@ -98,7 +98,7 @@
98 98  * The role naming in both grouping and failover is crucial. The whole name needs to be matched fully to make it work.
99 99  * For the infra configuration of the failover setup, we have a store item that you can use.
100 100  
101 -== 5. Suggested Additional Readings ==
99 +== 6. Suggested Additional Readings ==
102 102  
103 103  There are no suggested additional readings for this microlearning.)))
104 104  (((