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.
Difference between revisions of "Java Workflow Tooling Project"
(→JWT Installation and Usage Documentation) |
(→Get and use Java Workflow Tooling!) |
||
| (35 intermediate revisions by 5 users not shown) | |||
| Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
| + | [http://www.eclipse.org/jwt/ JWT Website] | ||
| + | |||
JWT aims to provide both '''build-time and runtime generic tools for workflow engines'''. It is composed of several tools: the '''WE (Workflow Editor)''' to model the workflows and '''WAM (Workflow engine Administration and Monitoring tool)''' for monitoring and deployment. JWT also aims to provide generic APIs for defining and administrating business processes, in order to achieve said genericity. Addtionally, we will provide the user with several '''transformations''': a user can start modeling his/her processes in BPMN, transform those to JWT, enrich them with technical details and then deploy them on a process engine. Therefore, we develop transformations from BPMN to JWT, from JWT to BPMN, from JWT to XPDL, from JWT to STP-IM, etc. | JWT aims to provide both '''build-time and runtime generic tools for workflow engines'''. It is composed of several tools: the '''WE (Workflow Editor)''' to model the workflows and '''WAM (Workflow engine Administration and Monitoring tool)''' for monitoring and deployment. JWT also aims to provide generic APIs for defining and administrating business processes, in order to achieve said genericity. Addtionally, we will provide the user with several '''transformations''': a user can start modeling his/her processes in BPMN, transform those to JWT, enrich them with technical details and then deploy them on a process engine. Therefore, we develop transformations from BPMN to JWT, from JWT to BPMN, from JWT to XPDL, from JWT to STP-IM, etc. | ||
| + | == Get and use Java Workflow Tooling! == | ||
| + | * [[JWT_Downloads|Download and install JWT]] | ||
| + | * [[JWT_Tutorial|Tutorial on how to use and extend JWT]] | ||
| + | * [[JWT_SVN| Download the current source code of JWT]] and try the latest features | ||
| + | == JWT Community == | ||
| + | * [[JWT Resources]] - Mailing list, newsgroup, original proposal and other sites | ||
| + | * [[JWT Press]] - Public Presentations, conferences, press articles, blogs, forums | ||
| + | * [[JWT Downloads#Install other products based on JWT|JWT Integrations]] - Solutions that integrate and extend JWT | ||
| − | + | == JWT Developer Documentation == | |
| − | + | ||
| − | == JWT | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* [[JWT_Extensions|Extending JWT]] - How to extend JWT through Plugins and available extension points. To go further : | * [[JWT_Extensions|Extending JWT]] - How to extend JWT through Plugins and available extension points. To go further : | ||
| − | * [ | + | * [[JWT Architecture | Overview of JWT architecture]] |
* [[JWT Metamodel]]- JWT model core design, extensions and governance | * [[JWT Metamodel]]- JWT model core design, extensions and governance | ||
| − | * [ | + | * [[JWT WE architecture]] - Documentation about an old version and integration of JWT named AgilPro |
* [http://wiki.eclipse.org/images/8/8e/JWT_WAM_and_AgilPro_IFW.pdf JWT WAM architecture] Alignment of JWT WAM and AgilPro IFW/AFW | * [http://wiki.eclipse.org/images/8/8e/JWT_WAM_and_AgilPro_IFW.pdf JWT WAM architecture] Alignment of JWT WAM and AgilPro IFW/AFW | ||
* [[JWT Transformations]] - Compatibility tools with other standards and languages | * [[JWT Transformations]] - Compatibility tools with other standards and languages | ||
| − | * [[JWT Monitoring]] - Monitoring of Workflow Engines in JWT | + | * [[JWT Workflow Engine API and Monitoring]] - [[JWT Workflow Engine API]] and [[JWT Monitoring | Monitoring of Workflow Engines]] |
| + | * [[JWT Runtime]] - JWT Workflow Engine SPI and Runtime tools in JWT | ||
== JWT Contributor Documentation == | == JWT Contributor Documentation == | ||
* [[JWT_DeveloperFAQ|JWT DeveloperFAQ]] - General information about many recurring development and release tasks. Also : | * [[JWT_DeveloperFAQ|JWT DeveloperFAQ]] - General information about many recurring development and release tasks. Also : | ||
| − | * [[JWT_Modifications | JWT Modification Guidelines]] - | + | * [[JWT_Modifications | JWT Modification Guidelines]] - JWT development guidelines (such as API, string externalization) |
* [[JWT Ramp-Down-Policy]] - all necessary informations to integrate JWT into Eclipse Releases | * [[JWT Ramp-Down-Policy]] - all necessary informations to integrate JWT into Eclipse Releases | ||
* [[JWT Automatic Build]] - how build is automated (releng) | * [[JWT Automatic Build]] - how build is automated (releng) | ||
| − | + | Other Development Resources : | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
* [[JWT Meetings | Telcos and Meetings of JWT]] | * [[JWT Meetings | Telcos and Meetings of JWT]] | ||
* [[JWT Brainstorming | Brainstorming]] | * [[JWT Brainstorming | Brainstorming]] | ||
| − | + | * [[JWT Release Engineering | Release Engineering]] somewhat obsolete, rather see [[JWT Ramp-Down-Policy]] and [http://www.eclipse.org/projects/project-plan.php?projectid=soa.jwt project plan]. | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | * [[JWT Ramp-Down-Policy]] | + | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
[[Category:Eclipse Technology Project]] | [[Category:Eclipse Technology Project]] | ||
Latest revision as of 09:02, 23 May 2013
Contents
Overview
JWT aims to provide both build-time and runtime generic tools for workflow engines. It is composed of several tools: the WE (Workflow Editor) to model the workflows and WAM (Workflow engine Administration and Monitoring tool) for monitoring and deployment. JWT also aims to provide generic APIs for defining and administrating business processes, in order to achieve said genericity. Addtionally, we will provide the user with several transformations: a user can start modeling his/her processes in BPMN, transform those to JWT, enrich them with technical details and then deploy them on a process engine. Therefore, we develop transformations from BPMN to JWT, from JWT to BPMN, from JWT to XPDL, from JWT to STP-IM, etc.
Get and use Java Workflow Tooling!
- Download and install JWT
- Tutorial on how to use and extend JWT
- Download the current source code of JWT and try the latest features
JWT Community
- JWT Resources - Mailing list, newsgroup, original proposal and other sites
- JWT Press - Public Presentations, conferences, press articles, blogs, forums
- JWT Integrations - Solutions that integrate and extend JWT
JWT Developer Documentation
- Extending JWT - How to extend JWT through Plugins and available extension points. To go further :
- Overview of JWT architecture
- JWT Metamodel- JWT model core design, extensions and governance
- JWT WE architecture - Documentation about an old version and integration of JWT named AgilPro
- JWT WAM architecture Alignment of JWT WAM and AgilPro IFW/AFW
- JWT Transformations - Compatibility tools with other standards and languages
- JWT Workflow Engine API and Monitoring - JWT Workflow Engine API and Monitoring of Workflow Engines
- JWT Runtime - JWT Workflow Engine SPI and Runtime tools in JWT
JWT Contributor Documentation
- JWT DeveloperFAQ - General information about many recurring development and release tasks. Also :
- JWT Modification Guidelines - JWT development guidelines (such as API, string externalization)
- JWT Ramp-Down-Policy - all necessary informations to integrate JWT into Eclipse Releases
- JWT Automatic Build - how build is automated (releng)
Other Development Resources :
- Telcos and Meetings of JWT
- Brainstorming
- Release Engineering somewhat obsolete, rather see JWT Ramp-Down-Policy and project plan.