Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 22.1
edited by Erik Bakker
on 2024/03/01 15:55
Change comment: There is no comment for this version
To version 27.1
edited by Carlijn Kokkeler
on 2024/08/09 14:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ebakker
1 +XWiki.CarlijnKokkeler
Content
... ... @@ -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||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."
... ... @@ -105,7 +105,9 @@
105 105  
106 106  == 5. Suggested Additional Readings ==
107 107  
108 -There are no suggested additional readings for this microlearning.)))
112 +* [[Crash Courses (Menu)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.WebHome||target="blank"]]
113 +** [[Crash Course Platform (Navigation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.WebHome||target="blank"]]
114 +*** [[Promote flows to deploy (Explanation)>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Platform.crashcourse-platform-create-promote-flows-to-deploy||target="blank"]])))
109 109  (((
110 110  {{toc/}}
111 111  )))