DAP Does Not Populate XML Tag Parameters
Last updated on SEPTEMBER 12, 2017
Applies to:Oracle Communications Convergent Charging Controller - Version 6.0.1 and later
Information in this document applies to any platform.
Oracle Communications Convergent Charging Controller (OC3C) Data Access Pack (DAP) provides the capability to send requests to external Application Service Providers (ASP) and optionally receive responses for further processing by the IN platform.
In order to build those requests messages DAP populates an eXtensible Markup Language (XML) formats (Over HTTP or HTTPS), there is an issue when constructing a message, DAP correctly finds and replaces tag parameters during substitution, but does not actually update them in the outgoing message.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms