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.
Frequently Asked Questions about JWT.
What is 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.
What does JWT consist in ?
- 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.
What are the requirements ?
For the requirements needed in order to run components of JWT, please refer to Requirements.
Where can I find some example workflows ?
JWT comes with some workflow sample files which can be found directly in Eclipse by clicking on
File -> New -> Examples -> Java Workflow Tooling.
There you will find currently two sample files (as of version 0.7.0) which show how a modeled process might look like. The integrators of JWT (e.g. AgilPro) also have their own sample files which are packaged and distributed and can be downloaded from their site. Please also have a look at the page of our integrators.
How can I install it ?
The ready-to-use binary packages can be obtained from Downloads.
Source packages correponding to the official releases can be found on Downloads.
What is planned next ?
Upcoming Release Information describes the planned and current state of the next JWT release(s) presenting planned/implemented features, bugfixes and changes.
How can I contribute ?
Committers that want to contribute to JWT can find information concerning the development process of JWT components at Developer FAQ.