Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Configuration Console
  Search  |  Index
Process Reference  
Process Configuration Console
Getting started
Isolated regions
  Initialize an isolated region
  Connect to an isolated region
  Disconnect from an isolated region
  Export to
IBM CrossWorlds®
  Copy an isolated region
  Remove an isolated region
  Modify isolated region properties
     Configure event logging options
     Enable or disable statistics collection
     Set performance parameters
     Set web application properties
     Configure step processors
     Specify step processor locations
Queues
Rosters
VWServices
Process Engines
Workflow database
Events and statistics
   

Set performance parameters

The performance parameters maximize performance by controlling workstation access to the server and balancing the optimization of workstation and server performance.

For most systems, the default settings are sufficient. You should adjust the settings only if directed by your FileNet support representative.

See Adjusting performance parameters for an isolated region for more detailed information.

To set performance parameters

  1. Select the icon of the isolated region you wish to modify and click Properties on the toolbar.
  2. Select the Region Configuration tab.
  3. In the Maximum operations per transaction box, indicate the maximum number of database operations per transaction. You can enter a number manually or choose from the drop-down list. The default setting is 100.
  4. In the Maximum instructions per transaction box, indicate the maximum number of instructions per transaction. You can enter a number manually or choose from the drop-down list. The default setting is 200.
  5. Click OK.
  6. Click Commit Changes on the toolbar to apply this change to your isolated region. You can commit the changes immediately, or you can wait until you have finished all your changes.

    NOTE The commit process suspends all other database transactions within the isolated region until it finishes. We strongly recommend that you accumulate all changes and commit them once when you're done, or that you commit changes when the isolated region is relatively inactive. Avoid committing changes after every modification whenever possible.