AnsweredAssumed Answered

Running Embedded - best use cases

Question asked by dereksurfs on Jun 30, 2014
Latest reply on Jul 5, 2014 by dereksurfs

I am interesting in hearing of some views on use cases when running embedded makes sense?

A little background regarding our client's situation.  They are running legacy jBPM (~v. 3.2) which they are very unhappy with.  They have a very limited staff both in terms of BPM skills and number of developers.  Their system is also a legacy system of ~ 85% Oracle PL/SQL & 15% Java code.  In a nutshell jBPM was poorly architected, implemented and integrated in a tightly coupled fashion with their current system and now it is their weakest link and greatest headache.  In addition it did not have a good migration path forward for their 'limited' team working with it.  We need something much more loosely coupled to their legacy system and easier to deploy and maintain.  One technical adviser recommended ditching BPMs altogether and writing everything in Java for simplicity sake.  IMO, that is not very practical given the nature of the application which has extending processes and human interaction among other things.

I've thought that embedding a BPM might be easier for them to maintain and understand vs. a separate deployment.  I'm just not sure of the pros and cons.  The Java app will run in Weblogic app server.  Thanks for any tips or suggestions regarding the benefits of embedded over other configurations.