My Oracle Support Banner

Release Of Oracle Communications BRM Elastic Charging Engine (ECE) 12.0 (Version (Doc ID 2518119.1)

Last updated on DECEMBER 08, 2022

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version and later
Information in this document applies to any platform.


Oracle Communications Billing and Revenue Management (BRM) - Elastic Charging Engine (ECE) 12.0 (Version is released on 4 March 2019.
This announcement lists various functional and operational enhancements delivered in Oracle Communications BRM - Elastic Charging Engine (ECE) Version

Cache Persistence for Improved Resilience

The cache persistence feature provides your deployment with the following benefits:

Better resilience with cache persistence in Oracle database, dropping the dependency on NoSQL : ECE supports cache persistence to improve resilience of the charging system. You can persist customer, pricing and configuration data that are cached, into Oracle Database as a backup. The rated events are also stored into the same Oracle database eliminating the need for NoSQL database.

Superior cache management ensuring smaller memory footprint: The cache management comes with configuration of high and low watermarks, that defines offloading and fetching thresholds respectively, thus providing a mechanism to control memory growth of cache. With this you will always have a subset of data in cache. Only the recently used data is kept in the cache and least used/unused data is off-loaded from the cache. The system will load the data on-demand (lazy load) if a charging request arrives for a customer whose data was offloaded due to inactivity. This keeps the JVM size to a predictable low and makes ECE node stable, reliable and robust.

Automated cache priming for cold (full) and warm (incremental) re-starts: The first time loading of data into ECE system will be a full load from BRM, loading the data into the cache and then into Oracle database. The cache management rules apply to keep only the recently used objects complying to the configured high watermark. In the unforeseen event of a node failure or partition drop, the system detects the failure and automatically recovers the node, reloading most recently used data up to lower watermark. This restart is significantly faster compared to the earlier approach of full load of data from BRM Database.

High Availability and Disaster Recovery: You can use Oracle RAC or RAC One Node with Oracle database used as persistent store for deploying a highly available ECE system. Oracle Data Guard can be used to replicate the data across two sites for redundancy to help re-cover from any disaster to the primary site.

Secured deployments with Wallets for sensitive information: With previous releases of ECE, the boundary system passwords were stored in files in encrypted format. With ECE 12.0, the passwords are stored in Oracle Wallet, which is much more secured than files. Further it allows you to manage these passwords from JConsole interface.

During the installation of ECE you will be given a choice to choose between the new approach of Oracle DB as persistence store or the old approach of NoSQL as rated event store without cache persistence. It is recommended that you choose the new approach to leverage the above stated benefits.


ECE is certified with

Please note that the following are prerequisites for installing ECE

Important Note: Required Products in an Integrated System:
In order to use ECE, you must install following dependent Products as well.
  • Billing and Revenue Management (BRM) 12.0 Patch Set 1
  • Pricing Design Center (PDC) 12.0 Patch Set 1
  • Oracle Communications Offline Mediation Controller 12.0 Patch Set 1






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
 Cache Persistence for Improved Resilience

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.