Siebel Business Process Framework: Workflow Guide > Administering Workflow Processes > Monitoring Workflow Processes in a Production Environment >

Setting Workflow Process Monitoring Levels

The Monitoring Level you set determines the frequency with which log writing occurs and, hence, the data available in the workflow instance views.

There are two views you can use to monitor workflow processes. For more information, see Workflow Instance Admin View and Workflow Instance Monitor View.

Setting Monitoring Level Parameters

When the workflow instance is created, the monitoring level is read from the workflow process definition and remains throughout the lifetime of the instance unless the instance is paused. In the case of an instance being paused, when the instance is resumed, the monitor level is reread from the definition.

Table 63 describes monitoring level parameters and their corresponding log writing frequencies you can set for a workflow process.

To set the monitoring level parameter

1. In the Siebel client, navigate to Administration-Business Process > Workflow Deployment.
2. In the Active Workflow Processes applet, set the Monitoring Level field.

Considering the Impact of Monitoring Levels on Performance

The monitoring level determines the frequency at which data is written to the disk. The frequency is optimized internally by the Workflow run-time environment, based on the workflow type and the monitoring level you choose.

Configuring monitoring at any level incurs performance overhead to your workflow processes. It is best to set the monitoring level to 0 (None) or 1 (Status) on workflow processes running in production.

NOTE:  It is recommended that monitoring levels of 2 (Progress) and higher only be used for debugging workflow processes.

At the Debug monitoring level, the log is written to the disk after every step.

Monitoring Levels and Version 7.0 Compatibility

Version 7.0 workflows with persistence frequency and persistence level set are mapped to a monitoring level based on the following logic:

• If the persistence frequency is set to NONE, then the monitoring level is set to NONE.
• If the persistence frequency is ON_PAUSE or EVERY_STEP, persistence is explicitly turned on and the monitoring level is set:
  • If the persistence level is ALL_STEPS, then the monitoring level is set to PROGRESS.
  • If the persistence level is CURRENT_STATE, then the monitoring level is set to STATUS.

In this release, persistence and monitoring are separate features that serve different purposes. Persistence is a quality of service and is controlled at definition time. Monitoring is an administrative tool and is controlled at deployment time. Monitoring typically does not impact workflow process functionality.