How Can Suspense CDRs Written by OCOMC be Shared with REL in a Cloud Native Environment?
(Doc ID 2824020.1)
Last updated on JUNE 26, 2024
Applies to:
Oracle Communications Billing and Revenue Management - Version 12.0.0.3.0 and laterInformation in this document applies to any platform.
Goal
In an Oracle Communications Billing and Revenue Management (BRM) Cloud Native (CN) deployment, the shipped configuration does not support the ability for the suspense Call Data Records (CDRs) written by Oracle Communications Offline Mediation Controller (OCOMC) pod to be shared with the Rated Event Loader (REL) pod.
By default, the OCOMC pod configuration defines the following Persistent Volume Claims (PVCs):
- admin-server-pvc
- node-manager-pvc
- vol-keystore
- vol-data
- vol-external
- vol-suspense
Whereas the REL pod configuration defines:
- oms-rel-input
- oms-rel-archive
- oms-rel-reject
- oms-rel-input-{{ add1 $_ }}
- oms-rel-archive-{{ add1 $_ }}
- oms-rel-reject-{{ add1 $_ }}
What is the recommended approach to share the suspense CDRs between these 2 pods?
Solution
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
Goal |
Solution |