Runtime Fault Handling with the Fault Management Framework

Fault handling allows a SOA suite component to handle error situations caused by outside web services. The error situations can be both business (e.g. invalid data value) and runtime faults (service unavailable). I’m aiming to handle business fault as much as possible in the composite (catch) while handle runtime faults outside the composite.
In the remaining of this blog I will describe an implementation of the Fault Management Framework to handle runtime faults.

I have implemented the following policy:
1) RemoteFault (invocation of a service fails)

  • Start a retry cycle
    standaard retryCount:                 5
    standaard retryInterval:              300 (seconden)
    standaard exponentialBackoff:   2
    Retry will take place after 5, 10, 20, 40 en 80 minutes.
  • If it still fails, start a human intervention

2) All other unhandled (runtime) faults

  • Start a human intervention

Continue reading

SOA Suite 11g: set the Composite Instance title with a Mediator component

In this blog I will describe how to set the composite title with a Mediator component. I will also describe where this approach matches and where it differs from setting the title with a BPM or BPEL component.

Lets first start with an overall important match: you need the setCompositeInstanceTitle function. This function sets the composite instance title and returns it. The return value brings us to the biggest difference: the assignment of the return value. In BPMN and BPEL you must assign the return value to a variable. In Mediator you must assign it to a property.

This post shows the Mediator approach. In parallel posts I show the BPM and BPEL approach.

Continue reading