
Implementing Oracle Integration Cloud Service
By :

We have seen how to use WSDL based endpoints for filtering and routing integrations, but how would the filter integration look and behave if we replaced the trigger with a REST connector and a JSON payload? While it should be possible to achieve the same integration, what does a REST connector look like that provides the two-way behavior we mentioned on the WSDL source? Is the mapping impacted at all by the fact we are receiving a JSON payload now? Our filter condition has also been a lot simpler, so we should try a more complex filter.
While we look at these points, we also have the opportunity to examine a couple of other important ideas such as CORS, which we have not yet seen in previous example integrations. This integration should look as follows: