My Oracle Support Banner

How to Configure Round Robin Load Balancing from DAP to the PI (Doc ID 2527604.1)

Last updated on OCTOBER 14, 2019

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.0 and later
Oracle Communications Network Charging and Control - Version 4.3.0 and later
Information in this document applies to any platform.

Goal

On all versions of Oracle Communications Network Charging and Control (OCNCC or NCC) and Oracle Communications Convergent Charging Controller (OC3C or 3C), Data Access Pack (DAP) is a module on the Service Logic Controllers (SLCs) and Voucher Wallet Servers (VWS') responsible invoking web services on a provider.

The Provisioning Interface (PI) on the Service Management Server (SMS) just so happens to be a web service provider.

Due to the architecture of NCC/3C, it is possible for the DAP interfaces (dapIF) on the SLCs to overwhelm the PI process (PIprocess) listening on a port.  This is due to the scalability of dapIF (at least 1 per SLC) versus the lack of scalability of the PIprocesses (1 single threaded process per port). Depending on how DAP is set up, this may cause timeouts not only between DAP and the PI, but also any external traffic that is triggering the SLCs.

This article will cover a method of scaling the PIprocess' to reduce the chances of overloading.

This article assumes there is already (at least) a single web service configured between DAP and the PI.

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
 Configuring Additional PI Ports
 Add a New DAP ASP/Operation
 Introduce Round Robin Load Sharing in the Control Plan
 Further Scaling/Limitations


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.