I'm looking into using components implemented in BPEL as part of a Tuscany Java application, but I've come across what seems to be a limitation of ODE - that it does not support clustering out of the box. It looks like if multiple ODE instances in a cluster are using a single centralized database they're not able to coordinate their actions and might end up executing the same BPEL process instance multiple times.
Does anybody have any experience in running components using implementation.bpel in a clustered environment and can provide more insight into how this would work? >From my initial investigation it looks like one option is to move from ODE to >a different BPEL engine that supports clustering and communicate with it using >standard web service calls, but that means that we lose the benefits of tight >Tuscany integrations and any calls back from the BPEL process to components >hosted in Tuscany also have to go over the SOAP WS communication stack. I guess the ideal solution would probably be to implement a new Tuscany implementation type that uses an alternative BPEL engine instead of ODE, but I'm not sure how complex that would be. Is there any documentation that describes what it would take to implement a new Tuscany implementation type? Thanks Anuj
