Process editor server page reference

The server properties page displays run time information for an activity or the process as a whole.

This page will look different depending on what you are configuring the server for. You can either configure the server for the process as a whole, or for a specific activity.

Here is an alphabetical list of the options that will be available:

Continue on Error
This setting specifies how the execution of a process should proceed when an fault is not caught on the enclosing scope.
If the check box is clear, and there is no fault handler defined on the enclosing scope, then the activity is put into the stopped state, and a work item for the process administrator(s) is created so that the problem can be repaired. Potentially, this option allows you to simply pause the execution of the process to have the problem fixed. This is especially useful in a process that has been running for a long time.
If the check box is enabled, then the fault is sent to the fault handler of the activity's enclosing scope. If this is insufficient to deal with the fault, then it is re-thrown to the next enclosing scope. If the fault reaches the outermost scope, the process will terminate.
Enable persistence and queries of business-relevant data
When this check box is enabled, the details and history of the execution of this activity are stored in the runtime environment for later reference.
When it is clear, then no data is kept.
Transactional Behavior
This field describes how invoke, visual snippet, or human task activities will execute in a long-running process. There are four choices:
  • Commit Before
  • Use this setting if the transactions that precede it must be fully committed before it can begin. This activity will still tolerate being in a transaction with other activities that follow it.
  • Commit After
  • Use this setting if your activity must be committed immediately after it has completed. This activity will still tolerate being in a transaction with other activities that precede it.
  • Participates
  • Use this setting if this activity does not require a commit to occur either before or after it, and where it can co-exist within a transaction where one or more other activities will be invoked.
  • Requires Own
  • Use this setting when this activity must be isolated within its own transaction.

Feedback
(C) Copyright IBM Corporation 2005, 2006. All Rights Reserved.