IPSA Rest Call Response Format For Upstream (OSM)
(Doc ID 2803972.1)
Last updated on SEPTEMBER 14, 2021
Applies to:
Oracle Communications IP Service Activator - Version 7.4.0.0.0 and laterInformation in this document applies to any platform.
Goal
A recent SNO implementation required the use of a 'ReasonForFailure' message to be sent from the IPSA restApi to OSM. Prior to this only 'Success' and 'Failed' messages were being exchanged.
The 'ReasonForFailure' is transferred to the JMS queue where it is then relayed to OSM as to why the order has failed.
The JMS message now includes the 'ReasonForFailure' as well as the start and complete times from the transaction.
Example;
Failed response:
StartTime: 2021/07/12 16:22:22
Type: Transaction
Result: Failed
CompletionTime: 2021/07/12 16:22:22
ReasonForFailure: ReasonForFailure : Driver raised an unexpected exception(command: shape average 56000000 38000 / response: Configured shape BC valueresults in the interval being out of range. Allowed BC value for given CIR of 56000000 should be at least 224000. / Rollback succeeded / )
StartTime: 2021/07/12 16:22:22
Type: Transaction
Result: Failed
CompletionTime: 2021/07/12 16:22:22
ReasonForFailure: ReasonForFailure : Driver raised an unexpected exception(command: shape average 56000000 38000 / response: Configured shape BC valueresults in the interval being out of range. Allowed BC value for given CIR of 56000000 should be at least 224000. / Rollback succeeded / )
Solution
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
| Goal |
| Solution |
| References |