I have two ears, and several clusters at my environment.
We have the following scenario:
JBPM is used in two EARs, and we are upgrading from 3.1 to 3.2.3.
The EARs can be deployed on the same cluster, the same node of a given cluster, or in two separate clusters.
We would like to take advantage of the new timer and asynchronous continuation services in JBPM.
Questions:
To take advantage of the Enterprise features in JBPM 3.2+, should I install the jbpm-enterprise-bundle.ear, or should I incorporate the pieces into my existing EARs?
The problems I see with incorporating the services into my EARs is that I would have several services running, and I may need to rename the services to allow the EAR deployments in the same server node.
The problem I see with breaking out my workflows and action handlers into Process Archives is that the Process Archive, to my understanding, can not include libraries. Therefore, there is no way to make reference to the local/remote interfaces in my action handlers.
Also, I am wondering if I use the out of the box jbpm-enterprise-bundle.ear, it will pick up jobs from the database for the EARs, whether they are deployed to a given node or not.
If I decide to move the timer and asynchronous services into my EARs, will they need to be separate into separate data sources, or does JBPM include the service name and filter on the service name internally?
Thanks for the insight.
Brad
