Jump to: navigation, search

Difference between revisions of "JWT FAQ"

m (The Goal of JWT)
m (The Components of JWT)
Line 14: Line 14:
 
* [http://www.eclipse.org/jwt/components/we/index.php WE (Workflow Editor)] will be a visual tool for creating, managing and reviewing process definitions. Straightforward and simple, WE will let users quickly create workflow process definitions, check and store them for further use. Once a process definition is proved valid, it can be imported/referenced into new ones, thus shortening the time and effort needed to define the workflow process. WE provides several views: for business managers to change the control flow of a process, for technical experts to invoke services, or others.
 
* [http://www.eclipse.org/jwt/components/we/index.php WE (Workflow Editor)] will be a visual tool for creating, managing and reviewing process definitions. Straightforward and simple, WE will let users quickly create workflow process definitions, check and store them for further use. Once a process definition is proved valid, it can be imported/referenced into new ones, thus shortening the time and effort needed to define the workflow process. WE provides several views: for business managers to change the control flow of a process, for technical experts to invoke services, or others.
 
* [http://www.eclipse.org/jwt/components/desktop/index.php Desktop tools] are useful to preview your processes without using any process engine or to simulate a number of processes.
 
* [http://www.eclipse.org/jwt/components/desktop/index.php Desktop tools] are useful to preview your processes without using any process engine or to simulate a number of processes.
* Building on a [http://www.eclipse.org/jwt/components/transformations/index.php transformation] base plugin it is possible to transform the JWT-model into BPMN and to generate XPDL-code. We are also working on other transformations, such as from BPMN to JWT, from JWT to STP-IM, etc.  
+
* [http://www.eclipse.org/jwt/components/transformations/index.php Transformation]: Building on a transformation base plugin it is possible to transform the JWT-model into BPMN and to generate XPDL-code. We are also working on other transformations, such as from BPMN to JWT, from JWT to STP-IM, etc.  
 
* [http://www.eclipse.org/jwt/components/wam/index.php WAM (Workflow engine Administration and Monitoring tool)] will be used to deploy and test a workflow in a workflow engine so to handle an engine's process definition external repository, to load some process definitions into a specific Workflow Engine, unload it, update it, instantiate it, monitor the Workflow Engines processes, perform mappings among participant definitions and real users, and among application definitions and tool agents.
 
* [http://www.eclipse.org/jwt/components/wam/index.php WAM (Workflow engine Administration and Monitoring tool)] will be used to deploy and test a workflow in a workflow engine so to handle an engine's process definition external repository, to load some process definitions into a specific Workflow Engine, unload it, update it, instantiate it, monitor the Workflow Engines processes, perform mappings among participant definitions and real users, and among application definitions and tool agents.
  

Revision as of 15:03, 30 July 2008

Frequently Asked Questions about JWT.

About JWT

The Goal of JWT

The goal of the JWT project is to develop a set of tools that help to develop, deploy and test workflows. JWT is not just another modeling tool and workflow engine, but provides an adaptable framework for different graphical representations and XML notations, as well as different workflow engines. The JWT project aims to provide both build-time and runtime generic tools for workflow engines. It will initially be composed of two tools, WE (Workflow Editor) and WAM (Workflow engine Administration and Monitoring tool). JWT also aims to provide generic APIs for defining and administrating business processes, in order to achieve said genericity.

More information on the Java Workflow Tooling project

The Components of JWT

  • WE (Workflow Editor) will be a visual tool for creating, managing and reviewing process definitions. Straightforward and simple, WE will let users quickly create workflow process definitions, check and store them for further use. Once a process definition is proved valid, it can be imported/referenced into new ones, thus shortening the time and effort needed to define the workflow process. WE provides several views: for business managers to change the control flow of a process, for technical experts to invoke services, or others.
  • Desktop tools are useful to preview your processes without using any process engine or to simulate a number of processes.
  • Transformation: Building on a transformation base plugin it is possible to transform the JWT-model into BPMN and to generate XPDL-code. We are also working on other transformations, such as from BPMN to JWT, from JWT to STP-IM, etc.
  • WAM (Workflow engine Administration and Monitoring tool) will be used to deploy and test a workflow in a workflow engine so to handle an engine's process definition external repository, to load some process definitions into a specific Workflow Engine, unload it, update it, instantiate it, monitor the Workflow Engines processes, perform mappings among participant definitions and real users, and among application definitions and tool agents.

Requirements

For the requirements needed in order to run components of JWT, please refer to Requirements.

Download and Installation

Binary Packages

The ready-to-use binary packages can be obtained from Downloads.

Source Code

CVS Information describes the layout of the JWT CVS Repository and gives information on how to download, install and run the most recent source code versions.

Source packages correponding to the official releases can be found on Downloads.


What is planned for the future

Upcoming Release Information describes the planned and current state of the next JWT release(s).


Contribute

Committers that want to contribute to JWT can find information concerning the development process of JWT components at Developer FAQ.

See also