Monitoring and Managing Engine Sessions

Process Instance Termination

Process termination occurs when the engine places a process instance in either a COMPLETED state or an ABORTED state.

Completed Process Instances

An engine completes a process instance when the Last activity reaches a

COMPLETED state.

Aborted Process Instances

An engine aborts a process instance in the following situations:

the process instance is stalled—no activities are in an ACTIVE or READY state (that is, all are either COMPLETED or PENDING) and no timers are active.

an ACTIVE activity (including a Subprocess activity) is placed in an ABORTED state and has no OnAbort router method specified.

a system manager requests that a process be aborted.

an exception is thrown on an activity method.

When a process instance is aborted, any uncompleted activities in the process are aborted, all process timers are stopped, and all process attribute updates are discarded.

Monitoring and Managing Engine Sessions

Since the engine is coordinating work being performed by client applications that have sessions with the engine, one dimension of system management concerns the number and state of such sessions.

This section describes how to perform the following tasks:

Monitor the state of a session

Manage one or more sessions

NOTE This section uses mouse popup menu commands to describe how to perform various operations. You can also use other methods of accessing commands, as described in Chapter 3, “The iIS Console.”

Chapter 6 Managing Process Execution 173

Page 173
Image 173
Sun Microsystems 3 Monitoring and Managing Engine Sessions, Process Instance Termination, Completed Process Instances