Taking Care – Error Handling - Applied SOA Patterns on the Oracle Platform - page 494

Go on, break these rules, and see what will happen. The severity of consequences
will depend on the complexity of your compositions, from mess in static until dis-
aster in dynamic. The best outcome would be to park every fault for manual resol-
ution, which is far from optimal. Again,these rules are for the implementation of
an agnostic Composition Controller. For static task-orchestrated processes the
standard OFM Fault Management Framework will suffice and for this type of im-
plementation please follow the rules 3, 4, 11, 12, and 13. We also have to mention
that this list can be extended with your own rules, as we could have the design
variation on south, around Adapter Factory.
Also, please bear in mind that we will use the rule numbers (from 1 to 15) all the
way in this chapter. The number 15 will be some kind of magical number here,
because at the end we will see how 15 design rules refer to 15 main Audit event
sources.
From top to bottom, one rule is leading to the next, thus summarizing all the preceding 15
rules and SOA patterns (presented in bold) around Preventive Error Managing (rule 15).
We can extend the SOA infrastructure diagram from Chapter 7 , Gotcha! Implementing Se-
curity Layers (related to security, the first figure), with all the layers—the sources of mon-
itoring information, required for proactive management and automated recovery:
Technical and Functional monitoring flows in a typical SOA infrastructure