Debugging BIP under EBS
By Tim Dexter on Apr 17, 2009
Apologies, Im getting more and more sporadic ... will try and do better!
Today I wanted to highlight some work Pieter has been doing on our behlf in support. He has a very useful note in metalink on debugging BIP issues under EBS. Check out
Note 364547.1 Troubleshooting Oracle XML Publisher For The Oracle E- Business Suite
Recently an enhancement has been made to the current capabilities, which Pieter will include into the note in due course but here's the details for now.
Currently, to request for XDO debug log, you have to create a file xdodebug.cfg, and copy it in to <JRE>/lib directory. This is sometimes very difficult to do this step because:
1) When there are multiple JDK/JRE installed in a system, it is sometime
difficult to know which one is being used.
2) The <JRE>/lib directory is locked, only writable by top admin person
To alleviate this issue the enhancement provides the ability to turn on debugging for a specific RTF template.
There is a new XDO propety that can be embedded into the template:
* Name: xdo-debug-level
* Default: OFF
* Allowable values: STATEMENT, ERROR, OFF
When it is set to any value but "OFF", it will turn in debug mode.
The debug log directory will be in
2) <Java java.io.tmpdir>/xdodebug (if system-temp-dir is not defined)
- The following comment added to the XSL template or FO file will also turn on XDO debug mode for that thread.
<!-- xdo-debug-level="STATEMENT" -->
The comment must reside within the first 512 bytes in the file ie get it into the top of the document.
The value of debug_level is not case sensitive,
<?xdo-debug-level:"statement"?> are the same.
should make life a whole lot easier for you EBS folks. Its being released to the 5.6.3 code line so if you want it you need to get to that level. Not available quite yet, just being tested but watch out on Metalink for the patch against # 8359991.