ActiveBPEL™ Designer User’s Guide
This is an ActiveBPEL extension activity. When you save the process, a message appears informing you that the process contains an activity that is not in the BPEL specification.
The suspend activity suspends a running process. This activity is useful for catching unexpected faults to allow manual intervention for viewing and correcting errors. The optional variable attribute can be used to attach data to an alert which both automatic and programmatic suspends can trigger.
In ActiveBPEL Enterprise, you can perform process exception management on a suspended process. On the ActiveBPEL Enterprise server, you can conveniently view the location of a faulting activity.
|
Required Properties |
Optional Properties |
|---|---|
|
none |
Name. See Selecting Activity Labels |
|
Variable |
|
|
Join Condition. See Creating a Join Condition for an Incoming Link |
|
|
Suppress Join Failure. See Process Properties |
|
|
Comment. See Adding Comments to a Process |
|
|
Documentation. See Adding Documentation to a Process |
|
|
Setting Visual Properties and Using Your Own Library of Images |
|
|
Execution State. See Viewing the Execution State of an Activity or Link |
|
|
Extension Attributes and Extension Elements. See Declaring Extension Elements and Attributes. |
To build a suspend activity:
The following illustration shows an example of using the suspend activity.

<suspend variable="NCName"? standard-attributes>
standard-elements
</suspend>
Example
<catchAll>
<extensionActivity>
<ext:suspend/>
</extensionActivity>
</catchAll>
Copyright (c) 2004-2007 Active Endpoints, Inc.