Some Date Formats Are Not Supported by DAP
(Doc ID 1579697.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Communications Network Charging and Control - Version 4.0.0 and later
Oracle Solaris on SPARC (64-bit)
In all current versions of NCC (Network Charging and Control), DAP (Data Access Pack) has limit support for parsing ISO 8601 date formats. This is used in DAP to convert date strings returned by an ASP (Application Service Provider) into a date profile tag. Here is an example of the DAP Operation Response configuration required to extract a date string from the returned XML and store it into a DATE type profile tag (aptly named DATE in this example):
For more information on how to use this screen, please refer to the DAP User/Technical Guide.
Currently, only two date string formats are supported:
In other words, basic format only with no support for date only formats, time only formats or timezone offsets.
When formats other than the two aforementioned formats are used, the DAP2 macro node will fail and the following will be written to slee_acs debug:
2013/06/14 02:10:49 sendRequestInternal.cc 41  dapMacroNodes void dap::ConversionInterface::fromString(const std::string&, dap::MemoryBuffer&, unsigned int) const
2013/06/14 02:10:49 sendRequestInternal.cc 42  dapTypeDetail From '2013-07-06' (10 bytes)
2013/06/14 02:10:49 defaultTypes.cc 184  dapTypeConversion Conversion failed - exception: bad lexical cast: source type value could not be interpreted as target
2013/06/14 02:10:49 sendRequest.cc 825  dapMacroNodes Conversion Failed - Conversion to date failed
2013/06/14 02:10:49 sendRequest.cc 136  dapMacroNodes Asked to exit down branch Problem
Due to this limitation, DAP is not able to correctly integrate with ASPs which return date strings which DAP does not handle.
Attempts to return date strings from an ASP to DAP.
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