Changing Runtime NGW Configuration Overwrites Original Configuration File
(Doc ID 2323978.1)
Last updated on NOVEMBER 02, 2017
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Information in this document applies to any platform.
On all versions of Oracle Communications Convergent Charging Controller (OC3C), Notification Gateway (NGW) is a Java application responsible for converting Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) notifications into Simple Object Access Protocol (SOAP) messages for Open Services Development (OSD).
OSD will then trigger Control Plans in Advanced Control Services (ACS) to implement any desired service logic. By default, a notification is delivered to a handset.
Runtime configuration changes can be made to NGW (the complete list of runtime parameters can be found in the NGW Technical Guide) through Java Management Extensions and NGW will automatically back up the configuration file when changes are written. However if two or more sets of changes are made, the original configuration is lost.
For example, out of the box, this is the delivered configuration file:
bash-4.2$ ls -lrth etc/config.xml*
-rw-r--r-- 1 acs_oper esg 3.5K Nov 1 19:22 etc/config.xml
After making changes through JMX, the original config.xml is copied to config.xml.12125:
-rw-r--r-- 1 acs_oper esg 3.5K Nov 1 19:22 etc/config.xml.12125
-rw-r--r-- 1 acs_oper esg 3.5K Nov 1 20:40 etc/config.xml
If another change is made, the original configuration in config.xml are lost forever (original file with timestamp "Nov 1 19:22"):
-rw-r--r-- 1 acs_oper esg 3.5K Nov 1 20:40 etc/config.xml.12125
-rw-r--r-- 1 acs_oper esg 3.5K Nov 1 20:41 etc/config.xml
Runtime configuration changes to NGW.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!