Prafull, It all depends on how you want to store the data that you need to do BAM. You could consider the audit logger as an example of how you could do logging (although it might probably be better to not use XML logging for BAM, but rather use a database or feed the events directly into Drools Fusion for processing). Quoting Prafull Kumar <to_prafull(a)yahoo.com&gt;: The event listeners provide access to the process instance object, so you can access all runtime information, including variable values, etc. You can then customize how to store that information. You should probably be looking at the history log (in the drools-bam module) for this kind of features, which maintains a history of what happens at runtime (including variable values) based on the events. Again, you could look at this as an example that you can tweak according to your needs. Depending on whether you use persistence or not, you should be looking at the WorkingMemoryDbLogger or JPAWorkingMemoryDbLogger respectively: http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-process/... How your event listener works is up to you. If you use persistence, you should make sure the events are created as part of the transaction the events are generated in. The two default implementations don't use asynchronous handling of events, but this could be added if necessary by updating the listener. When using the JPA version, all updates to the history log are already batched as part of one commit, so this should improve performance. You should also make sure that you only log the data that you are planning to use (at the level of detail you'll be using it) to avoid storing too much data and impacting performance. Kris Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm