Repairing BPEL processes and activities using Business Process Choreographer Explorer
If a BPEL process runs into problems, you can analyze the process and then repair the activities.
About this task
Business Process Choreographer Explorer provides various views for the process administrator to monitor the processes that are currently running.
The failure behavior of your process
is controlled by the Continue On Error setting
of the process template. If Continue On Error is
set to no, any unexpected failure causes the affected
activity to go to the stopped state.
If Continue
On Error is set to yes (or if it is not
set because your process was created with a WebSphere® Integration
Developer version earlier than 6.1.2) and an unexpected failure occurs,
the default fault handler is invoked and ultimately causes the process
to end in a failed state. The latter happens because with an unexpected
failure there is no appropriate fault handler in the directly surrounding
scope. When there is no explicit fault handler defined for the current
fault and the default fault handler is invoked, it terminates the
current scope and propagates the fault to the surrounding scope. Ultimately,
this will cause the process to end in the failed state.
For
invoke, Java snippet, human task, and custom activities you can model
a dedicated Continue On Error setting and override
the process setting. However, if you leave the default value the same
as for the process, you can repair failure situations for these activity
types. The setting at the activity level controls only the behavior
of faults that are generated by the implementation of the activity.
Faults that occur during the evaluation of the join condition, or
during the evaluation of the transition condition of outgoing links
are still controlled by the setting at the process level. Therefore,
for example, an invoke activity can go to the stopped state (if, for
example, the evaluation of its join condition failed) even if the Continue
On Error setting at the activity level is set to yes.
If your activity stops, the process remains in the running state. You then have several options in Business Process Choreographer Explorer to repair the process and continue navigation.
Procedure
- To view process instances with activities in the stopped state, define your own process instance search. Or, click Stopped Activities under Activity Instances in the navigation pane, and then click the relevant process instance of the failed activity.
- To view process instances with activities in the stopped state, click Critical Processes under Process Instances in the navigation pane.
- To monitor the progress of a specific process instance, click View Process State in any view that displays a list of process instances.
What to do next
You can now take action to repair the pending activities.