Tracing Global XPRESS

While not generally recommended, you can use global XPRESS tracing to trace any and all XPRESS code, wherever the code is located. For example, you can trace XPRESS code in forms, views, and workflows. The resulting trace shows XPRESS output that can expose potential problems.

XPRESS tracing is disabled by default because it produces a large amount of output, which affects system performance.

See Testing Your Customized Form in Oracle Waveset 8.1.1 Deployment Reference for more information about tracing XPRESS functions.

To Enable Global XPRESS Tracing:

1. Open a command window.

2. Change directories to config/Waveset.properties in the default Waveset installation directory.

3. Open the config/Waveset.properties file and edit the xpress.trace line to read:

   xpress.trace=true

4. Save the Waveset.properties file.

5. Restart your application server or reload the Waveset.properties file from the Waveset debug pages.

6. Replicate the XPRESS trace output to a file by adding this line to the Waveset.properties file:

   xpress.traceFile=FileName.txt

   xpress.traceFileOnly=true

   When you set xpress.traceFileOnly=true in Waveset.properties, all XPRESS statement evaluations will generate trace messages to a file specified by xpress.traceFile. Otherwise, when xpress.traceFile has a value, trace messages are redirected to both the console and a file.