Analyzing Process Execution

To analyze the situation further you might have to open particular activity instances, check sessions, or possibly check attributes of the corresponding process instances.

Analyzing Process Execution

The iIS product does not provide tools for analyzing information in the engine database’s history log tables that could be useful in managing and reporting on process execution. The history log provides information that can be used to answer the following types of questions:

How long does it take for processes to complete?

You can determine how long it took for a particular process instance (identified by primary attribute) to go from start to finish, or how long it takes, on average, for process instances to complete. You can analyze this question as a function of some particular process attribute (creator, creation date, invoice value, and so forth).

Where are the bottlenecks in process execution?

There are several approaches to finding bottlenecks. One is to determine how many process instances are currently in a given stage of completion. For example, you could create a graph of how many process instances have reached each activity, and then look at how this graph changes over time to see if a pattern emerges that indicates a bottleneck. You could also look at how this graph changes as a function of some particular process attribute.

Another approach to finding bottlenecks is to determine how long it takes, on the average, for a process instance to complete each activity. Some might take substantially longer than others. You might also look at how long the activity is in each state (PENDING, READY, ACTIVE) to determine a strategy for resolving the bottleneck.

How well are activity queues functioning?

For a queued activity, you can see how long the queue currently is or how long it is on the average. You can determine the average length of time that activities remain in the queue, or if the prioritizing of activities in the queue leaves some activities at the bottom of the queue for an unacceptable length of time.

Chapter 6 Managing Process Execution 197

Page 197
Image 197
Sun Microsystems 3 manual Analyzing Process Execution