Consider creating the following indexes to increase the
performance of FileNet® P8 components.
mime_type
Create a single-property index
on the mime_type database column that is in the docversion database
table when the number of records in the docversion table exceeds 1,000,000,
or when both of the following conditions are true:
- The number of items in a folder exceeds 2,000.
- Performance degrades across common functionality such as browsing,
searching, and creating documents.
Restriction:
- If the object store is not case-sensitive, create the index by
using the LOWER function on (mime_type).
- (Workplace XT only) As of the Workplace XT
1.1.5 release, indexing the mime_type column in the docversion table
is no longer necessary for Workplace XT stored search retrievals. The
mime_type search condition is replaced by a search on the SearchType
(integer) property, which can be indexed from the StoredSearch document
subclass in IBM® Administration Console for Content
Platform Engine.
As a result, skew no longer occurs.
Table 1. Single-property index on mime_type that improve
performance of FileNet P8
applicationsDatabase table name |
Class |
Database column name |
FileNet P8
property name |
docversion |
Object Store > Document Class |
mime_type |
MIME Type |
security_policy_id
Create a single-property
index on the security_policy_id database column in one or more of
the following database tables: docversion, container, or generic when
response times degrade or when errors occur when you delete a security
policy from an object store that has more than 1,000,000 documents.
Table 2. Single-property index on security_policy_id that improves performance
of FileNet P8 applicationsDatabase table name |
Class |
Database column name |
FileNet P8
property name |
docversion |
Not applicable |
security_policy_id |
Not applicable |
container |
Not applicable |
security_policy_id |
Not applicable |
generic |
Not applicable |
security_policy_id |
Not applicable |
tail_id and head_id
Create a composite-properties
index on the tail_id and head_id database columns in the relationship
table to improve the performance of insubfolder and infolder searches,
such as when client applications retrieve stored searches or retrieve
properties of stored searches.
Tip: This composite-properties
index is most effective in DB2® databases,
but you can also use it in other supported databases.
Table 3. Composite-properties index on tail_id and head_id that improve
performance of FileNet P8 applicationsDatabase table name |
Class |
Database column name |
FileNet P8 property
name |
relationship |
Not applicable |
tail_id and head_id |
Not applicable |