Skip navigation FileNet logo
Glossary  |  Help Directory  
  Help for Process Task Manager
  Search  |  Index
Process Reference  
Process Task Manager
Getting started
Process Service
  Configuring Process Service
  Starting and stopping Process Service
  Configuring the Process Engine
    Datasets
    RDB objects
    Additional Process Engines
PPM (Pooled Process Manager)
Rules Engine
Component Manager
Process Simulator
Routers
Administrative tasks
   

Managing RDB objects

This folder contains the relational database (RDB) objects that are associated with a particular Process Engine. An RDB object can be any FileNET object in a relational database, such as a specific table, index, rollback segment, or workflow queue.

Using RDB objects to designate tablespaces or filegroups

Process Engine uses RDB objects to allow you to decide whether to specify a tablespace or filegroup other than the default for one or more of the Process Engine database tables. A tablespace is a logical construct particular to Oracle databases. It consists of a set of files, partitions, or logical volumes. By assigning database tables to tablespaces, you can designate where the database tables will reside on the server’s storage media. For more information about tablespaces, see your Oracle documentation. A filegroup is a simular concept for SQL Server databases. For further information, see your SQL Server documentation.

By default, the Process Service software places Process Engine database tables in the default tablespace or filegroup specified in the Process Engine database properties. You can specify an alternate tablespace or filegroup by defining RDB objects. The tablespace or filegroup you specify for each Process Engine database table affects the resulting size of each tablespace or filegroup, as well as the performance of database access in your system.

To specify a different tablespace or filegroup for one or more Process Engine database tables, take the following steps on the Process Engine.

To create a new RDB object

  1. Select the RDB object folder, then click New on the Action menu.
  2. Enter the Object Name and Location. See the table below for further details.
  3. Click OK.
  4. Select the Process Service node, then restart Process Service to commit your changes.

To modify an existing RDB object

  1. Select the RDB object you want to modify.
  2. Modify the Object Name and Location as desired. See the table below for further details.
  3. Click Apply.
  4. Select the Process Service node, then restart Process Service to commit your changes.

To delete an existing RDB object

    1. Select the RDB object you want to delete, then click Delete on the toolbar.
    2. Click OK.
    3. Select the Process Service node, then restart Process Service to commit your changes.
Property Description
Object name

The name of the RDB object. The initial system has a basic set of default objects. Defining additional RDB objects allows you to customize the data layout of your relational database. This object name, in conjunction with the location, tells the FileNET software where in the database that object (or group of objects) is to be created. The scope of the RDB object depends on how you format or build the RDB object name.

It is very important to correctly build the object name string. When the Process Engine is directed to create a database object (for example, a workflow roster or queue), it searches the configuration database for a matching RDB_Object to find the location of the object. If not found, the search continues for the location of the parent object.

RDB object name basic syntax

The object name is a multi-part string, separated by periods. The maximum string length is 255 characters. The object name is built in a hierachy, where all names begin with fn_data or fn_indexes.vw. Enter the name of the RDB object, as described in the sections below. Use the following chart to determine the appropriate value to substitute for each variable.

Bracketed text Value
region# The isolated region number
Process Engine# The Process Engine number
tablename The actual table name
indexname The actual index name

For queues:

fn_data.vw.region<region#>.server<Process Engine#>.queue

For rosters:

fn_data.vw.region<region#>.server<Process Engine#>.roster.DefaultWCTable

For all other Process Service tables:

fn_data.vw.region<region#>.server<Process Engine#>.table.<tablename>

For all indexes (Oracle only)

fn_indexes.vw

NOTE  fn_index.vw is an optional RDB object used to specify the location where the software creates all Process Engine indexes. If not specified, the location of fn_index.vw defaults to the fn_data location.

Example

For example, to specify that all queues on server zero in region one go in a tablespace or filegroup other than the default, create an RDB object with a name of “fn_data.vw.region1.server0.queue.”

When a Process Engine database table is created, the software looks up this RDB object to find the corresponding tablespace or filegroup. To do this, the software looks for names which are prefixes of the complete RDB object name if the complete name is not found.

For example, if you create an RDB object with the name:

fn_data.vw.region1.server0.queue

The software looks for the following names in the database until a match is found:

fn_data.vw.region1.server0.queue
fn_data.vw.region1.server0
fn_data.vw.region1
fn_data.vw
fn_data

Note that with the manner in which the prefix search is executed, and the way the RDB object names are chosen, you can control all queue tables on a server, all tables on a server, all tables in a region, or all indexes with a single RDB object.

Location

The name of the tablespace or filegroup to place the RDB object in. The tablespace or filegroup does not have to exist yet; however, you must create it before making configuration changes that use the RDB object.