This is a business / architectural question - not necessarily a technical one.
Looking for a paper/whitepaper etc discussing how the three of these all work together in an enterprise environment. As far as I can tell: Messaging gives an implementation under the JMS API and perhaps an adapter to something like IBM MQ | | ESB gives webservices and often, not though not exclusively, a XML/SOAP layer on top of msg'ing. It also gives transformations, ACID transactions and a process flow (maybe session beans or maybe a scripting language like IBM broker) | | BPM gives a process flow with ACID transactions and a cool GUI for modeling the flow. A primary language used for BPM modeling is XML for BPEL | | A rules engine also models a business process. It can be a java lib called by a session bean or the rules can be exposed as webservices from their own 'container' like ILOG and others. | | So, what processes go in the rules engine? in BPM? In the ESB? | | When is it best to embed the rules code behind a sessionbean (maybe exposed as a WebService), called be the esb code? called by the bpm code? In a Rules container and centralized? | View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4000645#4000645 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4000645 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
