Databases Reference
In-Depth Information
</property>
<propertyname="oracle.composite.faultBindingFile">
oramds:/apps/com/rubiconred/obay/fltmgmt/fault-bindings.xml
</property>
This has a number of distinct advantages. Firstly, you can share fault polices across
multiple composites. Secondly, if you need to modify your fault policies, you simply
need to update a single copy of your fault policy and redeploy it to MDS.
When deploying an updated version of the fault policy it will
NOT
be able to automatically pick up by any composite that uses it. Rather,
you need to either re-deploy the composite or restart the server.
Fault policy and binding files are deployed to MDS in an identical way to XML
Schemas, as covered in
Chapter 11
,
Designing the Service Contract
.
Human intervention in Fusion Middleware
Control Console
To manage composites suspended pending human intervention, we need to log
into the Fusion Middleware Control Console in Enterprise Manager. Once logged
on, browse to the
Faults and Rejected Messages
tab. This, by default, will list all
faults, if you select the checkbox
Show only recoverable faults
(shown in the next
screenshot). This will list all recoverable faults, as shown in the following screenshot:
