Preparing a database for the case history store

Edit online
Draft comment:
This topic is shared by BAW, CP4BA. Last updated on 2025-03-13 12:15
If you plan to use the Timeline Visualizer widget to view case history over time, you must prepare a database to record extended case history data.

Before you begin

If the case history store is configured to use an Oracle database and the Oracle server has ADVANCED compression enabled, the case history store will be created with ADVANCED compression. However, additional Oracle licensing might be required. For more information, see Additional Oracle licensing might be required when using ADVANCED compression in the Case History store External link opens a new window or tab.

About this task

The system can store extended case history data in the database instance that is used for the target object store, or in a separate database instance. Consider the capacity of your database server, the case size, and the case load when determining where to store extended case history data.

When extended case history data is stored in the database instance that is used for the target object store, you do not need to define an additional JDBC data source, and you can easily back up the case history store along with the target object store. However, including the case history data increases the load on the database server, and this can have a negative impact on performance. Defining a separate database on the same remote database server as the target object store can also degrade performance.

Alternatively, the system can store extended case history data in a separate database instance. For example, you might want to use a separate, remote database server if I/O throughput is problematic. If the system stores extended case history data on a different remote database server, you can get additional disk arms, disk space, CPU, and memory to support it.

Restriction: You cannot delete cases or prune extended case history data. Ensure that there is sufficient disk space to store extended case history data.

The following procedure refers to IBM Content Cortex tools and procedures to set up a database for your case history store.

Procedure

To store extended case history in a separate database instance:

  1. Prepare the database for the case history store.
    For more information, see Database administrator installation tasks External link opens a new window or tab.
  2. Create JDBC data sources. Run the Configure JDBC Data Sources task by using the IBM Content Cortex Configuration Manager.
    For more information, see Editing the Configure JDBC Data Sources tasks External link opens a new window or tab and Configuration Manager reference External link opens a new window or tab.
  3. Create a database connection.
    For more information, see Creating a database connection External link opens a new window or tab. Based on performance considerations, you might want to share data sources. For more information, see Sharing data sources External link opens a new window or tab. You enter the database schema name when you configure and enable the case history store by using the IBM® Business Automation Workflow administration client.

What to do next

Select custom properties to audit and enable the case history store by using the IBM Business Automation Workflow administration client.