Configuring the Oracle Schema

Status

If you are...	This task is...
Installing a new iProcess Engine Version 11.9.0	Optional
Upgrading from an iProcess Engine Version 11.0 or later	N/A

Database

Oracle

Description

When you run the installer, it creates a small database by default (approximately 50Mb) that is suitable for benchmarking or development purposes.

You can modify this default database configuration if you want to optimize it for your Oracle environment, taking into account factors specific to your installation, such as the number of cases, the amount of case data, the life of cases, and so on.

The Default iProcess Engine Schema Configuration

By default, the installer performs the following operations when it creates the iProcess Engine schema:

• It creates the following tablespaces for the Oracle instance. In the non- RAC environment, the default tablespaces location is ORACLE_HOME\database. In a RAC environment, the installer does not specify the datefile value, and RAC determines the tablespaces location automatically.

— a data tablespace (with the default name staffwar). By default, all iProcess Engine tables, indexes, and Oracle AQ queues are stored in this tablespace.

— a temporary tablespace (with the default name temp), which is used for sorting.

•

It creates the following Oracle users:

— iProcess Engine DB Schema Owner User (with the default name swpro).

— iProcess Engine DB User (with the default name swuser).

The staffwar and temp tablespaces are allocated to these users as their default tablespaces.

• It creates the iProcess Engine schema tables, indexes, and Oracle AQ queues in the default staffwar tablespace.

Note	The use of the `staffwar` tablespace is defined in the `tablesizes` file. See How the Installer Sets Up the Default Configuration for details.

How the Installer Sets Up the Default Configuration

The installer uses the init2Kora_tok.sql file and the tablesizes file as the template files to create the iProcess Engine schema:

• the init2Kora_tok.sql file

The init2Kora_tok.sql file defines the following configuration macros for each iProcess Engine table and index that is to be created:

— SIZETABLESIZE—the initial size (in extents) of a table.

— SIZETABLEPCTINCREASE—the percentage increase to be applied when growing a table.

— SIZETABLESPACE—the tablespace to be used by a table.

— SIZEINDEXSPACE—the tablespace to be used by an index.

where SIZE is one of seven different categories, as shown in SIZE Categories .

SIZE Categories
Category	Used For	Example
TINY	Small tables that do not grow.	`flag_table procedure_lock`
SMALL	Generally static tables that contain small amounts of data.	`list_names dbs_names`
MEDIUM	Generally static tables that contain more data.	`user_names user_values`
BIG	Slightly larger tables that typically hold values for references held in SMALL and MEDIUM tables.	`user_values db_str_values`
LARGE	Most of the tables that contain case-related information, typically ones that only have one or two rows per case.	`case_information outstanding_addr staffo`
HUGE	Tables that hold multiple rows per case, but not for all cases.	`pack_data pack_memo`
MASSIVE	Tables that hold multiple rows per case for all cases.	`audit_trail case_data`

Note	See TIBCO iProcess Engine (Oracle) Administrator’s Guide to see which macros are defined for each table and index in the iProcess Engine database.

• the tablesizes file

The tablesizes file defines a real value for each configuration macro in the init2Kora_tok.sql file. The default values for the different TABLESIZE macros are shown :

# # Initial size (in extents) for each # category of table. # TINYTABLESIZE=1K SMALLTABLESIZE=2K MEDIUMTABLESIZE=40K BIGTABLESIZE=200K LARGETABLESIZE=500K HUGETABLESIZE=500K MASSIVETABLESIZE=1M

When running the installer, it:

1. copies the following files to the installing user’s temporary folder (as defined by the %TEMP% user environment variable):

— init2Kora_tok.sql

— the tablesizes file specified in the Select Tablesizes Profile dialog box.

updates the init2Kora_tok.sql script to:

replace the configuration macros with the actual values from the tablesizes file.
replace occurrences of the default data tablespace name (staffwar) with the name specified in the Confirm Tablespace dialog.

3. runs the init2Kora_tok.sql script to create the iProcess database schema.

How to Change the Default Configuration

You can change the default configuration of the iProcess Engine schema to match your particular requirements. Depending on the level of configuration control you need, you can use any combination of the following methods:

•

Change the Default Data Tablespace

There are two ways in which you can change the default data tablespace to be used:

—

The installer can automatically create the default data tablespace for you, using the name you specify in the Database Details dialog. See Database Details for details.

—

Alternatively, you can create the default data tablespaces manually before running the installer. You may want to do this if, for example, you want to spread the larger iProcess tables across multiple tablespaces.

Note

If you are using Oracle Real Application Clusters (RAC) you must create all required tablespaces on the RAC shared storage device or devices before running the installer. If you do not do this, the installer creates the data file or files for the tablespace in the ORACLE_HOME\database directory.

To do this:

— Manually create a tablespace you want to use as the default data tablespace. If you have created multiple tablespaces, simply specify the name of one of these tablespaces.

— When running the installer, specify that you want to use this tablespace in the Database Details dialog, then specify that all database objects should be created in this tablespace in the Confirm Tablespace dialog. See Database Details for details.

•

Use an Alternative tablesizes File

When you run the installer, you can use the Select Tablesizes Profile dialog to choose one of the following alternative tablesizes file:

— tablesizes.med—Using this file will create a medium-sized database, requiring at least 2.5 GB of disk space.

— tablesizes.large—Using this file will create a large-sized database, requiring at least 65 GB of disk space.

Note	See Usage Profiles for Tablesizes Files for more information about the intended usage profiles of these files.

•

Customize Specific Configuration Macros in the Tablesizes File

If you require more specific configuration control, you can edit the tablesizes file to change the values assigned to specific configuration macros. For example, you may want to:

— increase the initial size of tables that use the LARGETABLESIZE macro.

— spread the larger iProcess tables across multiple tablespaces or file systems (to aid I/O performance and reduce contention) by modifying individual SIZETABLESPACE or SIZEINDEXSPACE entries.

Note	Remember to create any additional tablespaces before you run the installer.

You can edit the tablesizes file when you run the installer.

•

Customize the init2Kora_tok.sql File to Assign Different Configuration Macros or Values to Specific Tables or Indexes

Finally, you can edit the init2Kora_tok.sql file to assign different configuration macros (or hard code specific values) to specific tables and indexes. You can do this when you run the installer.