Monitoring and Managing Process Execution
Checking for Bottlenecks in Process Execution
Instances of a given process sometimes stall at a particular activity, causing a bottleneck in execution of that activity. This could happen, for example, if a particular activity were backlogged, or a trigger condition could not be fulfilled.
➤To find a process bottleneck
1.Select the engine executing the process in the iIS Console main window. The engine must be running.
2.Choose Monitor > Activities Resident. This opens the Activity Resident window, displaying the list of activity instances being executed by the engine.
For each activity instance, the list shows the activity name, activity ID, activity state, process name, and process ID.
3.Filter the activity list by the process name (registered process definition) of the process you are checking (see “Filtering iIS Console Lists” on page 73).
This filter should list activities for all active process instances corresponding to the registered process.
4.Look for an activity name with more than an average number of instances.
You can also filter the activity list by activity name and check the number of items in the list, which is displayed in the status bar.
5.Filter the activity list by the name of the suspected bottleneck activity.
6.Check the state of activities in the listing.
Depending on the situation, you might need to do further analysis. For example, if most instances of the activity are in READY state, there might currently be too few sessions to do the work or the sessions to which the activity is assigned are doing other work. If most of the activities are in PENDING state, then probably a trigger condition is not being met.
