Error Handling For BRM CM
Last updated on JULY 24, 2017
Applies to:Oracle Communications Billing and Revenue Management - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 7.4.0 to 7.5.0]
Information in this document applies to any platform.
We need to have the ability to :
1. Using a trace signal (without restarting CM) to trace the Input Flists for a given API and the response time in a separate object/log file
2. Log the input flist for all the error API's. Currently if you look at the logs without level 3 logs its highly difficult to debug what the problem is in production environment.
3. Ability to execute an API with a flag which will make it like a CALC ONLY MODE to capture the logs without committing the transaction so that we can check what the problem is in production. We should not commit the trans as if its an order transaction or CSR trans, it should come through the self-care channels to handle the cross reference data.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms