XML Notification Not Sent and DAP Interface (dapIF) Reports "ERROR: XML request template ID xxxx contains invalid destination URL" Message
(Doc ID 1315165.1)
Last updated on FEBRUARY 18, 2019
Oracle Communications Network Charging and Control - Version 3.1.0 and later Information in this document applies to any platform.
DAP (Data Access Pack) provides the capability to send requests to external ASPs (Application Service Provider) and optionally receive responses. Amongst other things, DAP can trigger:
XML (eXtensible Markup Language) over HTTP(S) (HyperText Transfer Protocol)
SOAP (Simple Object Access Protocol) over HTTP(S)
It can therefore interact with external servers using XML or SOAP formatted messages.
The dapIF (DAP Interface) is responsible to accept DAP requests and triggers and handles the external communication over HTTP(S). Requests to an ASP are based on a DAP template. These originate from an ACS (Advanced Control Services) Control Plan, using the DAP ACS Feature Node:
Send Request: allows ACS to send DAP requests to a DAP interface for forwarding to an external ASP
DAP Request: allows ACS to select, configure and then send DAP requests to a DAP interface for forwarding to an external ASP
The ASP definition configures the URL to be connected, and dapIF parses that URL to make sure it is valid before it initiates the connection.
The dapIF process is a SLEE (Service Logic Execution Environment) interface and typically uses:
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!