Account Rolled Back in BRM Commited in ECE
(Doc ID 2286409.1)
Last updated on AUGUST 06, 2018
Applies to:Oracle Communications BRM - Elastic Charging Engine - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Customer data management
Using AIA, BRM, and ECE, the BRM eai_js has been configured to publish the account creation into both ECE's EMGateway and AIA's AQ_SYNC.
When creating an account which got published into ECE's Cache via emGateway, but it was failed when publishing it into AIA's AQ_SYNC. Therefore, the account was rolled back in BRM, but it wasn't rolled back in ECE. As result, there were an account in ECE's cache that did not exist in BRM.
1. Configure eai_js to publish account creation event into DM_AQ and ECE EMGateway DB
2. Start emGateway, stop DM_AQ, change aq_names files to use an invalid queue, start DM_AQ
3. Create an account in BRM, the account will be created at ECE, it will fail at DM_AQ and rolled back at BRM, but not rolled back at ECE
Should not the account be rolled back from ECE's Customer Cache as well?
As the event AccountStatusUpdate is shared between EAI_JS DBs, if an account is set inactive or closed in BRM, it will be closed at ECE and then if the operation fails in the other EAI_JS DB, it will remain open at BRM but closed at ECE. Is that correct?
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