ECE BRS Configurations Are Not Persistent
(Doc ID 2546884.1)
Last updated on MAY 03, 2021
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Elastic Charging Engine (ECE) BatchRequestService (BRS) is the ECE charging client layer embedded in the ECE CustomerUpdater, Diameter Gateway (DGW), Oracle Communications Offline Mediation Controller (OCOMC ECE-DC), RadiusGW, Simulator, and SDK programs. Tuning parameters such as batchSize, threadPoolSize, and others can be changed during the run time, but they are not persisted after every client restart, and same parameters need to be tuned again. Refer to Elastic Charging Engine 11.3 System Administrator's Guide "Configuring Overload Protection" paragraph.
Is it possible for each client to have a dedicated configuration file, so that any change in their attributes to be persistent?
This enhancement will improve the Operational Procedures and will reduce the risk of error.
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