Overview: Siebel eBusiness Application Integration Volume I > Scalability and Performance >

Workflow Process Manager

Workflow Process Manager is a task-based server component. A new thread is created for each request. However, Object Manager sessions are cached and reused for subsequent requests. When sizing a system, you need to look at the maximum number of workflow tasks you expect to have active at a given time. This determines the maximum number of Object Manager sessions Siebel applications create.

NOTE:  Starting with Siebel 7.0, Business Integration Manager and Business Integration Batch Manager have been deprecated, so if you were using either one in your business processes you need to replace them with Workflow Process Manager or Workflow Process Batch Manger respectively. For details on Workflow Process Manager and Workflow Process Batch Manager, see Siebel Business Process Designer Administration Guide.

The exact CPU and memory consumption of each task depends on the actions performed in your workflow processes. To estimate CPU and memory consumption in your production environment, run a single task, measure its resource consumption, and make an estimation based on your maximum concurrent sessions. (Be sure to take into account session caching when making these measurements.)

If you need a large number of sessions, you may want to run Workflow Process Manager on multiple Siebel Server machines. You can then use Resonate to load-balance requests across the Siebel Servers. If you plan to run a significant number of tasks per server (such as 100 or more), you may also want to run multiple MT (multithreaded) server processes.

If you are going to run several different types of workflows, you should run each type in a separate process. This makes it easier to monitor the overall CPU and memory usage of each process type.

The number of MT server processes and the number of tasks per process are controlled through these parameters:

NOTE:  These parameters are per Siebel Server. For example, Max MT Servers refers to how many server processes to run on each Siebel Server machine. For details, see Siebel Server Administration Guide.

Performance Events

You can get performance tracing of workflows by setting the event WfPerf for the component in which your workflow is running. Setting the event to level 4 gives timing for the execution of the overall process. Setting the event to level 5 provides timing for each step as well. These events can be useful not just for measuring workflow performance but also for measuring the performance of business services executed within these workflows.


 Overview: Siebel eBusiness Application Integration Volume I 
 Published: 18 April 2003