Advanced table space settings

In addition to creating a custom table space for the region data, you can also create separate table spaces for specific workflow data, such as queues, rosters, event logs, indexes, region object table, or identity tables.

To access the Advanced Tablespace Settings window from the Region General tab, select the Custom radio button and click the ... button.

Field Description
Name

Enter the RDB Object name. See below for details on RDB Object name basic syntax.

NOTE   If the region is initialized, some default names are already specified.

Value

Enter the name of the table space in the database.

CAUTION   It is most efficient to create the table space in the database before you specify it in Process Task Manager. The table space name is case sensitive; it must match the table space name you defined in the database. (Check the name in the database to confirm the exact name.)

RDB Object Name Basic Syntax

An RDB object can be a table, or a whole group of objects created in Process Engine, such as queues, rosters or logs.

The object name is a multi-part string, separated by underscores and periods. Each node can have 128 characters.

Base Region Type Logical table name Logical index name
pe_data
pe_index
pe_blob
<region#> queue
roster
log
table
<logical_table_name> <logical_index_name>

NOTE   When you are using region recovery, you can specify only to the Type level. For example, you can specify a table for all queues in a region; you cannot recover to the level of separate tables for individual queues, rosters, and so on.

Example

<tablename> - the actual table name.
<indexname> - the actual index name.

For region:
pe_data.<region#> - Defines the location of all tables in a region.
pe_index.<region#> -
Specifies the location of all table indexes in a region.
pe_blob.<region#> - Defines the location of all BLOBs in a region.

For queue:
pe_data.<region#>.queue - Location of all queue tables in a region.
pe_data.<region#>.queue.<logicalqueuetablename>
- Location of a selected queue.
pe_data.<region#>.queue.<logicalqueuetablename>.<logicalindexname>
- Location of a queue index.

For roster:
pe_data.<region#>.roster -
Location of all roster tables in a region.
pe_data.<region#>.roster.<logicalrostertablename> -
Location of a selected roster.
pe_data.<region#>.roster. <logicalrostertablename>.<logicalindexname>
- Location of a roster index.

For log:
pe_data.<region#>.log
- Location of all log tables in a region.
pe_data.<region#>.log. <logicallogtablename> -
Location of a selected log table.
pe_data.<region#>.log. <logicallogtablename>.<logicalindexname>
-Location of a log index.

For specific table:
pe_data.<region#>.table.<tablename> - Location of a particular table in a region.
pe_data.<region#>.table.<tablename>.<indexname>
- Location of a table index.

For example, to specify a separate table space, Reg9Logs, for the log files for isolated region 9, you specify RDBObject pe_data.9.log, and the value Reg9Logs (the name of the custom table.

When Process Engine creates a table, it first checks for configured RDBObjects. If the appropriate object is not found, it uses the location of the parent object. In this example, if the location of pe_data.9 is not specified, the table will be created at the location of the parent, pe_data, located in VWDATA_TS.

The following table is the configuration corresponding to the figure below.

Object Name Location Description

Object Name Location Description

pe_data

VWDATA_TS

Default data table space.

pe_index VWINDEX_TS Default index table space.
pe_data.1 TS1 Region 1 default table space.
pe_index.1 TS1 Region 1 default index table space.
pe_data.100 TS100Data Region 100 default table space.
pe_index.100 TS100Index Region 100 default index table space.
pe_data.100.log TS100Log Table space for Region 100 event logs.

In the figure below, Region 1 takes table space TS1 and Region 100 spans across table spaces TS100Data, TS100Index, TS100Blob, and TS100Log. Region 1 and Region 100 can be backed up or recovered separately from the other regions. Region 2 is not specified in the table. This region is in the Process Engine default table space and blends with Process Engine system tables; this region cannot be backed up alone, it can only be backed up in a complete Process Engine backup.

Region 100 extends across four table spaces, TS100Data, TS100Index, TS100Blob, and TS100Log. In the table, the Region 100 index is in TS100Index. All BLOBs are in TS100Blob. All event logs are created in TS100Log. All other components are in the default table space TS100Data.

In the following example,

Custom table spaces