Hello,
I have JBPM 3 deployed in a number of JBOSS AS 5.1. I set up the application server and JBPM to use one single MYSQL database for persistence (--> only one shared database). The idea is to use the database as a "synchronization mechanism" between the various JBPM instances. I'm now trying to find out if this is supported by JBPM 3 (& Hibernate) and whether the following use-cases will work:
1/ New ProcessDefinition
- Create a new ProcessDefinition on one server and store it into the database.
- On a second server, obtain the list of ProcessDefinitions using the JBPM API (GraphSession::findAllProcessDefinitions).
Will the new ProcessDefinition be in the list?
2/ Resume process instance
- On one server, start a new process instance and store the state into the database
- On a second server, retrieve the process instance (based on instance ID) and make the process continue (signal)
Is this possible?
The idea is to have multiple JBPM run-times "virtually" working together without a need for JBOSS AS clustering, Hibernate caches etc. I believe Hibernate does some caching (don't know exactly how) and I fear this might cause this setup not to work (completely). Any info on this would also be welcome.
All answers & help are very appreciated.
Thanks,
Sven.