Configuring production target object store indexes
Your database administrator must create a four-part composite index for each production target object store that is used for case management. That database retrieval index is required for efficiently retrieving the case history in the Event table in target object stores.
About this task
Restriction: Create the index for production
target object stores that do not already have a four part index. In
previous releases of IBM® Case Manager,
a two part index was recommended, but a four part index is more effective.
If a two part index was previously applied, you must replace it with
the more effective, four-part index.
The index contains unique key values, and the four-part index uses the following format: <case_folder_column, audit_sequence DESC, object_class_id, source_object_classid>.
- case_folder_column
- The name of the database column that contains the CmAcmCaseFolder property. The property value is a globally unique identifier (GUID). The database column name might not be the same in different target object stores.
- audit_sequence
- The database column name for the CmAuditSequence property is always named audit_sequence in all target object stores. The audit_sequence column provides an accurate time sequence for events. The property type is float, but the property values are sequentially increasing positive integers that are generated as new events are stored in the Event table.
- object_class_id
- The name of this column is the same in all target object stores. This column is included in the index to make filtering the case history events more efficient when you search the case history.
- source_object_class_id
- The name of this column is the same in all object stores. This column is included in the index to make filtering the case history events more efficient when you search the case history.
Procedure
To create the four-part index: