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.
Java Workflow Tooling brings open business process (modeling|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 for 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 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.
For Galileo, the focus has been to add compatibility with common business process runtimes like Bonita, and to integrate service-oriented features in collaboration with projects of the SOA Tools Platform (STP), especially BPMN, SCA and IM.
- "Later on, we plan to improve runtime tooling, including deployment, monitoring, but also simulation and jBoss jPDL support."
- "standards compatibility and interoperabiltity"
More on JWT v0.6.0
Please see the New & Noteworthy section of JWT.