Imixs-Workflow
Imixs-Workflow
https://www.imixs.org
Imixs-Workflow is an Open Source Workflow Engine for Human-Centric BPM.
Imixs Workflow is an Open-Source-Project, providing technologies for building Business Process Management solutions. The project focus on human based workflows used to execute and control workflows in organisations and enterprises. In difference to task-oriented workflow engines, which focus on automated program flow control (tasks), Imixs Workflow is a representative of an event-based workflow engine. Here, the engine controls the status of a process instance within a defined state-diagram. By entering an event, the state of a process instance can be abandoned or changed. In human-centric workflow engines, events usually occur by an interaction of the actor with the system, for example by approving or rejecting a business transaction. They can also be triggered by scheduled events. An example of this is an escalation of an unfinished task.
Licensing
License
Verified by
Verified on
Notes
License
Leaders and contributors
| Contact(s) | Role |
|---|---|
| Ralph Soika (Rsoika) | project lead |
Resources and communication
Software prerequisites
Imixs Workflow is an Open-Source-Project, providing technologies for building Business Process Management solutions. The project focus on human based workflows used to execute and control workflows in organisations and enterprises. In difference to task-oriented workflow engines, which focus on automated program flow control (tasks), Imixs Workflow is a representative of an event-based workflow engine. Here, the engine controls the status of a process instance within a defined state-diagram. By entering an event, the state of a process instance can be abandoned or changed. In human-centric workflow engines, events usually occur by an interaction of the actor with the system, for example by approving or rejecting a business transaction. They can also be triggered by scheduled events. An example of this is an escalation of an unfinished task.
The goal of the open source project is to reduce the complexity of business applications by providing a flexible framework to implement business logic based on the BPMN 2.0 standard.
Technology
The project is based on the Java Enterprise Architecture (JEE) and represents a scalable and transactional framework for workflow management solutions. A major goal of the technology is to simplify the software build process in modern business applications. The project takes advantage of the JEE component model, and allows to reuse all components without limiting the capabilities of the Java EE architecture.
The technologies used includes:
- Enterprise JavaBeans – technology for a transactional business process management
- Java Persistence API vendor independent database access
- Java Authentication and Authorization Service for security
- BPMN 2.0 for modelling business workflows.<ref>See the BPMN modeling project page 3.</ref><ref>Eclipse BPMN2 Modeler Project 4.</ref>
The reference implementation is based on Wildfly. Glassfish and Payara application servers are supported. By Using the Java Persistence API (JPA), the workflo wengine is database independent and can be used with any relational SQL database.
Licence
Imixs-Workflow provides the results of the project under the GPL with a dual-license model, to meet the usage and distribution requirements of different types of users.
History
The Imxis workflow project was founded in 2005 by Imixs software solutions GmbH.
References
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the page “GNU Free Documentation License”.
The copyright and license notices on this page only apply to the text on this page. Any software or copyright-licenses or other similar notices described in this text has its own copyright notice and license, which can usually be found in the distribution or license text itself.