« File-based rules repository in a BPEL Decision Service (10.1.3) | Main | File-based vs. WebDAV Rule Repositories (10.1.3) »

Enabling debug output in a BPEL Decision Service (10.1.3)

Section 18.7.2 of the Oracle BPEL Process Manager Developer's Guide 10g (10.1.3.1.0) contains instructions for enabling debug logging for a decision service. However, unless you are familiar with BPEL debugging already, there is one step missing. The logging is at the "debug" level, but the BPEL server sets the logging level to "info" by default.

To change the logging level to "debug" so you can see the logging information from your rules:


  • From the BPEL Control panel, click on the "Configuration" tab.
  • From that tab, click on the "Logging" sub-tab.
  • For the "Logger Name" "default.collaxa.cube.engine.bpel", select "Debug" for the "Logging Level.
  • Click the Apply button at the bottom of the page.

Debugging output is now enabled and will be available in the OPMN log for the domain in which the process is deployed.

TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mte1521/mt-tb.cgi/8989

Post a comment

About This Entry

This page contains a single entry from the blog posted on December 16, 2008 10:51 PM.

The previous post in this blog was File-based rules repository in a BPEL Decision Service (10.1.3).

The next post in this blog is File-based vs. WebDAV Rule Repositories (10.1.3).

Many more can be found on the main index page or by looking through the archives.

Powered by
Movable Type and Oracle