Turn ON Logging for BI Publisher for debugging code

By default in BI Publisher detailed log will not be enabled. So it becomes tough to identify the problems whether in the XML data file/Template file /Application/Code or App engine.

So we cannot come to know where exactly error occurring. That’s the reason we have turn on logging for BI Publisher for Debugging reports for debugging. Have to create xdodebug.cfg file and which will give us XDO logging information that are related XML, XSL, Translation (XLIFF) and Template files such as PDF, RTF, XSL in the temporary directory specified in LogDir parameter.

Steps to Turn ON Logging for BI Publisher for Reports debugging

1.Create a folder xdolog and place it under

<Middleware_Home>/user_projects/domains/bifoundation_domain/config/bipublisher

This has to be used in LogDir parameter in step 2.

Note: The above mentioned path is optional .You can create it anywhere

2.Create a file named xdodebug.cfg and place it under

<Middleware_Home>/Oracle_BI1/jdk/jre/lib/

3.Add below listed lines in xdodebug.cfg file

Under Windows

LogLevel=STATEMENT
LogDir=c:\<Middleware_Home>\user_projects\domains\bifoundation_domain\config\bipublisher\xdolog

Under Unix:

LogLevel=STATEMENT
LogDir=<Middleware_Home>/user_projects/domains/bifoundation_domain/config/bipublisher/xdolog

4.Retest the issue

5.Check the files created in the specified LogDir (xdolog) directory.Here you can see XDO.log

6.Remove xdodebug.cfg when finished replicating the issue.

The logging is specifically useful for troubleshooting the Template(RTF/PDF) or Data File(XML file) specific issues. The generated XML file is the actual data file which is run from the MS Word Design Helper Preview mode to narrow down the issue.