Thursday, August 20, 2015

Description of the STATE Values for Tables in the BPEL



     The values of the STATE column in some of the BPEL dehydration store tables. These values are taken from the BPEL 2.1 dehydration store tables, but are included here for reference.

Table :  CUBE_INSTANCE

Value
Constant Name
Description
0
STATE_INITIATED
State value for an instance that has just been created. The instance will only have this value as its state after it has been created by the process domain.
1
STATE_OPEN_RUNNING
State value for an instance that has been created and has active activities executing. The instance is not in an exception or error condition.
2
STATE_OPEN_SUSPENDED
State value for an instance that is unavailable. Performers of any of the activities that belong to this instance cannot take any action until the instance has returned to the running state.
3
STATE_OPEN_FAULTED
State value for an instance that has an activity that has thrown an exception. When an activity throws an exception, the instance is flagged as being in an exception state until the exception is bubbled up, caught and handled.
4
STATE_CLOSED_PENDING_CANCEL
State value for an instance that has started its cancellation procedure. Since cancelling an instance may involve a great deal of business logic, the amount of time the entire cancellation process may take may be anywhere from seconds to days. During this time, the instance is said to be pending cancellation; an instance may not be acted upon during this time.
5
STATE_CLOSED_COMPLETED
State value for an instance that has been completed. All activities belonging to this instance have also been completed.
6
STATE_CLOSED_FAULTED
State value for an instance that has an activity that has thrown an exception while the instance is being cancelled. This state is equivalent to STATE_OPEN_FAULTED except that when the exception is resolved, the state transitions back to CLOSED_PENDING_CANCEL rather than STATE_OPEN_RUNNING.
7
STATE_CLOSED_CANCELLED
State value for an instance that has been cancelled. All activities belonging to this instance have also been cancelled.
8
STATE_CLOSED_ABORTED
State value for an instance that has been aborted due to administrative control. All activities belonging to this instance are also moved to the aborted state.
9
STATE_CLOSED_STALE
State value for an instance who's process has been changed since the process was last accessed. No actions may be performed on the instance. All activities that belong to this instance are also moved to the stale state.

 
Table :  WORK_ITEM

Value
Constant Name
Description
0
STATE_INACTIVE
State value for an activity that has just been created. This state is transient and is not persisted in the database.
1
STATE_OPEN_ACTIVE
State value for an activity that has been persisted in the database (activated) and may be acted upon by a performer.
2
STATE_OPEN_SUSPENDED
State value for an activity that has been suspended. Performers assigned to this activity will not be able to modify this activity until it has been resumed.
3
STATE_OPEN_PENDING_COMPLETE
State value for an activity that has started to be performed (by a remote asynchronous performer) and is waiting for a callback from the performer to signal that it is complete.
4
STATE_OPEN_FAULTED
State value for an activity that has thrown an exception but has not yet been closed. An activity that has thrown an exception cannot be closed until an enclosing block that can handle the exception has been found.
5
STATE_CLOSED_COMPLETED
State value for an activity that has been successfully completed without
error by a performer. Activitiess that are completed may be compensated if an exception in a block causes all activities to be rolled back.
6
STATE_CLOSED_FINALIZED
State value for an activity that has been successfully finalized. Once an activity has been completed, all dependencies to the performer are removed; the finalized state is available for the system to perform any last-minute actions on the activity.
7
STATE_CLOSED_PENDING_CANCEL
State value for an activity that has started its cancellation procedure. Since cancelling an activity may involve a great deal of business logic, the amount of time the entire cancellation process may take may be anywhere from seconds to days. During this time, the activity is said to be pending cancellation; an activity may not be acted upon during this time.
8
STATE_CLOSED_CANCELLED
State value for an activity that has been cancelled due to scope
* closure. If a scope is closed due to either a successful
* <code>until</code> or <code>handleException</code> call on the
* parent block, all activities created within the enclosed blocks
* must be cancelled. Cancelled activities cannot be compensated like
* completed activities.
9
STATE_CLOSED_FAULTED
State value for an activity that has thrown an exception and has been closed as a result. Once the thrown exception has been handled by an enclosing block the activity that threw the exception is marked as STATE_CLOSED_FAULTED while those activities that were closed as a result of an enclosing block closure are transitioned to STATE_CLOSED_CANCELLED.
10
STATE_CLOSED_ABORTED
State value for an activity that has been aborted due to administrative control. The performer of the activity will not be contacted in this case; abort is available only as an administrative function.
11
STATE_CLOSED_COMPENSATED
State value for an activity that has been successfully completed but must be compensated due to an exception in a parent block. Once an activity has been compensated, it cannot be moved to another state; activities cannot be undone/redone.
12
STATE_CLOSED_STALE
State value for an activity who's process has been changed since the activity's instance was last accessed. No actions may be performed on the activity or the instance.


Table :  DLV_MESSAGE

Value
Constant Name
Description
0
STATE_UNRESOLVED
State value for a message/subscriber inserted into system but has not been correlated with its corresponding subscriber/message. 
1
STATE_RESOLVED
State value for a message/subscriber has been correlated with its corresponding subscriber/message but has not been processed by the BPEL domain (ie callback). 
2
STATE_HANDLED
State value for a message/subscriber has been processed by the BPEL domain (ie callback)
3
STATE_CANCELLED
State value for a message/subscriber has been cancelled ... will not be processed by the BPEL domain.


Table :  MEDIATOR_GROUP_STATUS

STATE  Value
Description
 0
READY
 1
LOCKED
 3
ERRORED
 4
TIMED OUT
 6
GROUP ERROR


Table :  MEDIATOR_RESEQUENCER_MESSAGE

STATE  Value
Description
 0
READY
 2
PROCESSED
 3
ERRORED
 4
TIMED OUT
 5
ABORTED


Table :  MEDIATOR_INSTANCE

STATE  Value
Description
 0
 No faults but there still might be running instances
 1
 At least one case is aborted by user
 2
 At least one case is faulted (non-recoverable)
 3
 At least one case is faulted and one case is aborted
 4
 At least one case is in recovery required state
 5
At least one case is in recovery required state and at least one is aborted
 6
At least one case is in recovery required state and at least one is faulted
 7
At least one case is in recovery required state, one faulted and one aborted
 8 to 16
 Running
 16  
 Stale


Table :  COMPOSITE_INSTANCE

State Value
Description
0
Running
1
Completed
2
Running with faults
3
Completed with faults
4
Running with recovery required
5
Completed with recovery required
6
Running with faults and recovery required
7
Completed with faults and recovery required
8
Running with suspended
9
Completed with suspended
10
Running with faults and suspended
11
Completed with faults and suspended
12
Running with recovery required and suspended
13
Completed with recovery required and suspended
14
Running with faults, recovery required, and suspended
15
Completed with faults, recovery required, and suspended
16
Running with terminated
17
Completed with terminated
18
Running with faults and terminated
19
Completed with faults and terminated
20
Running with recovery required and terminated
21
Completed with recovery required and terminated
22
Running with faults, recovery required, and terminated
23
Completed with faults, recovery required, and terminated
24
Running with suspended and terminated
25
Completed with suspended and terminated
26
Running with faulted, suspended, and terminated
27
Completed with faulted, suspended, and terminated
28
Running with recovery required, suspended, and terminated
29
Completed with recovery required, suspended, and terminated
30
Running with faulted, recovery required, suspended, and terminated
31
Completed with faulted, recovery required, suspended, and terminated
32
Unknown
64
Unknown
65
Unknown
66
Unknown
68
Unknown
80
Unknown

No comments:

Post a Comment