The problem here is that many people get the impression that the sample webapp is the console. They think it is the way to do it, and it is responsible for managing jBPM. It's a SAMPLE webapp, giving EXAMPLES on how to monitor/etc. I think something needs to be done (no clue what) about people getting the wrong impression. Many just think it is jBPM itself, and that's how you use it. Crack the webapp code open, look at what it is doing, and copy/modify/paste into your non-web application. Learning the jBPM API allows you to do anything without relying on the example webapp. Write your own monitoring tool how you want, and you'll be set. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3959245#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...