Optimizing Process API Usage

This topic provides guidelines on optimizing your use of Process API classes in order to improve your Process application's performance. Improving application performance provides improved efficiency for users, improved efficiency of computing resources, reduces downtime, and improves the overall ability to manage the Process Engine.

Subtopics include:

General Guidelines on Optimizing a Process Application

Designing a Process application for high performance can significantly improve application efficiency while enhancing the user experience. The following guidelines provide general guidance on optimizing Process application performance:

The following subsections provide details on these and additional guidelines to improve application efficiency.

Optimizing Roster Usage

All work items are tracked through the roster and multiple workflow definitions are contained in a roster. Note that only VWRosterElements and VWWorkObjects are retrieved from a Roster query.

To optimize roster usage:

Optimizing Queue Usage

All work for a particular step resides in a queue (the queue contains the actual work object BLOB). A queue can potentially contain different types of work objects. When a queue is queried, VWWorkObjects, VWStepElements, and VWQueueElements are retrieved.

To optimize queue usage:

Optimizing Log Usage

To optimize log usage:

Optimizing Queries

To optimize query usage:

vwQueue.setBufferSize(25)

Guidelines for Generating Pattern-Matched Lists of User and Group Names with LDAP Data Security

To optimize lists of user and group names in systems with LDAP Data Security for completeness, the following guidelines should be observed:

The result list from either of the Java API VWSession methods findGroups(...) and findUsers(...) is determined by four input arguments: search pattern, search type, sort type, and buffer size. Whether one of these methods is invoked directly through a custom application or indirectly through a FileNet Participant Selection Dialog (accessed through the Config Console, Tracker, Administrator, Designer, and the Sample Java Step Processor client utilities), the output list normally has the following characteristics:

The name lists produced by these methods have limitations for particular combinations of input arguments, as follows: