Workflow Engines « J2EE Web Development « Java Products

Home
Java Products
1.Application
2.Business
3.Byte Source Code
4.Component
5.Data File
6.Database
7.Development
8.Graph Image Diagram Movie
9.GUI Tools
10.J2EE Web Development
11.Misc
12.Net Web Mobile
13.Programming
14.Science
15.Server Side JSP Servlet
16.Swing
17.Testing
18.Utilities
19.XML
Java
Java Tutorial
Java Book
Java Source Code / Java Documentation
Java Source Code / Java Documentation 2
Java Open Source
Jar File Download
Java Articles
Java by API
SCJP
Spring questions and answers
Swing questions and answers
JPA questions and answers
Java Products » J2EE Web Development » Workflow Engines 
1. JBoss jBPM
By:
License:Apache Software License
URL:http://www.jbpm.org/
Description:JBoss jBPM enables the creation of business processes that coordinate between people, applications and services. Designed for the mass market as well as supporting enterprise scale applications, jBPM bring process automation to a much wider set of business problems ranging from embedded workflow to enterprise business process orchestration and BPM.


2. Enhydra Shark
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://shark.objectweb.org/
Description:The Enhydra Shark project delivers a workflow server with a difference. It is an extendable and embeddable Java Open Source 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 activities.


3. OSWorkflow
By:
License:Apache Software License
URL:http://www.opensymphony.com/osworkflow/
Description:OSWorkflow is fairly different from most other workflow systems available, both commercially and in the open source world. What makes OSWorkflow different is that it is extremely flexible. This can be hard to grasp at first, however. For example, OSWorkflow does not mandate a graphical tool for developing workflows, and the recommended approach is to write the xml workflow descriptors 'by hand'. It is up to the application developer to provide this sort of integration, as well as any integration with existing code and databases. These may seem like problems to someone who is looking for a quick "plug-and-play" workflow solution, but we've found that such a solution never provides enough flexibility to properly fulfill all requirements in a full-blown application.


4. con:cern
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://concern.sourceforge.net/
Description: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. This approach is superior to the conventional process flow approach, if at least one of the following statements applies: * complex process with exceptions and special cases * execution sequence is dependent on multiple factors * possibility of manual intervention of process flow * content-based dependence amongst activities * strong requirements to modularity * strong requirements to flexibility * loose process coupling


5. Bonita
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://bonita.objectweb.org/
Description:Bonita is a J2EE workflow system providing out of the box workflow functionalities to define and run business processes such as the XPDL workflow defintion module, the J2EE based workflow engine, the JMS based awareness infrastructure or the interoperability services. Bonita is Open Source and is downloadable under the LGPL License.


6. Bossa
By:
License:GNU General Public License (GPL)
URL:http://www.bigbross.com/bossa/
Description: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.


7. Open for Business Workflow Engine
By:
License:MIT License
URL:http://www.ofbiz.org/docs/workflow.html
Description:The Open for Business Workflow Engine is based on the WfMC and OMG specifications. (See the related documents for information on these specs.) The Workflow Engine 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.


8. OpenWFE
By:
License:BSD License
URL:http://www.openwfe.org/
Description:OpenWFE is an open source workflow engine. It is implemented in Java, and is available under the BSD license. OpenWFE not only features a workflow engine, but also a full fledged Business Process Management Suite. OpenWFE contains these features and many more: * a worklist component for storing workitems (tasks) for participants, * an APRE component, allowing you to implement automated agents into your work flows, * Droflo, our web-based flow designer, * and a well-documented REST interface and several libraries to access it, with more on the way.


9. WfMOpen
By:
License:GNU General Public License (GPL)
URL:http://wfmopen.sourceforge.net/
Description: 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). The workflow component is based on a set of JAVA interfaces that define an API for a workflow management facility. The basic "omgcore" interfaces follow OMG's Workflow Management Facility Specification, V1.2 very closely, while making some modifications to adapt the CORBA service to the established design practices for a Java API.


10. XFlow
By:
License:Apache Software License
URL:http://xflow.sourceforge.net/
Description: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. XFlow runs within an EJB and servlet container. JBoss 4.0 (with bundled Tomcat) is the container used in this implementation. The architecture supports distributed and parallel processes within an organization's firewall as well as across organizational boundaries. XFlow is designed for scalability, extensibility and ease of integration with security models and legacy processes. XFlow's service-oriented architecture supports both a simple Java API as well as a web-service (SOAP/HTTP) interface.


11. JFolder (formerly PowerFolder)
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://www.powerfolder.org/
Description: JFolder (formerly PowerFolder) is a complete application creation and production solution. You can develop many applications without writing any code, even scripting. JFolder contains features critical to many applications - including web pages, workflow, security, persistence, email, file management, and data access


12. Taverna
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://taverna.sourceforge.net/
Description: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 GNU Lesser General Public License (LGPL).


13. Freefluo
By:
License:
URL:http://freefluo.sourceforge.net/
Description: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. Freefluo is very flexible, at its core is a reusable orchestration framework that is not tied to any workflow language or execution architecture. Freefluo includes extension libraries that enable execution of workflows written in a subset of WSFL. Support exists for for discovery via standard UDDI and recording of provenance. Freefluo is one component within the myGrid toolkit. The myGrid toolkit is composed of numerous useful software components. These components are designed to demonstrate higher level functionalities over an existing Grid infrastructure that support scientists in making use of complex distributed resources. These higher level functionalities extend through service lookup and discovery, provenance and data storage.


14. JFlower
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://sourceforge.net/projects/jflower/
Description:JFlower is workflow engine written in java, extendible with java plugins. The server parse xml document for execute jobs, and check conditions. The session data are stored on a database, so the server is fully scalable.


15. Syrup
By:
License:The Artistic License
URL:http://syrup.sourceforge.net
Description: Syrup is an adaptive Workflow system with a difference. Like any other Workflow solution, Syrup can be used to describe the tasks, procedural steps, required input and output information and tools needed for each step in a business process [1]. To be able to do this, Syrup provides five basic concepts: Tasks, Links, Workflows, Workers and the WorkSpace. Additionally, the minimal core is build in such a way that integrating Syrup into an existing infrastructure poses a minimal challenge to developers.


16. ActiveBPEL
By:
License:GNU General Public License (GPL)
URL:http://www.activebpel.org/
Description:ActiveBPEL, LLC is an open source software organization that licenses and distributes the ActiveBPEL engine technology. The 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. The ActiveBPEL engine technology is developed and maintained by Active Endpoints, Inc. (AEI), which also uses the same technology in some of its commercial products. AEI created the ActiveBPEL open source project because AEI believes that the open source model is an effective means through which to foster community interest, education and development around the BPEL standard.


17. AntFlow
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://antflow.onionnetworks.com/
Description:AntFlow is a tool for the automation and scheduling of data system tasks, including those with complex dependencies and workflow logic. Up until now it's been a component in the WAN Transport product my employer, Onion Networks, sells. They've agreed to let me open up the most generally-useful portions of the system and this is the place I'll be doing it. They've still got plans for parts of it that include productizing or monitizing or whatever it is people like that do, but I think I can get a lot of the good stuff out here under the Apache license.


18. Dalma
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://https://dalma.dev.java.net/nonav/maven/index.html
Description: Many applications of today need to have a part of the program that waits for other entities. For example, a mailing list manager waits for an e-mail to trigger actions. A web application waits for incoming HTTP requests. Sometimes those applications are conversational; they not only just receive messages, but also send out messages. Those programs often maintain some state and change it as the conversation progresses. Often there are multiple conversations running concurrently. Those are what we call "workflow" applications.


19. Swish
By:
License:GNU Library or Lesser General Public License (LGPL)
URL:http://www.roxwood.com/swish.jsp
Description:Swish is an open source web services-based workflow API and engine. The name Swish is an acronym derived from the phrase Simple Web services Interface to Shark. Shark is a powerful open source workflow engine framework based on WfMC standards and developed using Java.


20. Business Processes
By:
License:Apache Software License
URL:http://www.bpmscript.org
Description:Business Processes are often long running and involve human intervention. Business Process Management or BPM is used to attempt to automate these business processes. To get some idea of what could consitute a business process, see the examples page.


java2s.com  |  | Contact Us | Privacy Policy
Copyright 2009 - 12 Demo Source and Support. All rights reserved.
All other trademarks are property of their respective owners.