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

Summary

Details

Page properties
Content
... ... @@ -21,24 +21,8 @@
21 21  
22 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 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-starting-point.png]]
24 +[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-deploy-possibilities-group-deployment-step.png]]
25 25  
26 -{{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}}
27 -
28 -Once on the "Advanced" tab, you must define the group name. You can determine the group name if this is the first flow you change. In all subsequent flows, you want to add to the same group, you must use the **same** group name.
29 -
30 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-define-group-name.png]]
31 -
32 -Once filled in, ensure that the auto startup configuration is set to Yes to ensure that, on default, all flows within the group start up when the container is started.
33 -
34 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-define-auto-startup.png]]
35 -
36 -Within a runtime context, you can add multiple groups that can be stopped and started separately from each other. In this example, we would also like to have a group for our exits to stop them if the connecting system undergoes maintenance or is down to store the messages in the queue.
37 -
38 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-starting-point-exit.png]]
39 -
40 -[[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-other-group.png]]
41 -
42 42  == 4. Failover Deployment Step ==
43 43  
44 44  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.