JBoss World Boston notes, JBoss BPM Past, Present & Future, John Graham
Past :
jBPM
– based on jPDL
– deployments : stand-alone, SOA-Platform, Seam
– jBPM 3, exising, stable
– jBPM 4, improved system, community effort
drools
– business rules
– BPM in drools flow
Riftsaw
– WS-BPEL 2.0
– based on Apache ODE
– release 2.1
– integration with SOA
Savara
– WS-CDL : choreography description language
– Pi calculus
– testable architecture, development validation, execution governance
– BPMN 2 work in progress
Present :
– Perspectives : rules-based, process-based, SOA-driven
– Need to integrate
– Need to avoid overlap
– Enable emergent usage
– Where to go?
jBPM 4 and drools flow are integrating and will be jBPM 5 which should be available in 2011
Key characteristics
– Business process engine
— BPMN2 native execution
— lightweight, embeddable
— generic process engine
– Full life cycle support
– Higher-level, domain-specific processes
– Powerful business rules and vent processing integration
BPMN 2.0
– OMG standard
— graphical notation
— process definition format
— execution semantics
– extensible
– interoperability
Generic process engine
– persistence
– transactions
– times
– expression dialects
– multi-threading
– events
– commands + interceptors
– session management
Future :
jBPM roadmap
– currently under community review
– more details soon
– 5.0 focus now on core components, should be ready by the end of the year
– regular (2-3 month) releases after that
Adaptive processes
– ability to handle change, complexity, …
How
– Externalise logic as rules
Leave a Reply