Cloud REL Daemon And ECE Event Files
(Doc ID 2690835.1)
Last updated on OCTOBER 28, 2021
Applies to:Oracle Communications Billing and Revenue Management - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Qn1: There is a requirement to integrate a cloud Rated Event Loader (REL) daemon module with a native Elastic Charging Engine (ECE) application in order to publish the rated event files. REL daemon is running, but unable to identify the ECE server. Could you provide the appropriate configuration for configmap_infranet_properties_rel_daemon.yaml regarding ECE connection?
Qn2: The input Rel file location is "/ece/ocece/done/data/". This is the way events are being loaded in the local installation of 184.108.40.206.0. Is it not supported on the cloud pin rel? Why should one change ECE to point to rel location?
Qn3: Using Network File System (NFS) rel_daemon managed to read ECE events.
Filesystem 1K-blocks Used Available Use% Mounted on
<server>:/ece/ocece/done 230574080 11068416 219505664 5% /data/BRM/oms_rel_input
a. Why oms_rel_input PersistentVolumeClaim (PVC) should be in the kubernetes ?
b. Except ECE, is it possible that other processes can now write to rel input PVC ?
c. How to disable the header file from ECE? Is it possible to have only one data file per event accordingly to pin_rel logic.
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