Connection Points and Isolated Regions

//Connection Points and Isolated regions


Connection Points: Connection points replace the router process used in previous Process Engine releases, connecting the Process Engine API to an associated isolated region. Connection points are defined in the Content Engine API (the PEConnectionPoint and IsolatedRegion classes) and persisted in the Global Configuration Data (GCD) on the Content Engine. Multiple connection points can reference the same isolated region. The set of connection points defined is reflected in the Content Engine's Domain.PEConnectionPoints property. To create and manage connection points, use the IBM Administration Console for Content Platform Engine.

To establish or log on to a Process Engine session a connection point must be specified and the Content Engine host must be accessible.

Isolated regions: An isolated region is a logical subdivision of the workflow system. Isolated regions are often used to separate development, testing, and production environments such that developers and testers can share computing resources while still keeping their disparate activities isolated. An isolated region consists of queues, rosters, and event logs.

An isolated region is identified by one or more connection points. Information that is common to all regions in the workflow system is contained in the workflow system properties.

You can initialize or delete an isolated region. In addition, you can delete the workflow system. Typically, these activities are performed only in a development environment.