Introduction
The information displayed in these iIS tools falls into the following categories:
Alarms A number of error conditions in the functioning of an iIS process engine that might require your intervention are reported as alarms. These conditions range from a communication problem between engine components to exceptions generated in the primary engine unit in the course of process execution. Alarms are displayed in the Process Engine Alarm window (see “Process Engine Alarms Window” on page 205) and written to an alarms table in the engine’s history log database (see “WFHAlarmLog” on page 349).
Exceptions All error conditions detected by an engine (including alarms) cause an exception to be raised. When the task that encounters the condition originates in the client, the error is reported directly to the client (for example, attempting to start an activity that has already been started). When an error is detected by an internal engine task (for example, attempting to start an unregistered subprocess), the engine records a process exception, activity exception, session exception, or timer exception in the primary engine unit’s log file (see “Engine Log Files” on page 210). The exception can also be written to the iIS Console trace window (see “Using the iIS Console Trace Window” on page 215).
Messages Each engine
Performance Indicators You can monitor various aspects of process execution using the iIS Console. For example, you can monitor sessions and executing processes as described in Chapter 6, “Managing Process Execution.” You can also monitor a number of specific performance indicators using the charting capabilities described in “Performance Charts” on page 221.
This chapter describes how to use the iIS alarms window, log files, tracing window, and performance window to display the above categories of troubleshooting information.
