1 / 9

Java Workflow Tooling (JWT)

Java Workflow Tooling (JWT). Florian Lautenbacher University of Augsburg Germany - JWT project lead – Eclipse Summit Europe 2007. Possible outline – to be discussed. JWT Introduction JWT place in the Business process development life cycle

marcy
Télécharger la présentation

Java Workflow Tooling (JWT)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Java Workflow Tooling (JWT) Florian Lautenbacher University of Augsburg Germany - JWT project lead – Eclipse Summit Europe 2007

  2. Possible outline – to be discussed • JWT Introduction • JWT place in the Business process development life cycle • How JWT improves the development, creation, maintenance and interoperability of the process definitions • Possible JWT Integrations with SOA platforms etc. • JWT vision for the future.

  3. JWT purpose • Provide build time and run-time tools to help develop processes • Typical use cases will be : • Graphically design a process • Start/Stop a process/workflow engine • Deploy a process definition in an engine • Administrate/monitor engine in order to debug a deployed process • No particular focus on a specific engine implementation or standard (even if standards will be promoted) : need for an independent process meta model definition • No constrained graphic representation but BPMN will be targeted at first. Motivations are to be able to give to different user profiles different representation of the same workflow definition. E.g. : simplified view for business oriented users.

  4. JWT description • JWT is divided in two related parts : • Workflow Editor (WE) • Graphical representation of process definition • Export of process definitions to XML • Import of valid XML process definition and its graphical representation • Workflow engine Administration and Monitoring (WAM) • Process Definition Management (Repository & Package) • Process Execution Management (Instantiation, Monitoring…) • Process Runtime Resources Mapping (Application & Users) • Worklist Management & out of the box “Desktop BPM” features

  5. PSM CIM JWT WE – underlying principle MDSD/MDATM MDSD light Business Expert Domain expert business view Architecture etc. simulation, preview MT domain specific model technical view IT Expert PIM IT-Expert PM MT XML code forprocess engine IT System Code Code

  6. JWT WE – Screenshot (JWT WE packaged as an RCP application, available on www.agilpro.eu)

  7. JWT WE – extension points • possibility to generate code from the workflow models (WSBPEL, XPDL, etc.) e.g. using the workflow generation framework at http://sf.net/projects/workflowgenerationframework • generate a documentation of the modelled processes • create additional views (BPMN, ITIL, ISO 9000, etc.) • ...

  8. JWT WAM

  9. JWT – To be filled • ToDo‘s in SCOrWare, by Obeo, INT Evry, OpenWide? • Timeline for releases? • When will the first release of JWT WAM be online? • JWT WE will be released on the Eclipse site in the first week of October • Short video using the simulator (Preview desktop)? • To be discussed on the mailing list • 30 minutes time, means a maximum of 17 slides

More Related