Open Source Workflow Engines in Java
|jBpm is a flexible, extensible workflow management system. Business processes , expressed in a simple and powerfull language and packaged in process archives, serve as input for the jBpm runtime server. jBpm bridges the gap between managers and developers by giving them a common language : the jBpm Process definition language (jPdl).
Go To jBPM
|Shark is an extendable workflow engine framework including a standard implementation completely based on WfMC specifications using XPDL (without any proprietary extensions !) as its native workflow process definition format and the WfMC \"ToolAgents\" API for serverside execution of system activitie
Go To Enhydra Shark
|OSWorkflow can be considered a \"low level\" workflow implementation. Situations like \"loops\" and \"conditions\" that might be represented by a graphical icon in other workflow systems must be \"coded\" in OSWorkflow.
Go To OpenSymphony OSWorkflow
|con:cern is a workflow engine based on an extended case handling approach. A process is described as a set of activities with pre- and postconditions. An activity is executed when its preconditions are met. It manipulates the process item, thereby creating postconditions. The process flow is determined at run-time.
Go To con:cern
|Werkflow is a flexible, extensible process- and state-based workflow engine. It aims to satisfy a myriad of possible workflow scenarios, from enterprise-scale business processes to small-scale user-interaction processes. Using a pluggable and layered architecture, workflows with varying semantics can easily be accomodated. Processes can revolve around documents, objects or any other entity. The core werkflow engine can be accessed through a Java API, EJB, JMS, SOAP and other conduits.
Go To Werkflow
|Bonita is a flexible cooperative workflow system, compliant to WfMC specifications, based on the workflow model proposed by the ECOO Team, which incorporates the anticipation of activities as a more flexible mechanism of workflow execution. Bonita is Open Source and is downloadable in LGPL License.
Go To ObjectWeb Bonita
|Bossa is a workflow engine written in Java. The engine is very fast and lightweight, uses a very expressive Petri net notation to define workflows, does not require a RDBMS and is very simple to use and to integrate with java applications.
Go To Bossa
|The Open Business Engine is an open source workflow engine written in Java. OBE workflow definitions are written in XPDL, the WfMC's XML process definition language and are typically executed inside of a J2EE container.
Go To Open Business Engine
|The Open for Business Workflow Engine is based on the WfMC and OMG spec; (See the related documents for information on these specs.) it is a member of the Services Framework, and is tightly integrated with the Entity Engine. It uses the entities found in entitymodel_workflow.XML for definition information and entitymode_workeffort for runtime storage. All changes to a process or activity are persisted real-time. Therefore, the engine does not run in a thread, it is simply a group of APIs and common objects which handle the flow. When a change to the workflow is made, the engine then processes that change. When finished, the engine returns. Hence, if the application does crash, or the system reboots, the workflow will continue right where it left off upon restart.
Go To The Open for Business Workflow Engine
|OpenWFE is an open source java workflow engine. It is a complete Business Process Management suite, with 4 components : an engine, a worklist, a webclient and a reactor (host for automatic agents). A python access library is available : your python application / client can interact with an OpenWFE REST worklist.
Go To OpenWFE
|WfMOpen is a J2EE based implementation of a workflow facility workflow engine) as proposed by the Workflow Management Coalition (WfMC) and the Object Management Group (OMG).
Go To WfMOpen
|XFlow is a pure J2EE platform for building, executing and managing business processes and workflows. It is a basis for building collaborative applications as well as integrating processes across an enterprise. XFlow has a small footprint but is extremely powerful. It is designed to be easy to use from the development, deployment and management standpoints.
Go To XFlow
|JFolder (formerly PowerFolder) is workflow server and development studio. It can be configured to work on J2EE application servers and a variety of persistance stores (databases).
Go To JFolder
|The Taverna project aims to provide a language and software tools to facilitate easy use of workflow and distributed compute technology within the eScience community. As a component of the EPSRC funded myGrid project, Taverna is available freely under the terms of the LGPL.
Go To Taverna
|Freefluo is a workflow orchestration tool for web services initially developed by IT Innovation but now available to all from the Freefluo Sourceforge Site. It can handle WSDL based web service invocation. It supports two XML workflow languages, one based on IBM's WSFL and another named XScufl that is under development as part of the Taverna Sourceforge project.
Go To Freefluo
|The micro-workflow framework targets developers who want to separate the control and logic aspects in their programs, thus making them flow independent. A well-factored flow independent application facilitates change because the most frequent business changes translate into process changes, thus leaving the code intact.
Go To Micro-Flow
|JFlower is a very light workflow handler. You can write complex flow, with conditions and other flow invocations, and JFlower evaluate each step of the flow to the end of the flow.
Go To JFlower
|YAWL (Yet Another Workflow Language), an open source workflow language/management system, is based on a rigorous analysis of existing workflow management systems and workflow languages. Unlike traditional systems it provides direct support for all of the workflow patterns (http://www.workflowpatterns.com). YAWL supports the control-flow perspective, the data perspective, and is able to interact with web services declared in WSDL. It is based on a distributed, web-friendly infrastructure.
Go To YAWL
|An adaptive workflow engine based on simple concepts. It offers full persistence, so that work is never lost, and deals with partial failure in a distributed setup. Syrup is also used reliably as a distributed scheduler to replace cron.
Go To Syrup
|PXE (short for Process eXecution Engine and pronounced like \"pixie\") is a runtime component for executing processes defined by the BPEL4WS 1.1 specification.
Go To PXE
|ActiveBPEL engine is a robust runtime environment that is capable of executing process definitions created to the Business Process Execution Language for Web Services (BPEL4WS, or just BPEL) 1.1 specifications.
Go To ActiveBPEL
|Zebra is a workflow engine - originally developed to fill in the gaps in some commercial and open source workflow engines. The key differences between it and other workflow systems are able to model all the workflows described in workflow patterns, a GUI designer and Hibernate persistence layer.
Go To Zebra
|A simple business process management (BPM) product that can be easily embedded in other applications and run on a range of devices, including handheld computers.
Go To Apache Agila
|AntFlow is a tool for the automation and scheduiling of data system tasks, including those with complex dependencies and workflow logic. Antflow represents a new approach to simplifying system automation that leverages pipelines of hot folders chained together to perform a given task. Using XML, Antflow associates an automated task, such as data transfer, compression, or encryption, with a directory on the local system. Whenever a file is copied or written into the hot folder, the associated task is executed and the file is moved to the next hot folder in the pipeline for further processing.
Go To Antflow
|Bexee is a BPEL engine capable of executing deployed business processes described in BPEL by orchestrating existing Web Services.
Go To Beexee
|The heart of the engine is an ability to capture the execution state of a thread and resume it later. Many applications of today need to have a part of the program that waits for other entities. . Often there are multiple conversations running concurrently. Those are what we call \"workflow\" applications. Today, those applications can be written, but one can't write it very productively. Dalma makes it very easy to write those workflow applications by letting you write it as an ordinary procedural program without any boilerplate.
Go To Dalma
|Swish is an open source web services-based workflow API/Engine. The name Swish is an acronym derived from the phrase Simple Web services Interface to Shark.
Swish provides a convenient web services layer on top of Enhydra Shark, offering two key benefits:
1. It opens Shark to a wider range of developers by supporting both Java and non-Java clients. Java clients are supported natively and can use Swish in 'embedded' mode in addition to the web services alternative.
2. It greatly simplifies access to the more commonly-used features of Shark.
Go To Swish
|BpmScript is a continuation based scripting platform for Business Process Management.
* Clustered processes
* Worklist Support
* ServiceMix JBI integration
* Web Management Console
* Versioned Processes
* Child Processes
* Remote API
* Half Async Processes
* Parallel Processes
Go To BpmScript
|RUNA WFE is an open source workflow/BPM environment based on JBoss JEMS stack engine.
It's main features are:
-rich web interface containing work list handler, process monitor and form player
- graphical process designer
- bots for automated business process steps
- powerful role based task assignment
- security system with LDAP/MS Active Directory, NTLM, SSO support
- easy integration with all SQL database management systems
- localization to English, French, German, Dutch, Spanish,Italian,Chinese and Russian
- platform independent pure Java solution
Go To RUNA WFE
|JawFlow is a Workflow Engine partially conformal to WfMC (www.wfmc.org) directives, completely written in Java using JMX technology. It understands XML Process Definition Language (XPDL) and can be customized using activities written in Java or in any scripting language supported by BSF
Go To jawflow
|Pegasus (Planning for Execution in Grids) is a workflow mapping engine that automatically maps high-level workflow descriptions onto distributed resources. It takes a description of computational tasks to be performed and adds the necessary data transfers and data registration tasks (optionally). Pegasus uses the Condor DAGMan execution engine to execute on Condor pools, and clusters managed by PBS and LSF. Pegasus can optimize the workflow performance and reliability.
Go To Pegasus
|Wilos is an orchestration process software. It allows users to manage a project driven by a process engineering taking from an exported xml file from Eclipse Process Framework Composer. The process is based on the Software Process Engineering MetaModel (SPEM2) specification of the OMG standard.
Go To Wilos
|The Imixs Open Source Project was created to promote the development of workflow technologies based on open software standards. Within the scope of this project, various technologies and procedures are published that allow and support the development of open, process-oriented workflow systems.
The project comprises the development of a framework to create workflow systems as well as a reference implementation based on the JEE standard. Additionally, the project includes the development of a graphic editor for creation and management of WorkflowModels within the Eclipse framework and also client frameworks to be build in user interfaces.
Go To Imixs IX Workflow
|Activiti is a light-weight workflow and Business Process Management (BPM) Platform targeted at business people, developers and system admins. Its core is a super-fast and rock-solid BPMN 2 process engine for Java. It integrates perfectly with Spring, it is extremely lightweight and based on simple concepts.
Go To Activiti
|Apache ODE (Orchestration Director Engine) executes business processes written following the WS-BPEL standard. It talks to web services, sending and receiving messages, handling data manipulation and error recovery as described by your process definition. It supports both long and short living process executions to orchestrate all the services that are part of your application.
Go To Apache ODE
|Bonita Open Solution is an intuitive and powerful open source Workflow and BPM suite: just draw your processes using a BPMN palette, then connect to your existing systems (Oracle, MySQL, LDAP, Google, Twitter, Facebook...) and run your Java Workflow application in a single click
Go To Bonita Open Solution
Go To Joget Workflow
|BPM platform built in Java and integrated to the Eclipse platform. Designed to be simple, versatile and focused on the developer.
It includes a Petri Nets graphical process designer integrated to Eclipse and a query language similar to OQL.
* kbee Workflow Server
* kbee Process Designer: Graphic design of procedures using Petri Nets.
* kbee OLAP Server: for OLAP cubes in the processes
* kbee.WQL (Workflow Query Language): OQL like query language on the workflow engine
Go To kbee.workflow
|Sarasvati is a capable, embeddable workflow/BPM engine for Java. For developers, it focuses on expressive modeling and ease of use features like embeddable sub-processes and backtracking. For users, it offers transparency via visualizations and human readable guards.
Go To Sarasvati
|TobFlow (Total Object Base and Flow or the Object Flow) is an internet application platform to manage forms and workflows. It is made of an engine which manages the user interface (forms) and the scheduling of tasks (workflows) based on object model descriptions.
The rationale of TobFlow is to propose a true document workflow tool, which, right from the design phase, combines the document approach (forms to fill in) and the process approach (sequence of tasks to fulfill a business objective). The solution is based on the notion of objects (i.e. information sets) that are defined both by the way they are presented to users (forms and views) and by their life sequence (workflow process).
Go To Tobflow