Billing Care Should Segregate The Configuration From The CustomWar File
(Doc ID 2745957.1)
Last updated on JANUARY 25, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
On Oracle Communications Billing and Revenue Management (BRM), 188.8.131.52.0 version, Billing Care,
Billing Care should segregate the configuration from the customWar file
Currently to change any configuration like pcm.connection.timeout, one need to build custom WAR file. The same needs to be deployed in Billing Care domain. This always gives a wrong impression to the Customer whenever they are not doing any customization or modification to the Graphical User Interface (GUI).
This needs an improvement, might be separate properties file in the domain similar to Business Operation Center (BOC) configurations, where user need to segregate all the configurations which does not need any custom code change, so that for any configuration they don't have to build any custom-war file.
Billing Care should have a complete configuration file for which there should not be any custom-war file to be built. The configuration file should be deployed in the Billing Care domain and the domain should use those configurations. This will improve the product from a maintenance perspective and Release management will be much more easier.
One need to build custom-war file to deploy any configuration change
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