JWT Galileo Summary
JWT Galileo (version 0.6.0) Short Summary
This summary is also used for an article on IBM developerWorks about the new Galileo release. On this page we summarize the paragraph about JWT in this article.
Paragraph on developerWorks article
When modeling business processes, every actor see a workflow with different eyes: the business analyst staying at a more abstract level with only the names of the actions, and the IT developer being quite concrete with implementations details, like service interfaces and operations. Hence, the goal of the Java Workflow Tooling (JWT) project is to allow users not only to model processes in one view, but in different ones and to refine them, import them from other representations and export them afterwards in order to execute them on existing process or workflow engines.
Thereby, JWT offers users an adaptable and extensible set of tools in Eclipse for code generation (e.g. XPDL- or WSBPEL-code, but also HTML documentation), deployment, execution and monitoring of business processes. Fitted with a flexible mechanism that allows to customize the underlying EMF core model and with support for all kind of views, vendors can build tools on top of JWT suited for their domain thus supporting specific business representations, process language formats, process engines, service platforms, etc.
For Galileo, the JWT-team focused on adding compatibility with common business process runtimes like Bonita and to integrated service-oriented (SOA) features in collaboration with projects of the SOA Tools Platform (STP), especially BPMN, SCA and IM. There are several views on a workflow model available, e.g. as UML activity diagram or event-driven process chain. There are already first tools that integrate JWT, too, such as Scarbo of the OW2 consortium, or AgilPro in SourceForge which brings WSBPEL-codegeneration.
Same in French
Le projet Eclipse Java Workflow Tooling (JWT) outille le développement de processus métier. La gestion des processus métier (Business Process Management, BPM) est au carrefour du métier, de l'infrastructure et de l'intégration, c'est pourquoi il ne devrait vraiment pas verrouiller les options de ses utilisateurs. C'est pourquoi les processus modélisés par JWT peuvent avoir la représentation que souhaite l'analyse, porter toute information d'implémentation que le développeur ajoute, et être déployé sur la plateforme d'exécution choisie.
Cela est rendu possible par un "framework" flexible autorisant des vues, modèles et transformations personnalisés, sur lequel communautés et éditeurs peuvent bâtir. JWT est livré avec plusieurs extensions comprenant les vues UML Activity Diagram ou Event-driven Process Chains (EPC), l'interopérabilité avec le standard BPMN, et la génération de code (par exemple des processus exécutables en XPDL, ou en WSBPEL avec l'intégration AgilPro, mais aussi de la documentation HTML). Il y a en fait déjà quelques solutions qui intègrent JWT, comme Scarbo hébergé par le consortium OW2 et se focalisant sur SOA, ou AgilPro sur SourceForge.
Pour Galileo, l'accent a été mis sur rendre compatible avec les moteurs de workflow usuels comme Bonita, et d'intégrer des fonctionnalités orientées service en collaboration avec les sous-projets de Eclipse SOA Tools Platform (STP), notamment BPMN, SCA et IM.
Ian Skerrett blog
1. What does your project do? Java Workflow Tooling brings open business process design and development to the Eclipse platform. Business Process Management (BPM) is at the crossroads of business, middleware and integration, so it really shouldn't lock up the options of its actors. That's why JWT-modeled processes can look the way the analyst wants, hold any implementation information the developer adds in, and be deployed to the runtime platform of choice.
This is possible thanks to a flexible framework allowing extensible views, model and transformations, that communities and vendors can build on. JWT comes with several built-in extensions like UML Activity Diagram or Event-driven Process Chains (EPC) views, BPMN interoperability, code generation (e.g. XPDL, or WSBPEL-code in the AgilPro integration, but also HTML documentation). There are actually already a few solutions that integrate JWT, such as the SOA-focused Scarbo of the OW2 consortium, or AgilPro in SourceForge.
2. Who are your typical users? Business process analysts and developers in need of a truly open workflow platform, but also vendors and academics interested by the extensibility of its framework. And anyone who already has a task-oriented, workflow-like engine but is missing an editor, and is willing to write an export transformation in order to get one.
3. Why did you join the Galileo release train? After completing your first release train, what do you think now? Being in the Galileo release train witnesses that JWT is a mature project that can be used and build on. It was not easy to fulfill all requirements for Galileo, but the attention it brings to JWT alone is worth it ! On the other side we believe that JWT provides features that are a valuable addition to Galileo. And looking back, getting into the release train was a unique opportunity to improve the general quality of the project and enhance its reactivity and agility, one step closer to graduation.
4. What future enhancements are you planning for your project? In the next release we plan to improve runtime tooling, including process simulation within Eclipse, deployment, monitoring as well as support for JBoss jBPM, but also switch to a more powerful views mechanism supporting different layouts.