My Oracle Support Banner

Every Interaction With BRM Via BCD Results In 3 Warnings To The Syslog. (Doc ID 2370630.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Communications Convergent Charging Controller - Version 6.0.1 to 12.0.0.0.0 [Release 6.0 to 12.0.0]
Information in this document applies to any platform.

Symptoms

On Oracle Communications Convergent Charging Controller (OC3C) version 6.0.1 the interaction with Oracle Communications Billing and Revenue Management (BRM) is done through the BRM Charging Driver (BCD) component. All Convergent Charging Controller access to BRM and BRM data is done through the BRM Portal Communications Module (PCM) API.

The BCD Client uses the Portal Communications Module (PCM) API to set up connections to the BRM Connection Managers and to send and receive messages over the BRM Portal Communications Protocol (PCP). The BCD Client uses a connection pooling mechanism with load balancing and fail-over to communicate with multiple BRM nodes.

 

In case one of the fields coming from BRM is not mapped in BCD, every interaction with BRM via BCD results in a warnings to the syslog:

 

Cause

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
Symptoms
Cause
Solution
References


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