REF Is Not Working In Active-Active Mode If DB Persistence Is Enabled
(Doc ID 2769750.1)
Last updated on APRIL 18, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Rated Event Formatter (REF) is not working in Active-Active mode if Data Base(DB) persistence is enabled
As per the proposed architecture, customer will have active-active and at the same time, Data Base(DB) persistence will be enabled.
If the DB persistence is enabled, then DB will be used for rated event flow instead of NoSQL.
With this approach, if the rated event formatter is started in both the sites, then it is generating duplicate rated events.
The rated events are federated and stored in both the database (site1 and site2). But rated event formatter is picking all rated events instead of site specific rated events.
This is creating duplicate rated events and impacting balance twice.
REF should work in segmented way. The rated event generated by site 1 should be processed by REF in site1 and usage generated in site2 should be processed by site 2 REF. Currently REF can be started only in site1 which is processing rated events of both site 1 and site 2 which is something customer is not accepting in Active-Active architecture
The issue has the following business impact:
Since the rated events federated and REF running in both the sites, both the REF picking up the same rated events and generating Rated Event Loader(REL) file. The REL file is loaded twice which impacts the Billing and Revenue Management( BRM) balance twice.
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