Monitoring a Workflow Process

This topic describes how to monitor and troubleshoot a Workflow Process in a production environment.

Note: Workflow Process monitoring is not available when inspecting a Developer Workspace. To debug a Workflow Process in a Developer Workspace, use the Process Simulator. For more information, see Using the Process Simulator.

The following tools and views are available to monitor and troubleshoot a Workflow Process:

• Workflow Monitoring Configuration view, Workflow Instance Monitor view, and Workflow Instance Admin view

  The Workflow Monitoring Configuration view allows you to configure the Monitoring Level (see Setting Monitoring Levels for a Workflow Process), Replication Level (see Deploying a Workflow Process to Siebel Mobile Web Client) and Analytics Level (see Collecting Data About Workflow Process Properties) for a given Workflow Process.

• Event logging

• WF Process Metric object

• SARM (Siebel Application Response Measurement)

• Siebel FDR (Flight Data Recorder)

Use these tools and views to monitor and troubleshoot the following for a Workflow Process:

• Progress and status information. Use the Workflow Instance Monitor view and the Workflow Instance Admin view to monitor the progress and status of each Workflow Process. For more information, see Setting Monitoring Levels for a Workflow Process.

• Operation details. Use event logging to trace operations that each Workflow Process step performs. For more information, see Monitoring Levels for Tracing and the Event Log and Increasing Tracing Levels for Server Components of the Workflow Management Server.

• Workflow Process metric information. Use the WF Process Metrics object to collect data that is associated with the properties of the Workflow Process. For more information, see Collecting Data About Workflow Process Properties.

• Performance measurement data. Use SARM to capture timing data that measures the performance of a Workflow Process. For more information, see Collecting Timing Data.

• Failure analysis records. Use Siebel FDR to capture the events that might cause a system failure. For more information, see Collecting Data About System Behavior and Server Component Behavior.