For partners that build or integrate commercially available applications and service solutions with the Oracle Cloud Platform
For partners that provide implementation or managed services around Oracle Cloud Applications
Hi,
My scheduled OIC integration has HCM adapter which is enabled for 'Subscribe to Atom Feeds' option. It is subscribed for employee new hire feed. The integration is scheduled for every 4 mins. For every schedule the current timestamp is captured and passed as parameter for Atom Feed.
Scenario:
In my first 3 runs I get zero response from atom feed. Consider in my 4th run my atom feed captures a new record (person created between 3rd and 4th run timestamp) say employee #124. Again in my 7th run the feed captures another new employee (#125). So my integration should do nothing in the runs except 4 and 7.
But atom feed captures #124 in runs 5 and 6. In my 7th run #125 is captured and replaces the previous response. Why is the response not getting replaced according to each run?
Comment
Hi,
ATOM Feed feature works based on the query parameters sent to the HCM ATOM service.
Is the integration saving the timestamp of last entry processed and using the saved timestamp in the next request/run ?
Please refer to following doc:
https://docs.oracle.com/en/cloud/paas/integration-cloud/hcm-adapter/subscribe-atom-feeds-scheduled-integration.html#GUID-B31360CF-2BA6-4A5B-88E2-DB3969917CA5
Be the first to rate this
|
Sign in to rate this
Is the integration saving the timestamp of last entry processed and using the saved timestamp in the next request/run ? - YES
For every run, the time stamp will get updated.
Be the first to rate this
|
Sign in to rate this
There is one more difference in the way ATOM feed is processed by adapter vs postman. To avoid missing entries/updates few records towards the end of the feed are skipped and they are included in the next run.
https://docs.oracle.com/en/cloud/paas/integration-cloud/hcm-adapter/avoid-missing-entries-while-processing-tthem-page-wise.html
Please enable payload tracing for the flow and check the timestamp sent to the ATOM service. The timestamp will be of the last entry processed, but it may not be the last entry in the feed due to above mentioned reason.
Average Rating:



1 rating
|
Sign in to rate this
According to atom feed functionality, request id 10002675 should fetch zero records. Thats my issue.
Average Rating:



1 rating
|
Sign in to rate this
The issue got solved by mapping the updated min of the record to schedule parameter and using that for next run. Below document solved the issue
https://docs.oracle.com/en/cloud/paas/integration-cloud/hcm-adapter/subscribe-atom-feeds-scheduled-integration.html#GUID-B31360CF-2BA6-4A5B-88E2-DB3969917CA5
Be the first to rate this
|
Sign in to rate this
Hi,
Could you please share the "updated_timestamp" and "published_timestamp" of record #123 ?
There is no caching of records in HCM adapter. HCM Adapter sends the timestamps as query parameter to the ATOM service and processes the records returned by the service.
If you use the the same timestamps in query parameters and invoke the ATOM service directly via POSTMAN, you will get the same results.
Be the first to rate this
|
Sign in to rate this