Tuning Workflow Process Manager for Performance

This topic provides general approaches to tune and optimize performance of Workflow Process Manager.

Note: Every implementation of Siebel applications is unique, and so every use of workflow processes is also unique. It is in your best interest to test, continually monitor, and tune your workflow processes to achieve optimal throughput.

You can follow the guidelines explained in the following information:

• "Caching Business Services"

• "Caching Sessions"

• 
  

  Note: Consider the information provided in this topic as general background information. No attempt is made to detail the many variables that affect tuning at specific sites. This content is not a substitute for specific tuning recommendations made by Global Customer Support or other Oracle service organizations.

  
  

Caching Business Services

This topic is part of "Tuning Workflow Process Manager for Performance".

Business services invoked through Workflow Process Manager must have the Cache property set to TRUE. This feature makes it possible for the Workflow engine to not reload and reparse the business service, and therefore enhances the performance of workflows that invoke business services.

Note: Predefined Siebel business services that have the Cache property set to FALSE must not be reset to TRUE.

Caching Sessions

This topic is part of "Tuning Workflow Process Manager for Performance".

The parameter OM - Model Cache Maximum (alias ModelCacheMax) for Workflow Process Manager determines the size of the cache for model objects (also known as cached sessions). Cached sessions maintain database connections and session data for locale, user preferences, and access control.

Note: Session caching applies only to noninteractive Object Manager-based server components like Workflow Process Manager. It does not apply to Siebel Application Object Manager or EAI Object Manager components.

This feature maintains and reuses existing sessions rather than creating a new session each time one is requested. Using this feature can improve login performance for Workflow Process Manager.

Each model in the cache creates two database connections for the life of the model: one connection for insert, update, and delete operations; another connection for read-only operations.

The default value of ModelCacheMax is 10. A value of 0 disables this parameter. The maximum value is 100. In general, you set ModelCacheMax to a value approximately equal to the number of concurrent sessions the Workflow Process Manager component is expected to support.

Note: When component sessions use multiple user IDs, session caching provides less benefit relative to its cost. The benefit is greatest for component sessions using the same user ID.

See also Siebel System Administration Guide.