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
   

Manage isolated regions

An isolated region is a logical subdivision of the workflow database. Isolated regions are useful for subdividing the work area within a VWService. For example, in a VWService used by workflow developers, each developer might have a separate isolated region. Or, in a VWService where claim processing occurs, users who handle medical claims might work in one isolated region while those who process dental claims work in another. Since each isolated region has its own user queues, work queues, and event logs, multiple isolated regions allow separate monitoring of each work area. See Multiple isolated regions and multiple VWServices for additional information.

Each VWService can contain up to 1000 isolated regions. Within a VWService, each isolated region is identified by a unique number ranging from 0 - 999. Isolated region 0 exists in every VWService; it contains system data and is reserved for system software use. Users can define regions 1 - 999.

You must connect to an isolated region in order to view or modify its configuration. Once connected, you can modify the isolated region's properties, initialize an isolated region to make it ready to process workflows, copy an isolated region's configuration to another isolated region, or remove the isolated region.