Blog Posts Process Management Service Oriented Architecture (SOA)

Jarvis Pizzeria blog refresh part 2 of 3 by Marcel van de Glind

Blog: PaaS Community

In this blog I do a quick refresh of the second 13 Jarvis Pizzeria blog posts
(note: the different headers in this blog contain a link to the actual blog).

14. Using an imported XSD in PCS

In this post we make an attempt to use an imported XSD containing a complex type in a web form. It is possible to ‘use’ the type, but things are not working very well (as described in the blog). In the current version (19.3.2) this works even less good. It is no longer possible to save the web form. The following error appears.

At various places in OIC the tooling has quite a bit of trouble with data types, and that in particular with complex data types but also with simple data types, not everything goes smoothly. These are generally not insurmountable issues, but in my opinion Oracle still has some work to do.

15. Testing in PCS against the Development or Production environment

In this post, testing in PCS is discussed for both the test and the production modes. In an earlier post we have already shown how a PCS process can be started from postman via a rest call (Using the REST interface to start a Process).
In this blog we show how this rest call must be adjusted to distinguish between a call in test or production modes. In a nutshell: we need to set the ‘pcs_mode’ param in the request header and give it the value ‘dev’.

16. Handling SOAP Faults in PCS

In this blog post we show how PCS deals with SOAP errors in the following two situations: the out of the box fault policies ON and OFF.

Are there any scenarios conceivable where a developer should turn off the fault policies? The disadvantage of turning on fault-policies is that the fault policies are turned on for the entire application. If one – for whatever reason – wants to build a proprietary error handling framework than this feature should be turned off.

For example, in the situation that an email has to be sent to one of our customers (like an order confirmation), and the process fails for some reason we do not want to use the retry policy of the default error handling, because that could mean that we send the same email 4 times to the customer. Isolating such functionality in a separate dedicated application is preferred in this case. 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