Enabling ODWEK tracing

ODWEK tracing writes trace statements to the binary file arswww.trace. ODWEK tracing assists IBM support in problem determination; however, as with any form of tracing, you might notice a decline in performance when you enable ODWEK tracing. Enable ODWEK tracing only when you need to re-create a problem and as directed by IBM support.

About this task

By default, ODWEK appends information to the trace file until you disable tracing; it does not cycle through the file. You must periodically delete old trace files. If you need to set a maximum size that your trace file can grow to, you must set a value using the ODConfig.MAX_TRACELOG_SIZE field when you create your ODConfig object. For more information, see the Javadoc.

Procedure

To enable the ODWEK tracing, do the following steps:

Add code to your application that indicates where to save the trace information.
The following code is an example:
```
ODConfig cfg = new ODConfig(
/*AfpViewer*/           ODConstant.PLUGIN,
/*LineViewer*/          ODConstant.APPLET,
/*MetaViewer default*/  null,
/*MaxHits*/             500,
/*AppletDir*/           "/applets",
/*Language*/            "ENU",
/*TempDir*/             "c:\\temp",
/*TraceDir*/            "trace_directory",
/*TraceLevel*/          trace_level);
```
The following list describes what values to provide for the TraceDir and TraceLevel:

TraceDir

Specify the full path of the directory where you want ODWEK to store the trace file. If you need to enable logging for extended periods of time, make sure that the directory is on a storage device with sufficient free space.

TraceLevel

Specify a numeric value (0, 1, 2, 3, or 4), as directed by IBM Software Support.
Re-compile and restart your ODWEK application.
Re-create the situation that created the problem.
Send the arswww.trace file to IBM Software Support.