Skip to Content
Last modified by Erik Bakker on 2024/09/27 14:07
From version 24.1
edited by Erik Bakker
on 2024/03/29 13:47
Change comment: There is no comment for this version
To version 23.1
edited by Erik Bakker
on 2024/03/29 13:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -57,10 +57,6 @@
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 [[store item>>doc:Main.eMagiz Store.Accelerators.Active-Passive Failover.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 -
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."