Skip to Content

Changes for page Failover - Configuration

Last modified by Erik Bakker on 2024/09/27 14:06
From version 26.1
edited by Erik Bakker
on 2024/03/29 13:51
Change comment: There is no comment for this version
To version 21.1
edited by Erik Bakker
on 2024/03/01 15:54
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,14 +53,10 @@
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>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.WebHome||target="blank"]] 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 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||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 -
64 64  === 3.3.1 Infinispan Cache Manager ===
65 65  
66 66  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."
... ... @@ -78,7 +78,7 @@
78 78  {{warning}}Please note the following when configuring the values for the host and other host address(es):
79 79  * The relevant values in case of running on-premise should be requested internally with your infrastructure provider
80 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}}
77 +* The "Other host addresses" values **needs** to include a reference to the port through which both hosts communicate with each other.{{/warning}}
82 82  
83 83  === 3.3.2 Clustered Lock Registry ===
84 84