Configuring auditing
You can configure auditing for use with the analytics tools that are supported by Case Analyzer. You can also configure auditing to track the history of cases by using the Timeline Visualizer widget. You can configure auditing for a deployed solution in a development environment, or in a production environment.
About this task
Choose properties to audit that are meaningful to your business and solution. For example, a financial organization might want to audit properties such as LoanAmount, ApprovalStatus, and Priority. A case analyst might be interested in the number of occurrences of a particular case type, or the length of time that case workers require to complete a particular task.
You specify properties to audit by using the audit configuration wizard in the IBM® Business Automation Workflow Case administration client. Select document properties and properties of each case type for the solution that you want to audit. If tasks are defined for the case type, you can select the task and then select the task properties that you want to audit. To view custom properties in the extended history, you must select those properties for auditing. In addition, some system properties are automatically selected for auditing.
Audit configuration settings are stored in an audit manifest file. You can move an audit manifest from one environment to another by using the export and import audit configuration wizards. For example, you can create and check your audit configuration in a test environment before you import the audit configuration into production.
After you specify properties to audit and apply the audit configuration to a solution, you can use Case Analyzer to generate chart-based reports that are based on statistical information that is gathered from the system. For information about additional configuration steps that are required before you can use Case Analyzer and other case analytics tools, see Integrating IBM case analytics tools.
To track the extended history of cases by using the Timeline Visualizer widget, you must define a case history store. You can store extended case history data in the database instance that is used for the target object store. Alternatively, you can store extended history data in a separate database instance. For example, you might want to use a separate, remote database server if the I/O throughput is problematic. For more information, see Preparing a database for the case history store.
Procedure
To configure auditing: