Skip to main content
Jump to: navigation, search

Difference between revisions of "JWT Galileo Summary"

(Paragraph on developerWorks article)
(Paragraph on developerWorks article)
Line 6: Line 6:
 
=== Paragraph on developerWorks article ===
 
=== Paragraph on developerWorks article ===
  
There is never a single or perfect kind of workflow / process model. Everybody sees a workflow with different eyes: the business analyst more abstract with only the names of the actions and the IT developer quite concrete with 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 and to refine them, import them from other representations and export them afterwards in order to execute them on existing process and workflow engines.  
+
When modeling business processes, there is never a single or perfect kind of workflow / process model. Everybody sees a workflow with different eyes: the business analyst more abstract with only the names of the actions and the IT developer quite concrete with 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 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.
 
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 business process runtimes like Bonita and integrated service-oriented features in collaboration with the STP project. So now, there are transformations from and to the STP-BPMN-modeler as well as to the STP Intermediate Model (IM) which can be used to generate e.g. BPEL- or SCA-code. 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, e.g. Scarbo or AgilPro.
  
 
=== More on JWT v0.6.0 ===
 
=== More on JWT v0.6.0 ===
  
 
Please see the [http://wiki.eclipse.org/JWT_NewNoteworthy_0_6 New & Noteworthy] section of JWT.
 
Please see the [http://wiki.eclipse.org/JWT_NewNoteworthy_0_6 New & Noteworthy] section of JWT.

Revision as of 02:57, 16 June 2009

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, there is never a single or perfect kind of workflow / process model. Everybody sees a workflow with different eyes: the business analyst more abstract with only the names of the actions and the IT developer quite concrete with 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 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 business process runtimes like Bonita and integrated service-oriented features in collaboration with the STP project. So now, there are transformations from and to the STP-BPMN-modeler as well as to the STP Intermediate Model (IM) which can be used to generate e.g. BPEL- or SCA-code. 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, e.g. Scarbo or AgilPro.

More on JWT v0.6.0

Please see the New & Noteworthy section of JWT.

Back to the top