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

Property Common values (the list is incomplete for brevity; extend it with your values, but avoid redundancy)

Put your own requirements here. We suggest (and actually have it implemented in our design) that we perform an unconditional
audit on the edges south and north. The BPEL Audit level is set to Prod. Logging for errors is mandatory. The External Audit
log DB is implemented for data consolidation and maintaining vendor neutrality; it is available for external monitoring tools as
well as for BAM. Common Audit sources include COMPOSITE_INSTANCE , CUBE_INSTANCE , and DLV_MESSAGE . Add
your own sources. The External Audit facility is probably the most common homebrew application. The main rule is the con-
sistency of unified log records, for instance, services-initiators on north should provide log records containing "START ..", not
"starting" or null; similarly, for ultimate receiver: "END", not "stopped" or "exit."

Logging/
Audit re-
quirements
for function-
al monitor-
ing

Canonical expression can be applied here. As an error occurs in a framework when a certain operation is performed by a com-
ponent that assumes a certain role, the combination of these three codes could be quite logical. Mapping to/from external code
will require an extra column.

Error code

The list is not complete. Add your own descriptors with extra care for services with external exposure. Descriptions based on
the application Canonical Expression pattern could be as follows:

Error de-
scription

• Transformation EBM2ABM failed

• Requested business data is invalid

• Unable to find XML routing slip (EP) for response flow

The list is not complete. This information is for the Audit log, not for the SOAPFault message. Make it clear that this will be
the basis for your ops teams' actions. Every new reason discovered during the exploitation must be diligently added to the fol-
lowing list:

Possible
reasons

Cannot correlate message, message structure is invalid, execution plan XML is not according to XSD or missing XDK error,
Invalid Audit message input, JMS queue as an Audit service is unavailable, Audit MDB is malfunctioned, Audit service is
down, Audit DB is down, and so on.

The following list is not complete:

Resolutions

Abort, ErM Notification, AbortSilently, RetryOperation, and Recover

List is not complete:

Resolution
scope

OSB PS, SCA BPEL, Custom Java, Network Infrastructure

This position together with the next one will set requirements for the response time:

Severity

Low, Moderate, High, or Critical

Probability Low, Moderate, or High

The structure of the spreadsheet with the initial data we mentioned in the preceding table
is a balanced scorecard (see the next figure, step 2 ), which is divided into several tabs for
every framework. It contains the logical outcome for a combination: service + performed
operation + position in technical infrastructure + process step (this is the service role). The