Siebel Business Process Designer Administration Guide > For Administrators: Administering Workflow Processes > Administering Workflow Processes in the Run-Time Client >

About Process Monitoring Levels

You set deployment parameters to determine the way you monitor your workflow processes. These deployment parameters are Monitoring Level and Log-writing Frequency.

Monitoring Level Parameters

Table 20 shows the monitoring level parameters (and their corresponding log-writing frequencies) that you can set for a workflow process. When the workflow instance is created, the monitoring level is read from the workflow process definition and stays 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.

Log-writing Frequency Parameters

Log-writing frequency determines the frequency at which monitoring 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 select.

You can set the log-writing frequency parameters directly only by using the Debug monitoring level. At the Debug monitoring level, the log is written to the disk after every step.

NOTE:  Enabling 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. Monitoring levels of 2(Progress) and higher should only be used for the debugging of workflow processes.

Monitoring Levels and 7.0 Compatibility

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 as follows:
  • 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.

NOTE:  In this release, persistence and monitoring are separate features that serve different functions. Persistence is a quality of service and is controlled at definition time. Monitoring is an administrative tool and is controlled at deployment time. Monitoring has no impact on the way a workflow process functions.