Java Workflow Tooling (JWT) Florian Lautenbacher University of Augsburg Germany - JWT project lead – Eclipse Summit Europe...
Outline <ul><li>Java Workflow Tooling (JWT): </li></ul><ul><li>JWTs place in the business process development life cycle  ...
JWT – A complete, flexible BPM platform <ul><li>To provide a comprehensive, flexible BPM platform </li></ul><ul><ul><li>Ad...
The BPM „Babel Tower“ issue <ul><li>Problems in BPM </li></ul><ul><ul><li>Many modeling languages (e.g. BPMN, EPCs, UML Ac...
The BPM „Babel Tower“ issue <ul><li>On the other side </li></ul><ul><ul><li>Many tools for many modeling languages and pro...
Addressing the BPM „Babel Tower“ issue <ul><li>Solution 1: an extensible metamodel </li></ul><ul><ul><li>JWT‘s core metamo...
Achieving a unified approach to BPM design <ul><li>First workflow editor available on the Eclipse web site </li></ul><ul><...
JWT for SOA - Benefits of SOA for BPM <ul><li>SOA acts as a „protective shell“ over the enterprise information system </li...
JWT for SOA – Targeting an SOA platform <ul><li>Again: still under development </li></ul><ul><ul><li>Scheduled for the end...
JWT consists of (at least) two related parts <ul><li>Workflow Editor (WE) </li></ul><ul><ul><li>Graphical representation o...
JWT WE – Underlying principle domain specific model XML code for process engine simulation, preview business view technica...
JWT WE – Screenshot <ul><li>(JWT WE packaged as an RCP application, available on  www.agilpro.eu ) </li></ul>
JWT WE – extension points <ul><li>Preview / Simulate the modeled processes </li></ul><ul><li>Possibility to generate code ...
Thanks for your attention!! <ul><li>The JWT project team:  </li></ul><ul><li>Marc Dutoo (Project Lead) - Open Wide, FR </l...
Upcoming SlideShare
Loading in …5
×

Eclipse Foundation, Inc. | © 2007 by OpenWide / University of ...

506 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
506
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Eclipse Foundation, Inc. | © 2007 by OpenWide / University of ...

  1. 1. Java Workflow Tooling (JWT) Florian Lautenbacher University of Augsburg Germany - JWT project lead – Eclipse Summit Europe 2007
  2. 2. Outline <ul><li>Java Workflow Tooling (JWT): </li></ul><ul><li>JWTs place in the business process development life cycle </li></ul><ul><li>Addressing the BPM „Babel Tower“ issue </li></ul><ul><li>Achieving a unified approach to BPM design </li></ul><ul><li>JWT for SOA – Targeting an SOA platform </li></ul><ul><li>JWTs general purpose, structure and APIs </li></ul><ul><li>Specific focus: JWT Workflow Editor (WE) </li></ul>
  3. 3. JWT – A complete, flexible BPM platform <ul><li>To provide a comprehensive, flexible BPM platform </li></ul><ul><ul><li>Addresses and (hopefully) solves the BPM „Babel Tower“ issue, that has plagued the BPM field for years </li></ul></ul><ul><ul><li>Allows for „Distribution“-like releases with specific extensions targeting specific platforms or problems (e.g.) JWT for SOA </li></ul></ul><ul><li>To provide a complete and usable BPM solution </li></ul><ul><ul><li>Business View, Technical View </li></ul></ul><ul><ul><li>Deployment View, Monitoring View </li></ul></ul><ul><ul><li>Tooling and integration with runtime </li></ul></ul><ul><li>JWT consists of </li></ul><ul><ul><li>Set of generic (Eclipse-based) plugins </li></ul></ul><ul><ul><li>Extensible APIs </li></ul></ul><ul><ul><li>Extensions allowing support for specific business representations, process language formats, process engines, service platforms… </li></ul></ul>
  4. 4. The BPM „Babel Tower“ issue <ul><li>Problems in BPM </li></ul><ul><ul><li>Many modeling languages (e.g. BPMN, EPCs, UML Activity diagrams) </li></ul></ul><ul><ul><li>Many process languages and technical formats (e.g. XPDL, WSBPEL and extensions) </li></ul></ul><ul><ul><li>Even more process engine implementations; each with different features </li></ul></ul><ul><ul><ul><li>e.g. open source process engines like jBoss jBPM, OW2 / Bull Bonita & Orchestra, Apache ODE, … </li></ul></ul></ul><ul><li>Origins of the BPM Babel Tower issue </li></ul><ul><ul><li>Vendors first and foremost develop and „sell“ process engines </li></ul></ul><ul><ul><li>Only then they start developing tools for their engines </li></ul></ul><ul><ul><li>And in order to showcase their engine‘s specific features, their tooling is usually bound to their engine (Engine specific implementation) </li></ul></ul>
  5. 5. The BPM „Babel Tower“ issue <ul><li>On the other side </li></ul><ul><ul><li>Many tools for many modeling languages and process engines, but most of them are not compatible </li></ul></ul><ul><li>What the user(s) would like </li></ul><ul><ul><li>Being able to use the best technology and the best tools for all of their needs </li></ul></ul><ul><ul><li>For instance </li></ul></ul><ul><ul><ul><li>BPMN used by a business analyst to design a first high, business-level process description using a full blown BPMN editor </li></ul></ul></ul><ul><ul><ul><li>Help the developer from there to an XPDL implementation </li></ul></ul></ul><ul><ul><ul><li>XPDL used for workflow needs, BPEL for orchestration, with minimal hindrance in the must-have knowledge about engine integration </li></ul></ul></ul>
  6. 6. Addressing the BPM „Babel Tower“ issue <ul><li>Solution 1: an extensible metamodel </li></ul><ul><ul><li>JWT‘s core metamodel is simple </li></ul></ul><ul><ul><li>Forms a good basis for such an extensible metamodel </li></ul></ul><ul><li>Solution 2: a pivotal metamodel </li></ul><ul><ul><li>A metamodel for which exists a bijective transformation with the JWT core metamodel is granted the full set of features that JWT provides </li></ul></ul><ul><ul><li>This solution allows a unified approach to BPM tooling and especially design, since any BP-related language can to some point be integrated this way </li></ul></ul><ul><li>Possible example: the STP-Intermediate Model (IM): </li></ul><ul><ul><li>Bridges different SOA platforms: </li></ul></ul><ul><ul><ul><li>Workflow / process: e.g. BPMN, BPEL </li></ul></ul></ul><ul><ul><ul><li>Architecture specification: e.g. SCA, JBI </li></ul></ul></ul><ul><ul><ul><li>Service Creation: e.g. JAX-WS </li></ul></ul></ul><ul><ul><li>Mapping between STP-IM and JWT considered </li></ul></ul><ul><li>Solution 3: the Process Virtual Machine (PVM) </li></ul><ul><ul><li>abstraction layer above existing process engines </li></ul></ul>
  7. 7. Achieving a unified approach to BPM design <ul><li>First workflow editor available on the Eclipse web site </li></ul><ul><ul><li>based on the open-source toolsuite AgilPro </li></ul></ul><ul><li>Unified approach still under development </li></ul><ul><ul><li>Scheduled for the end of the year </li></ul></ul><ul><ul><li>Two way BPMN to JWT transformation </li></ul></ul><ul><ul><li>JWT to XPDL transformation </li></ul></ul><ul><ul><li>JWT to BPEL transformation </li></ul></ul><ul><li>Planned work: </li></ul><ul><ul><li>Mapping with other metamodels (such as STP-IM) </li></ul></ul><ul><ul><li>PVM interoperability </li></ul></ul>
  8. 8. JWT for SOA - Benefits of SOA for BPM <ul><li>SOA acts as a „protective shell“ over the enterprise information system </li></ul><ul><ul><li>Ensuring business processes won‘t be impacted by unmanaged evolutions of the information system </li></ul></ul><ul><li>SOA platforms provide services that are natural candidates for JWTs process execution </li></ul><ul><ul><li>Therefore, integrating JWT with SOA platforms at development- and runtime definitely makes sense! </li></ul></ul><ul><li>Looking at BPM the SOA way </li></ul><ul><ul><li>BPM engines may be seen as exposing services </li></ul></ul><ul><ul><ul><li>BPM engine administration service, Process start service, Process Activity Lifecycle service… </li></ul></ul></ul><ul><ul><li>BPM tooling may be integrated to SOA platforms development, deployment or management tooling </li></ul></ul>
  9. 9. JWT for SOA – Targeting an SOA platform <ul><li>Again: still under development </li></ul><ul><ul><li>Scheduled for the end of the year </li></ul></ul><ul><li>Generic service registry API </li></ul><ul><ul><li>With a first simple implementation </li></ul></ul><ul><li>Generic service registry Browsing and Search UI </li></ul><ul><ul><li>Basic browsing UI </li></ul></ul><ul><ul><li>Advanced semantic search UI </li></ul></ul><ul><li>Integrated in the JWT workflow editor </li></ul><ul><ul><li>Allows to graphically create JWT actions targeting a service that is known by the registry </li></ul></ul><ul><li>Planned work : </li></ul><ul><ul><li>Process registry </li></ul></ul><ul><ul><li>SCA integration (within the public-funded project SCOrWare) </li></ul></ul>
  10. 10. JWT consists of (at least) two related parts <ul><li>Workflow Editor (WE) </li></ul><ul><ul><li>Graphical representation of process definition </li></ul></ul><ul><ul><li>Export of process definitions to XML (BPEL, XPDL, etc.) </li></ul></ul><ul><ul><li>Import of valid XML process definition and its graphical representation </li></ul></ul><ul><li>Workflow engine Administration and Monitoring (WAM) </li></ul><ul><ul><li>Integration with SOA, SCA, etc. </li></ul></ul><ul><ul><li>Process Definition Management (Repository & Package) </li></ul></ul><ul><ul><li>Process Execution Management (Instantiation, Monitoring, etc.) </li></ul></ul><ul><ul><li>Process Runtime Resources Mapping (Application & Users) </li></ul></ul><ul><ul><li>Worklist Management & out of the box “Desktop BPM” features </li></ul></ul>
  11. 11. JWT WE – Underlying principle domain specific model XML code for process engine simulation, preview business view technical view Domain expert IT-Expert MDSD light MDSD/MDA TM Business Expert IT Expert IT System Code PIM Code Architecture etc. PM MT MT CIM PSM
  12. 12. JWT WE – Screenshot <ul><li>(JWT WE packaged as an RCP application, available on www.agilpro.eu ) </li></ul>
  13. 13. JWT WE – extension points <ul><li>Preview / Simulate the modeled processes </li></ul><ul><li>Possibility to generate code from the workflow models </li></ul><ul><ul><li>WSBPEL </li></ul></ul><ul><ul><li>XPDL </li></ul></ul><ul><ul><li>e.g. using the workflow codegeneration framework at http://sf.net/projects/wf-codegen </li></ul></ul><ul><li>Generate a documentation of the modeled processes </li></ul><ul><ul><li>HTML documentation </li></ul></ul><ul><ul><li>PDF files </li></ul></ul><ul><li>Create additional views </li></ul><ul><ul><li>BPMN </li></ul></ul><ul><ul><li>ITIL </li></ul></ul><ul><ul><li>ISO 9000 </li></ul></ul><ul><li>... and many others possible! </li></ul>
  14. 14. Thanks for your attention!! <ul><li>The JWT project team: </li></ul><ul><li>Marc Dutoo (Project Lead) - Open Wide, FR </li></ul><ul><li>Florian Lautenbacher (Project Lead) – University of Augsburg, DE </li></ul><ul><li>Miguel Valdez (Technology Advisor) – Bull, FR </li></ul><ul><li>Alain Boulze (Market Advisor) – INRIA / OW2, FR </li></ul><ul><li>Fabrice Dewasmes (Vision Advisor) – Pragma Consult, LU </li></ul><ul><li>Günther Palfinger (Technical Advisor) – eMundo, DE </li></ul><ul><li>Koen Aers, Tom Baeyens – JBoss corp. </li></ul><ul><li>Pardeep Sood – Independent Consultant </li></ul><ul><li>and many others... </li></ul><ul><li>Other contributors are more than welcome!! </li></ul><ul><li>Are there any questions? </li></ul>

×