Planning to Implement Data Exporter

Because Data Exporter is disabled by default, it must be configured to become operational. Configuration of Data Exporter requires several decisions to be made before configuration can begin.

• Which data types will be exported?

• Which techniques will be used to capture data for each data type?

• How often will data be exported for each type?

• What will be in the exported schema for each type?

• Will a custom Warehouse Interface Code (WIC) factory class be required?

When Data Exporter is enabled, the default configuration exports all attributes of all data types. This may cause an unnecessary processing burden on Waveset and the warehouse by consuming warehouse storage that will never be used. Data warehousing tends to be conservative and capture data when there is a chance the data might be used later. You do not have to export all the data that can be exported. You can configure which data types to export and restrict some events from being export.

Once these decisions above have been made, use the following steps to implement Data Exporter:

To Implement Data Exporter

1. (Optional) Customize the export schema for selected types and regenerate the warehouse DDL. Refer to the Customizing Data Exporter in Oracle Waveset 8.1.1 Deployment Guide for more information.

2. Create a user account on the warehouse RDBMS and load the warehouse DDL on that system. Refer to the Customizing Data Exporter in Oracle Waveset 8.1.1 Deployment Guidefor more information.

3. Configure Data Exporter, as described in Configuring Data Exporter.

4. Test Data Exporter to ensure it was configured correctly. See Testing Data Exporter for more information.

5. (Optional) Create forensic queries that can search data written to the data warehouse. See Configuring Forensic Queries for more information.

6. Maintain Data Exporter using JMX and monitoring the log files. See Maintaining Data Exporter for more information.