Dehydration Process:
Dehydration is persisting the transaction in DB. This will be used as a point from which the Bpel Manager to retry the process. If there are three invoke point in a process if system restared in second invoke point and if its dehydrated then during rerunn of the instance process will start from third process instead of rerunning the first two invoke.
Durable
processes incur one or more dehydration points in the database during
execution. Dehydration is triggered by one of the following activities:
- Receive activity
- OnMessage branch in a pick activity
- OnAlarm branch in a pick activity
- Wait activity
- Reply activity
- checkPoint() within a <bpelx:exec> activity
No comments:
Post a Comment