Archive for the ‘Workflow’ Category

Java Open Source workflow engine based on XPDL

June 24, 2007

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.

Every single component (persistence layer, assignment manager, etc.) can be used with its standard implementation or extended/replaced by project specific modules. This way Enhydra Shark can be used as a simple “Java library” in servlet or swing applications or running in a J2EE container supporting a session beans API, Corba ORB or accessed as a web service.

Sample ToolAgents are available for many different common tasks in automated workflows.

Storage of process and activity instances is done via a configurable persistence API.

The workflow engine kernel supports configurable LRU caching of active workflow objects for high load scenarios. Caching can be turned off for clustered installations.

The XForms and XSLT based web worklist handler and admin application can be easily adopted to your needs.

In contrast to many other solutions on the market Enhydra Shark gives you the freedom to define your own GUI and to integrate existing systems components of YOUR environment !

OpenSymphony OSWorkflow

June 24, 2007

OSWorkflow overview

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.

OSWorkflow gives you this flexibility

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. That’s not to say that actual code is needed to implement situations like this, but a scripting language must be employed to specify these conditions. It is not expected that a non-technical user modify workflow. We’ve found that although some systems provide GUIs that allow for simple editing of workflows, the applications surrounding the workflow usually end up damaged when changes like these are made. We believe it is best for these changes to be made by a developer who is aware of each change. Having said that, the latest version provides a GUI designer that can help with the editing of the workflow.


June 18, 2007

OpenFlow è un motore di workFlow sviluppato da Icube secondo il modello Open Source.
E’ basato su una struttura ad oggetti, ha un potente sistema di gestione delle eccezioni e supporta il Dynamic Redesign (Process Optimization).
Queste caratteristiche lo rendono molto più flessibile degli altri sistemi di workflow esistenti.
OpenFlow supporta gli standard aperti (XML, XML-RPC) e tutti gli standard web; facilita l’integrazione tra sistemi eterogenei grazie all’accesso alla maggior parte dei database relazionali.
OpenFlow è activity based, multipiattaforma (Windows NT, Windows2000, Linux/Unix), Web based, basato sugli standard del WfMC, integrato e costruito con l’application server Zope, ed è Open Source.