An isolated region is a logical subdivision of the workflow database that contains the queues for the work items, event logs, rosters, and other configuration information. It also contains all transferred workflows and running work items.
In a FileNet P8 system, all Workplace applications that use workflow functionality (Process Designer, Process Administrator, active workflows) use a single isolated region. A system administrator uses Enterprise Manager to define the isolated region (a Process Engine host, the communication point, a password, and isolated region number), and to assign a connection point name to that configuration. See Concepts: isolated regions for additional information.
To specify the Process system and isolated region that will be used by the Workplace applications, an administrator specifies a connection point in Workplace Site Preferences. See Process Engine Connection Point for more information.
In Process Configuration Console, you connect to the isolated region and initialize it with default structures, such as Inbox, default roster, and event log, to make it ready to process workflows. See Connect to isolated region and Initialize isolated region for more information. To accommodate your applications, you can customize the isolated region by creating work queues to hold work items awaiting processing, defining exposed fields, configuring custom step processors, and other configuration tasks for the isolated region.
A workflow database can contain up to 1000 isolated regions, although a FileNet P8 system can access only one at a time. Within a workflow database, each isolated region is identified by a unique number ranging from 0 to 999. Isolated region 0 contains system data and is reserved for system software use. Users can define regions 1 - 999. See Multiple Process Engines and isolated regions for additional information.