JBossProcessServerDemoGuide.PDF

J Boss Process Server Demo Guide Overview For years, Java programmers have baked business rules and process logic into Java code. There is something terribly wrong with having to re-write and re-deploy code every time a business process or rule changes but BPM and rules technology is known as e pensive, niche technology. JBo ss, a division of Red Hat, has broken the high cost barrier with an Open Source BPM and Rules Engine offering. Pragmatic, Java developer friendly, enterprise grade BPM and Rules Engine technology is now available to the masses. By combining the leading J2 EE Application Server (JBoss Application Server), the leading Open Source BPM solution (jBPM) and the leading Java based Rules engine (Drools), Red Hat has forever changed the BPM and Rules Engine landscape. Problem JBo ss Rules has garnered a fair amount of fan-fair by providing a very good, general purpose, Java rules engine framework. Unfortunately, JBo ss Rules, also known as Drools, doesnt provide an effective rules management mechanism. Many development groups struggle with the following: ● How should the JBoss Rules binaries be packaged/deployed to the server? Its easy to bundle the JBoss Rules binaries in each rules engine enabled EAR, but its far more likely that several applications will share a single set of JBo ss Rules binaries. ● How should the POJO (Plain Old Java Object) model be packaged/deployed? Again, its likely that several applications will need to make calls to the same rules engine instance and it makes sense to have a single POJO model that is shared. ● How should rules be version controlled? ● How should rules be deployed? Ideally, rule deployment will not necessarily mandate application re-deployment. It would be nice to GUI enable rules management/deployment. ● How should rules be stored for application usage? Caching