Some Date Formats Are Not Supported by DAP

(Doc ID 1579697.1)

Last updated on SEPTEMBER 08, 2013

Applies to:

Oracle Communications Network Charging and Control - Version 4.0.0 and later
Oracle Solaris on SPARC (64-bit)

Symptoms

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:

YYYYMMDDTHHMMSSZ (eg. 20130828T111300Z)

 and:

YYYYMMDDTHHMMSS (eg. 20130828T111300)

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            sendRequest.cc  2151 [18444]        dapMacroNodes    Converting from string to  DATE
2013/06/14 02:10:49    sendRequestInternal.cc    41 [18444]        dapMacroNodes    void dap::ConversionInterface::fromString(const std::string&, dap::MemoryBuffer&, unsigned int) const
2013/06/14 02:10:49    sendRequestInternal.cc    42 [18444]        dapTypeDetail    From '2013-07-06' (10 bytes)
2013/06/14 02:10:49           defaultTypes.cc   184 [18444]    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 [18444]        dapMacroNodes    Conversion Failed - Conversion to date failed
2013/06/14 02:10:49            sendRequest.cc   136 [18444]        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.

Changes

Attempts to return date strings from an ASP to DAP.

Cause

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