If you want to separate the workflow isolated region data for any reason, you can specify a custom tablespace to contain the data for that region. In addition, you can enable a region for recovery independent of other regions. See Isolated region recovery overview for more information.
Set the custom tablespace properties for the selected region. From the Region node, select a region, then click the General tab.
General fields | Description |
---|---|
Tablespace Filegroup
|
Default tablespace - Select this option for Process Engine to use the tablespace defined in the Database tab for Process Engine properties. The data for all regions is in these database tablespaces. |
Custom - Select this option and enter the name of a tablespace you defined in the database. This specifies a separate tablespace for the data of the selected isolated region. CAUTION The tablespace name is case sensitive; it must match the tablespace name you defined in the database. (Check the name in the database to confirm the exact name.) You can also create multiple tablespaces for specific workflow data, such as queues, rosters, indexes, event logs, region object table, or identity tables. Click the ... button to specify multiple tablespace. See Advanced Tablespace Settings. NOTE If you want to back up the data of one isolated region separately from other regions, you must specify one or more custom tablespaces for that region data that are not shared with other regions. See the next entry, Enable region for recovery. |
|
Enable region for recovery | Select this option to enable backup and recovery of the isolated region independent of other regions. (This option is available for selection only when the custom tablespaces for the selected region are not shared with other regions.) NOTE Once you select Enable region for recovery, the setting is permanent and cannot be undone. If you do not select this option before you initialize the region, some of the shared workflow data will remain in the default tablespace and you will not be able to select this option until you convert the region data.) For an isolated region that has not been initialized: Specify one or more separate tablespaces in the database for the region (as described above). The tablespace must not be shared with other isolated regions. When you initialize this region, all of the data for this region will be saved in the specified tablespaces. See Enable recovery for a new region, not initialized. For an existing (initialized) region: Specify one or more separate tablespaces, as above, use database tools to move the region data to the separate tables, and then use vwtool - rdbConvertReg to move the shared workflow data for the region into the separate tables. See Convert existing region to recovery enabled. In the illustration below, Region 1 is recovery-enabled—the system data and region data for Region 1 are all moved to tablespace TS1. The data for other regions are still in the default tablespaces. |
Tablespaces in Use (Oracle, DB2) Filegroups in Use (Microsoft SQL Server) |
This field displays a list of all the tablespaces that are currently being used by the region. This property is useful to a database administrator to identify shared tablespaces, since you cannot enable region recovery if tablespaces are shared. |
Right-click the region name to access the following options.
Action | Description |
---|---|
Lock/Unlock | Before backing up or recovering the data, lock the region. Right-click the region name, and select Lock from the context menu, or from the Action menu. After the region backup is complete, unlock the region. |
Delete | Before you choose this option, use the Process Configuration Console Remove Region command to delete the region from the PE database. Once the region is removed, use Delete to remove the region from the list of regions displayed. NOTE If you use Delete in Process Task Manager without first removing the region from Process Configuration Console, Delete detects that the region tables still exist, and displays an error message. |