tag:blogger.com,1999:blog-5869426.post5034596127942876317..comments2024-03-25T09:15:58.430+00:00Comments on Drools & jBPM: Dynamic BPMMark Proctorhttp://www.blogger.com/profile/03304277188725220501noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-5869426.post-38075462088625302332010-05-19T08:23:58.235+01:002010-05-19T08:23:58.235+01:00Interesting post - basically confirms what we'...Interesting post - basically confirms what we've been doing for years...<br /><br />Gartner, welcome to the present ;)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5869426.post-72108669787597109632010-04-08T21:37:43.740+01:002010-04-08T21:37:43.740+01:00One thing that should be noted is the importance o...One thing that should be noted is the importance of service orientation - this quote from the Vosibilities blog ( http://www.vosibilities.com/soa/bpm-and-soa-belong-together/2009/09/10/ ) explains:<br />"Workflow, human interaction, reports, event processing — all need to be incorporated in a service-based architecture if we’re ever to get to better business (i.e. BPM) and IT (i.e. infrastructure) alignment. In other words, BPM itself needs to be service-oriented."Unknownhttps://www.blogger.com/profile/14176555560990790605noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-9473254812541422882010-04-01T19:34:13.337+01:002010-04-01T19:34:13.337+01:00I'm looking forward to your technical post. M...I'm looking forward to your technical post. Most of the collateral I've read about ACM since seeing this blog doesn't really say much concrete.Kenhttps://www.blogger.com/profile/11583717134076863159noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-4463360473977066082010-03-30T21:24:14.923+01:002010-03-30T21:24:14.923+01:00Hi Kris - interesting post. For further thoughts o...Hi Kris - interesting post. For further thoughts on this browse <a rel="nofollow">http://tibcoblogs.com/cep/category/bpm/</a> . <br /><br />Also note the European academics are starting to use the term "event driven BPM" or edBPM - although of course all business processes are event driven, this term is meant convey "event-focused". <br /><br />CheersPaul Vincenthttp://tibcoblogs.com/cepnoreply@blogger.comtag:blogger.com,1999:blog-5869426.post-88206706887055242962010-03-30T14:59:11.825+01:002010-03-30T14:59:11.825+01:00Let me see if I understood this ACM (for lack of a...Let me see if I understood this ACM (for lack of a better name) thing: you pick a context, a set of data, or whatever (a "case", that has a "current state"), think on it or execute some rules on it, and then pick a "next state" from a list of known possible states.<br /><br />The system records the path you (and the rest of the users that work on the case) follow in a similar manner as a BPM system records execution. Only that there's no process definition, but in some way, you make it up as you go or as you need.<br /><br />It could be an interesting tool for process exploration and discovery...<br /><br />MicheleMichele Maurohttps://www.blogger.com/profile/17763664217760947014noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-10839437869132603992010-03-29T23:20:50.305+01:002010-03-29T23:20:50.305+01:00The Drools engine is capable of event processing (...The Drools engine is capable of event processing (Fusion) and executing processes (Flow). To integrate it into your application, pipelines will allow you to stream events (as input) from different sources to the engine. The engine can then process these events and start / signal processes whenever necessary.<br /><br />To integrate with external services (as output), take a look at work items, they will allow you to declaratively specify what needs to happen in your processes / rules, where you can then link that to a specific implementation (e.g. using ServiceMix) at runtime.Kris Verlaenenhttps://www.blogger.com/profile/11456672157934554969noreply@blogger.comtag:blogger.com,1999:blog-5869426.post-70794569975934902242010-03-29T13:03:44.397+01:002010-03-29T13:03:44.397+01:00Very interesting post, I'm defining (architect...Very interesting post, I'm defining (architecture, components, flows, metadata, etc.) a system that will support the processing of a huge amount of events received through interfaces like plain tcp, WS, JMS.<br />Processes are building blocks that could be part of workflows.<br />I'm thinking about the integration of Drools (w/ Flow) and Apache Service Mix, any suggestion? RobRobertonoreply@blogger.com