This is an area customers often ask me about.
Firstly, when is an error re-submittable?
According to the docs -
You can manually resubmit failed messages. Resubmitting a failed message starts the
integration from the beginning.
All faulted instances in asynchronous flows in Oracle Autonomous Integration Cloud
are recoverable and can be resubmitted. Synchronous flows cannot be resubmitted.
Next question is - who do I know if my flow is asynchronous?
Again back to the docs -
Oracle Autonomous Integration Cloud does not currently allow modeling an
asynchronous request response service. However, all scheduled orchestration
patterns internally use an asynchronous request response.
However, OIC does support Fire and Forget (one-way requests).
Now you ask - how can I create a Fire and Forget interface for my OIC Integration flow?
This is relatively simple -
I use a SOAP trigger, based on a one-way wsdl.
The one way wsdl, as the name strongly suggests, does not include a response.
I then create a new SOAP Connection in OIC, based on this wsdl.
That Connection, I then use as a Trigger in the following integration -
Very minimalistic - however, suffice to know, I just invoke Service Cloud to create a new Organization.
I have guaranteed an error, by mapping the lookupName. This is not allowed, as this field in auto-generated by Service Cloud.
I deploy and test, which brings me back to the first screenshot in this post -
Resubmitting Errors
I have a new integration flow with my one-way SOAP Trigger.
This integration simply writes new organization data to a file,
via the OIC Connectivity Agent.
via the OIC Connectivity Agent.
The destination folder is on a thumb drive, plugged into my laptop.
As you can see, I already have 1 output file there.
I now remove the thumb drive and test the integration again -
The flow throws an error -
The above error message is self explanatory.
I now re-insert the thumb drive
I re-submit the error via OIC Monitoring console
I check out the folder - voilà.
No comments:
Post a Comment