|
Problem(Abstract) |
Best practice method for implementing exception handling
in the IBM® WebSphere® Application Server V5.0 Process Choreographer. |
|
|
|
Cause |
Best practice exception handling for process
choreographer. |
|
|
Resolving the
problem |
Non-interruptible processes, or microflows, are very fast and used for
straight-through processing. They are executed in memory as a single
transaction and have a small footprint. Therefore, microflows should be
used whenever possible.
For exception handling, the best practice recommendation is to execute the
main process as a very fast microflow and to call an interruptible
process, or macroflow for the error handling whenever an exception is
thrown. The macroflow is called using a one-way operation and can be used
to do corrective activities or to involve staff activities to handle the
error.
The macroflow for exception handling can be called as a sub-process or
invoked as a service. In either case, the microflow is completed before
the macroflow is started.
This is a good pattern to follow when most of the processing is
error-free, but people are still needed to handle the exceptions. |
|
|
|
|
|
|