Unlock new patterns of integration by controlling the HTTP Response status in OIC REST based integrations by Anuj Kaushal

Integration flows with a REST based trigger can be called using any HTTP client. In this blog post we illustrate how an integration developer can control the HTTP response code from within the integration flow and how doing so can unlock interesting patterns of integration.

By default, REST based integration flows return the following HTTP response status:

-       HTTP 200 (OK) in case of success

-       HTTP 202 (Accepted) in case of Asynchronous flows.

-       HTTP 4xx in case of client side errors like calling the integration flow with the wrong method or URL etc.

-       HHTP 5xx or user-defined in case of failures during the integration flow but with a fixed error format.

The integration developer needs to assign the HTTP response status code from the mapper as follows: This option provides a number of possibilities to integration developers, few applications of which are:

1.     Return a redirect (3xx) code.

-       There exist several re-direct codes that have specific meaning. For instance method forwarding is usually performed by some clients only when the status code is 307. While in some cases a POST is always redirected as a GET (PRG) to avoid double posts. When a web form is submitted to a server through an HTTP POST request, attempts to refresh the server response can cause the contents of the original POST to be resubmitted, possibly causing undesired results, such as a duplicate insert. Read the complete article here.

PaaS Partner Community

For regular information on Oracle PaaS become a member in the PaaS (Integration & Process) Partner Community please register here.

Blog Twitter LinkedIn Facebook Wiki

Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress