Functionality Missing For Retrying Web Service Payloads In Service Contracts
(Doc ID 2389408.1)
Last updated on MAY 14, 2018
Applies to:Oracle Fusion Enterprise Contracts Management Cloud Service - Version 11.13.17.09.0 and later
Information in this document applies to any platform.
On : 220.127.116.11.0 version, Contract Authoring
Functionality Missing for Retrying Web Service Payloads in Service Contracts
Here is an approach we will be pursuing for creating Sales Orders, in OM Cloud, and how we are planning to handle reprocessing failures:
1. Initiate Create Sales Order web service in real-time mode
2. If the web service returns an error, we are retry the same web service in batch mode.
3. The batch mode allows the order to be staged so it can be imported with an ESS process. This is important because the sequencing of master data may not have occurred properly. For example, the customer or item may not have arrived yet. When it does, we can simply submit an ESS job to process the staged data instead of having to re-trigger the data from the source system. Re-triggering the data from a source is not alway a viable solution.
4. We will be using Redhat Fuse (based on Camel) to call the web service for real-time processing. Fuse will resend the payload again for a failure, but with batch mode selected.
BTW, we have asked the OM development team (via an enhancement request) to enhance the Sales Order creation web service to have a re-processing flag. So, if the real-time payload fails then automatically send the payload to a staging table for reprocessing if the flag is set. This eliminates the need for us to re-trigger the payload.
Please consider adding this as a common approach for SaaS cloud web services and not just Service Contracts.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!