Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "JWT EclipseCon 2009"

(Conference details)
(Submitted Presentation)
Line 8: Line 8:
 
== Submitted Presentation ==
 
== Submitted Presentation ==
  
Title: Make Your Process Executable!
+
Title: Make Your Processes Executable!
  
Abstract: Business Process Management has gained a lot of attention during the last years. There is now a huge amount of commercial and open-source-software tools available that allow to model, deploy, execute and monitor a workflow. However, most of the current open-source-workflow tools are still incompatible. In the Eclipse-project Java Workflow Tooling (JWT) we build a set of tools that enable users to model a workflow independently of the workflow engine first and add engine-specific details based on plugin extensions lateron. The workflow builds the basis for generating XPDL or BPEL-code in the next step which can then be deployed and executed on a workflow engine such as Bonita. We will also show the possibility to monitor the workflow on the workflow engine as well as our integration with the Eclipse STP project (e.g. by generating code for the STP-Intermediate Model) and within Service Oriented Architectures more generally.
+
Abstract:  
 +
 
 +
Business managers model their processes often in an abstract version. They are not concerned about how those will be executed later on (and they shouldn't be!). The actual execution information can be added by the technical staff afterwards. But what happens if the modeled process shall be deployed on different process engines? Each vendor requires different data which should be added to the process model. In the Eclipse project Java Workflow Tooling (JWT) we support the modeler with different views and aspects that allow the easy customization of a process also considering existing runtime data.
 +
 
 +
The process model also builds the basis for generating XPDL- or WSBPEL-code. We will also show the possibility to monitor the process on the engine as well as we'll demonstrate our integration with the Eclipse STP project (e.g. by generating code for the STP-Intermediate Model) and within Service Oriented Architectures more generally.
  
 
Type: Show me (Short talk up to 30 minutes)
 
Type: Show me (Short talk up to 30 minutes)

Revision as of 09:09, 5 November 2008

Conference details

March 23rd till 26th Santa Clara, California

Deadline for submission: November 24th, see Submission Guidelines

Submitted Presentation

Title: Make Your Processes Executable!

Abstract:

Business managers model their processes often in an abstract version. They are not concerned about how those will be executed later on (and they shouldn't be!). The actual execution information can be added by the technical staff afterwards. But what happens if the modeled process shall be deployed on different process engines? Each vendor requires different data which should be added to the process model. In the Eclipse project Java Workflow Tooling (JWT) we support the modeler with different views and aspects that allow the easy customization of a process also considering existing runtime data.

The process model also builds the basis for generating XPDL- or WSBPEL-code. We will also show the possibility to monitor the process on the engine as well as we'll demonstrate our integration with the Eclipse STP project (e.g. by generating code for the STP-Intermediate Model) and within Service Oriented Architectures more generally.

Type: Show me (Short talk up to 30 minutes)

Category: Eclipse Ecosystem - Emerging Technology (see Categories)

Difficulty: Easiest, Intermediate, Difficult or Expert (I'd say Intermediate)

Authors: Florian Lautenbacher and Christian Saad (the persons who will show it in Santa Clara if the talk is accepted)

Back to the top