[riftsaw-commits] riftsaw SVN: r1191 - trunk/docs/docbook/userguide/src/main/en-US/module.
Author: jeff.yuchang
Date: 2010-12-06 03:57:02 -0500 (Mon, 06 Dec 2010)
New Revision: 1191
Modified:
trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml
Log:
* Add a section of describing configuring exuection events.
Modified: trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml
===================================================================
--- trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml 2010-12-06 08:52:54 UTC
(rev 1190)
+++ trunk/docs/docbook/userguide/src/main/en-US/module/admin.xml 2010-12-06 08:57:02 UTC
(rev 1191)
@@ -373,4 +373,38 @@
</table>
</section>
+ <section>
+ <title>Enable Execution Events</title>
+
+ <para>
+ Apache ODE generates a set of events on the process running. below is the steps
for you to enable it.
+ for more detail information on this, please consult the <ulink
url="http://ode.apache.org/ode-execution-events.html">ODE's Execution
events guide</ulink>.
+ </para>
+
+ <para>
+ <itemizedlist>
+ <listitem>
+ In deploy.xml, adding <filename><process-events
generate="all"/></filename>.
+ </listitem>
+ <listitem>
+ Adding following two properties in the
<filename>bpel.properties</filename>.
+ <para>
+ bpel.event.listeners=org.apache.ode.bpel.common.evt.DebugBpelEventListener
+ debugeventlistener.dumpToStdOut=on
+ </para>
+
+ <para>
+ By registering the DebugBpelEventListener, it will use the log's DEBUG
level for the BpelEvent information.
+ By setting the
<filename>debugeventlistener.dumpToStdOut=on</filename>, it will render the
information on the console as well.
+ </para>
+ </listitem>
+ </itemizedlist>
+ </para>
+
+ <para>
+ We've also provided an out-of-box example to demonstrate the adding a custom
listener. Please see the <filename>bpel_event_listener</filename> example for
more information.
+ </para>
+
+ </section>
+
</chapter>