If you use the standalone server or with OBIEE and use OC4J as the web server. Have you ever taken a looksee at the console window (doc/xterm) that you use to start it. Ever turned on debugging to see masses of info flow by that window and want to capture it all? I have been debugging today and watched all that info fly by and on Windoze gets lost before you can see it!
The BIP developers use the
System.err.println()methods in the BIP applications to generate debugging formation. Normally the output from these method calls go to the console where the OC4J process is started. However you can specify command line options when starting OC4J to direct the stdout and stderr output directly to files. The
?err parameters tell OC4J which file to direct the output to.
All you need do is modify the oc4j.cmd file used to start BIP. I didnt get fancy and just plugged in the following to the file under the start section. I just modified the line:
set CMDARGS=-config "%SERVER_XML%" -userThreads
set CMDARGS=-config "%SERVER_XML%"
Bounced the server and I now have a ballooning pair of debug files that I can pour over to my hearts content. The .out file appears to contain BIP only log info and the .err file, OBIEE messages.
If you are using another web server to host BIP, just check out the user docs to find out how to get the log files to write.
Note to self, remember to turn off the debug when Im done!