Use the Case Analyzer compression
wizard to compress the Case Analyzer store.
You can use the Case Analyzer compression
wizard only on Microsoft SQL Server databases.
About this task
Important: The
Case Analyzer compression wizard is not
supported on operating systems such as AIX® and Linux®. However, there is an alternate procedure that you can use to compress
the
Case Analyzer database when
Content Platform Engine server is running on these types of operating systems. For
more information, see the following technical support document:
http://www.ibm.com/support/docview.wss?uid=swg27046421

.
As the fact tables in the Case Analyzer store grow over time, they
require more disk space and longer cube-processing times. Compressing
the Case Analyzer store reduces
the fact table sizes by aggregating, or "rolling up," measures across
common dimensional values, with a resulting loss of information.
For
example, consider a system that is composed of insurance claim data.
Table 1. Sample insurance claims data
| Date |
Claim Type (dimension) |
Claim Number (dimension) |
Workflow count (measure) |
| 1-2-12 |
Homeowners |
18275 |
1 |
| 1-5-12 |
Auto |
67251 |
1 |
| 1-26-12 |
Auto |
36185 |
1 |
| 2-22-12 |
Auto |
47477 |
1 |
| 4-13-12 |
Auto |
92487 |
1 |
| 4-28-12 |
Auto |
37530 |
1 |
| 5-15-12 |
Homeowners |
88357 |
1 |
Compressed by month and claim type, the data is aggregated
by month. The precise date and actual claim number information is
lost.
Table 2. Sample insurance
data that is aggregated by month
| Date |
Claim Type (dimension) |
Claim Number (dimension) |
Workflow count (measure) |
| Jan 2012 |
Homeowners |
<unknown> |
1 |
| Jan 2012 |
Auto |
<unknown> |
2 |
| Feb 2012 |
Auto |
<unknown> |
1 |
| April 2012 |
Auto |
<unknown> |
2 |
| May 2012 |
Homeowners |
<unknown> |
1 |
Procedure
- Before you start the Case Analyzer store
compression, do the following steps:
- Back up the Case Analyzer store.
Compressing the Case Analyzer store
cannot be undone or canceled.
- Set the Microsoft SQL Server database
timeout setting to unlimited:
- Open Microsoft SQL Server Management
Studio.
- Navigate to the database instance. Right-click and select Properties.
- On the Connections tab, make a note of
the current setting for the Query time-out,
and then set it to 0 (unlimited).
- Click OK.
- Close Microsoft SQL Server Management
Studio.
- Set the file path for the JDBC driver in the cacompression.bat file:
- Download the Microsoft SQL Server JDBC
driver.
- Edit the cacompression.bat file,
and set the JDBC driver JAR file path:
set JDBC_DRIVER=installation_directory\sqljdbc_4.0\enu\sqljdbc.jar
For
example:
set JDBC_DRIVER=c:\sqljdbc_4.0\enu\sqljdbc.jar
- Run the cacompression.bat file that
is in the default path.
C:\Program Files\IBM\FileNet\ContentEngine\tools\PE\cacompression.bat Case_Analyzer_store_name
Important: When
you issue the cacompression command to compress
the Case Analyzer store against
a workflow system in a tenant domain of a multi-tenant environment,
you must specify the -N tenant_domain_name parameter
in the command. To specify this parameter, you must be a member of
the workflow administration master group. This group is in the master
domain directory service provider and has permission to run workflow
system administrative tools in the tenant domain in which the group
is designated a master group.
- Log in as gcd_admin.
- Enter the following information in the Connect
to Database window.
Table 3. Case Analyzer database
connection properties
| Field |
Description |
| Database Type |
SQL Server is the only
valid database type |
| Database Server |
Server name of the Case Analyzer store |
| Database Instance |
Case Analyzer database
instance name. For the default instance, leave this field blank. |
| Database Name |
Name of the Case Analyzer database |
| Database Port |
Port number of the Case Analyzer database server |
| Schema Name |
Schema name for the Case Analyzer store |
| Database User Name |
Case Analyzer database
user name |
| Database User Name Password |
Password for Case Analyzer database user name |
- Set the Case Analyzer compression
intervals.
- Select one or more time intervals, and specify the start
and end dates. You cannot compress the current month data.
You can choose to compress data by monthly or daily intervals,
or a combination of the two. For example, if you have data that ranges
from the date of July 16, 2008, to the current date of November 12,
2012, you can compress the older data (from 2008 through 2011) into
monthly intervals. More recent data (from January 2012 to October
2012) can be compressed into daily intervals. The current month data
(November 1, 2012, to November 12, 2012) remains uncompressed. The
following table demonstrates the example time intervals.
Table 4. Compression interval
example
| Interval |
Start Date |
End Date |
| Month |
Jul 16, 2008 |
Dec 31, 2011 |
| Day |
Jan 1, 2012 |
Oct 31, 2012 |
- Modify the Temp Directory if
necessary. The temporary directory must have available space equivalent
to the size of the current Case Analyzer store.
- Click Next.
- Select the dimensions to be compressed. You can compress
dimensions for user-defined data fields only. By default only dimensions
that have more than 10,000 rows are shown.
- Click Show all dimensions to
display all dimensions.
- Click Next.
- Review the compression settings on the summary page.
- Click Back to make setting changes.
- Click Next to start the compression
process.
Important: You can stop the compression process
after it is started; however, if you do so, you must restore the Case Analyzer store from a backup.
- Click Finish when the process is
complete.