 |
The illustration at left shows a system with three Process Routers
running on the Application Engine or web server,
and thus accessible to Process Configuration Console.
- vwrouter -
specifying isolated region 1 on Process Engine
rosa (vwrouter is the default
Process Router
name)
- vwrouter262
- specifying isolated region 262 on Process Engine rosa
- HumanResources
- specifying isolated region 1 on Process Engine
hq_hr
There are two VWServices shown, whose primary Process Engines
are:
- rosa, with
two isolated regions: region 1 and region 262
- hq_hr, with
one isolated region: region 1
Work items and processing in one isolated region are entirely independent
from work items and processing in another isolated region. For example,
while isolated regions 1 and 262 share the same Process Engine
(rosa), each isolated region has
separate user queues, work queues, component queues, rosters, and
event logs.
In the illustration at left, the two isolated regions in the rosa
VWService have three Process EnginesServer
0 (the primary Process Engine),
Server 1, and Server
2to distribute the processing load. You can assign
separate component queues, work queues, and workflow rosters to
particular servers. During processing, the Process Router
routes work items based on the assignments you have made.
While the HumanResources Process Router
is running on the same Application Engine or web server
as vwrouter and vwrouter262,
it points to a different Process Engine
(hq_hr) and thus represents a different
VWService. Isolated region 1 on Process Engine
hq_hr is completely separate from
isolated region 1 on Process Router
rosa.
TIP
To configure a VWService/isolated region combination that is not
listed in your Process Configuration Console,
you must first start a Process Router
on the Application Engine or web server
and specify the VWService's primary Process Engine
and isolated region. See
in Help for Task Manager.
|