Troubleshooting Data Exporter

The volume and variety of data flowing through the exporter increase the possibility of problems occurring during data export.

Beans and Other Tools

Data Exporter performance and throughput can be monitored through the JMX management beans provided in Waveset. To minimize the performance impact of exporting data, Waveset uses some memory-based queues that are volatile. If the server terminates unexpectedly, the data in these queues will be lost. You can monitor the size of these queues over a period of time to judge your exposure to this risk.

Model Serialization Limits

Data Exporter must queue some objects to ensure they are available for export at the appropriate time. Queuing these objects is done by Java serialization. However, it is possible to include data in an exported object that is not serializable. In this case, the exporter code should detect the non-serializable data and replace it with tokens that indicate the problem, allowing the rest of the object to be exported.

Repository Polling Configuration

Each type may specify an independent export cycle. The administrator interface provides an easy way to define the simpler cycles which will be sufficient for most purposes. However, the export cycles can also be specified in the native cron style, which supports even more flexibility.

Tracing and Logging

The default WIC code uses Hibernate to provide object/RDBMS mapping for the exported data objects, but using the Hibernate library means the tracing and logging is not fully integrated. The actual WIC code can be traced by using the com.sun.idm.warehouse.* package. However, enabling Hibernate logging requires a different technique.

To pass a Hibernate property to the code that initiates the Hibernate sessions, add an attribute to the DatabaseConnection configuration object. You must prefix the attribute name with an “X”. For example, if the native property name is hibernate.show_sql, you must define it in the configuration object as Xhibernate.show_sql. The following example causes Hibernate to print any generated SQL to the application server’s standard output.

<Attribute name=’Xhibernate.show_sql’ value=’true’>

By default, Hibernate uses C3P0 for connection pooling. C3P0 uses the java.logging facility for its logging, which is controlled by the $JRE/lib/logging.properties file.