OK. Will look at running jBPM3 and jBPM4 on Tomcat. That might solve some other issues. My fear of running two ProcessEngines is that one of them is really the main ProcessEngine the other is secondary. The main ProcessEngine would deal with all external comms, and be the central point of contact. I can see, an have too often in my 20 years or so doing this, somebody coming along in 6 months and using the secondary ProcessEngine as the main engine and totally wrecking any architecture that was set up. I realize that this is a management issue but if you don't introduce the second ProcessEngine the problem can't arise. This is one way to manage complexity. I like to keep it simple. One ProcessEngine is enough for our needs. With that said I am still going to look at using two engines because the API is better. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4253332#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...