Coherence Federation Topology for Active-hot Standby ECE Configuration
(Doc ID 2652512.1)
Last updated on MARCH 30, 2020
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
A user has two Elastic Charging Engine (ECE) sites configured in an active-hot standby configuration. The current configuration in the coherence-override file does not define the topology, i.e. the user is currently having an active-active configuration, per said documentation. The Disaster Recovery documentation for ECE only mentioned to define the participants, yet not the topology.
Is it required to define a topology in the coherence-override file for an active-hot standby configuration?
Could it be causing ECE to duplicate or corrupt data in the active site or the passive site, if not having the said topology defined in the coherence-override file?
Does ECE need to have an active-active Coherence topology? Would it be best to add it explicitly on the coherence-override file, or is it best to leave the configuration as is?
What exactly tells the passive cluster that it is read-only? Is there a parameter that determines this?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document