RollingUpgrade Action Results In Unnecessary Changes To Configuration File "charging-settings.xml" (Doc ID 2065737.1)

Last updated on SEPTEMBER 20, 2016

Applies to:

Oracle Communications BRM - Elastic Charging Engine - Version 11.2.0.5.0 to 11.2.0.5.0 [Release 11.2.0]
Information in this document applies to any platform.

Symptoms

On : ECE 11.2.0.5.0 version,

Issue :

After performing a rollingUpgrade action , it is observed that the configuration file "charging-settings.xml" gets modified, resulting in ECE charging node not starting successfully.

Steps to reproduce :

  1. open file charging-settings.xml and make following changes (add an extra rumgroup):

    from :


    <productConfigurationGroup config-class="java.util.ArrayList">
                   <productConfiguration
                           config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.ProductConfiguration"
                           type="TestProduct">
                       <rumConfigurationGroup config-class="java.util.ArrayList">
                           <rumConfiguration
                                   config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.RumConfiguration"
                                   rum="TestRum" minAuthorizedQuota="1.0" initialQuota="100.0" incrementalQuota="50.0"
                                   unit="Seconds"/>
                       </rumConfigurationGroup>
                   </productConfiguration>
               </productConfigurationGroup>


    to:

    <productConfigurationGroup config-class="java.util.ArrayList">
                   <productConfiguration
                           config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.ProductConfiguration"
                           type="TestProduct">
                       <rumConfigurationGroup config-class="java.util.ArrayList">
                           <rumConfiguration
                                   config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.RumConfiguration"
                                   rum="TestRum" minAuthorizedQuota="1.0" initialQuota="100.0" incrementalQuota="50.0"
                                   unit="Seconds"/>
                       </rumConfigurationGroup>
                   </productConfiguration>
                   <productConfiguration
                           config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.ProductConfiguration"
                           type="TelcoGSM">
                       <rumConfigurationGroup config-class="java.util.ArrayList">
                           <rumConfiguration
                                   config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.RumConfiguration"
                                   rum="TestRum" minAuthorizedQuota="1.0" initialQuota="100.0" incrementalQuota="50.0"
                                   unit="Seconds"/>
                       </rumConfigurationGroup>
                   </productConfiguration>
               </productConfigurationGroup>

  2. now test rollingUpgrade as follows ( see below console output from ecc ):
     
  3. check the content of "charging-settings.xml"  

                       <productConfiguration
                            config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.ProductConfiguration" type="TestProduct">
                            <rumConfigurationGroup config-class="java.util.ArrayList">
                            <rumConfiguration
                            config-class="oracle.communication.brm.charging.appconfiguration.beans.reservation.RumConfiguration"
                            incrementalQuota="50.0"
                            initialQuota="100.0"
                            minAuthorizedQuota="1.0"
                            rum="TestRum" unit="Seconds"/>
                            </rumConfigurationGroup>
                       </productConfiguration>
                  </productConfigurationGroup>

  4. One may see either of the following issues :
    1. as seen in step 3, the additional productConfiguration that was added has been removed which is not expected
    2. another issue that might be seen is that the rumConfigurationGroup tag gets modified as below :
      <rumConfigurationGroup config-class="java.util.ArrayList">
              to
      <rumConfigurationGroup >
  5. now when restart of ece is attempted, it does not start successfully. This is the impact of the above behavior. 

 

Expected result:
After step 2, the content of the file charging-settings.xml should not get modified as noted.

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms