Siebel Reports Guide > Troubleshooting Siebel Reports >

Enabling and Disabling Debugging for Siebel Reports in Disconnected Mode

You can configure the Oracle BI Publisher XDO Engine to create log files that capture detailed information about errors that occur while generating Siebel Reports in disconnected mode. The administrator can use the log files to learn when there are report generation problems with the JAR (Java ARchive) files or the Oracle BI Publisher (RTF) layout templates.

Enabling Debugging for Siebel Reports in Disconnected Mode

Use the following procedure to enable debugging for the Oracle BI Publisher XDO Engine.

To enable debugging for Siebel Reports in disconnected mode

1. In a text editor such as Notepad, create a new file entitled, xdodebug.cfg, and type in the following for use as a sample file:

   LogLevel=STATEMENT

   LogDir=<path to logging directory>

2. Place the file in the jre\lib directory used by the Siebel client (for example, C:\Program Files\Java\jre1.6.0_07\lib) and make sure that the directory specified by the LogDir parameter exists. The resulting log files from the report generation will be created at this location.

If an error occurs while generating reports in disconnected mode, an xdo.log file is created and saved to the path specified in the .cfg file. Use this log file for troubleshooting.

Disabling Debugging for Siebel Reports in Disconnected Mode

To optimize the performance of Siebel Reports in disconnected mode, you might want to disable debugging for the Oracle BI Publisher XDO Engine.

To disable debugging for disconnected mode

1. On the computer where Oracle's Siebel Developer Web Client is installed, copy the xdo.cfg in the jre\lib installation folder to another computer for backup purposes.
2. Remove or rename the xdo.cfg in the jre\lib directory used by the Siebel client.