New Relocatable PI FIFO Location Functionality
(Doc ID 2227261.1)
Last updated on MARCH 23, 2022
Applies to:Oracle Communications Network Charging and Control - Version 4.3.0 to 22.214.171.124.0 [Release 4.3 to 12.0.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) up to and including 126.96.36.199, the Provisioning Interface (PI) is an interface which runs on the Service Management Server (SMS) which accepts requests to perform tasks such as provisioning new subscribers, recharging accounts, checking subscriber details etc.
When the PI needs to communicate with the NCC Voucher Wallet Servers (VWS'), it uses a First In First Out (FIFO) queue which is hardcoded to reside in: /IN/service_packages/PI/tmp/fifo
In most circumstances this does not pose any problems with the performance of the PI. However, while Oracle does not recommend this, it is possible to have the /IN filesystem mounted as a Network File Share (NFS) mount. As a result, any TCP/IP network latency will add significant latency to all PI commands which require VWS interaction.
All subsequent requests will also appear "slow" as the PIprocesses are blocked while they wait for a response from the PIbeClient (which doesn't receive the request in a timely manner due to the aforementioned network latency).
If PI commands are received from the network faster than they can be processed, then the observed latency from the PI client's perspective is exacerbated as the request will also sit in the local TCP/IP stack's send/receive buffers.
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