Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 19.1
edited by Erik Bakker
on 2024/03/01 13:28
Change comment: There is no comment for this version
To version 25.1
edited by Erik Bakker
on 2024/03/29 13:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,7 +1,7 @@
1 1  {{container}}
2 2  {{container layoutStyle="columns"}}
3 3  (((
4 -eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. The effect is that you can later in [[Deploy>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-flow-configuration.WebHome||target="blank"]], control them as one entity. This is mainly beneficial when faced with substantial maintenance or outage of systems connected to your eMagiz model.
4 +eMagiz flows, or more specifically, the flow's inbound component(s), can be grouped. The effect is that you can later in [[Deploy>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.Grouping and Failover.intermediate-grouping-and-failover-deploy-possibilities.WebHome||target="blank"]], control them as one entity. This is mainly beneficial when faced with substantial maintenance or outage of systems connected to your eMagiz model.
5 5  
6 6  Building on this functionality, you can even configure the group to run in an active/passive failover mode when you activate the multiple runtimes option on your runtime, and each separate runtime is deployed on another machine. The failover functionality is not only relevant in cases of server maintenance. It can also assist you when you want to exchange data with a system that allows only one active connection. Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).
7 7  
... ... @@ -53,10 +53,14 @@
53 53  
54 54  == 3.3 Failover Infra ==
55 55  
56 -The configuration of the infra flow of the runtime for which you want to configure the failover is detailed and only works if you configure all support objects correctly. Although we explain the various steps in the documentation, we advise utilizing the store item we created for this that will guide you in setting this up correctly.
56 +The configuration of the infra flow of the runtime for which you want to configure the failover is detailed and only works if you configure all support objects correctly. Although we explain the various steps in the documentation, we advise utilizing the [[store item>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]] we created for this that will guide you in setting this up correctly.
57 57  
58 58  The configuration consists of at least three separate support objects. Two are needed once (infinispan cache manager and clustered lock registry), whereas the other is required per unique group you have defined within the context of your runtime. So, if you have two unique group names within the runtime, you need two leader initiator support objects.
59 59  
60 +{{info}}When using this configuration across multiple runtimes on the same machines you need to take the following into account.
61 + * Each container needs a different port to communicate through. This can be configured by adding a [[route>>doc:Main.eMagiz Academy.Microlearnings.Intermediate Level.eMagiz Cloud Management.intermediate-emagiz-cloud-management-routes.WebHome||target="blank"]] in Deploy Architecture
62 + * Each container needs their own cluster. This can be achieved by providing unique names for the cluster when configuring the Infinispan Cache Manager (via the [[store item>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]]){{/info}}
63 +
60 60  === 3.3.1 Infinispan Cache Manager ===
61 61  
62 62  Given this, let us first look at the Infinispan cache manager. You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "infinispan cache manager."
... ... @@ -71,6 +71,11 @@
71 71  
72 72  [[image:Main.Images.Microlearning.WebHome@grouping-and-failover--intermediate-grouping-and-failover-flow-configuration-cache-manager-advanced.png]]
73 73  
78 +{{warning}}Please note the following when configuring the values for the host and other host address(es):
79 +* The relevant values in case of running on-premise should be requested internally with your infrastructure provider
80 +* The relevant values in case of running in the cloud can be requested via eMagiz
81 +* The "Other host addresses" value **needs** to include a reference to the port through which both hosts communicate.{{/warning}}
82 +
74 74  === 3.3.2 Clustered Lock Registry ===
75 75  
76 76  Now that we have the cache manager, we can configure the next support object on our list, the clustered lock registry. You can add this support object in the [[standard manner>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-support-objects-introduction||target="blank"]] by searching for "lock registry."