This forum is about both workflow (middleware) software and services, also called components, (small chunks of code for performing specific tasks). Please use a very broad definition since any sort of software that can be used to connect or compose services into larger processes fits in this forum. Equally, any software that has been found to be useful by the community and can be made into a re-usable component is appropriate to this forum. Both fully automated processes and those which include people should be part of these discussions. Also, it's not just about software! The layout of the processes, often called business processes and business integration patterns, are equally part of the discussion. None of these discussion need to be Fedora-specific since this is all about connecting any component from any source including your existing systems.
This registry includes known software aimed at workflow that works with recent releases of the Fedora Commons Repository Software (2.2.x and 3.x).
Know of anything that's not listed? Please add it below! And don't hesitate to add a project that is just getting started; it is good for the community to know what each other is working on.
Title and Link | Summary | Status | Compatibility | Contact |
|---|---|---|---|---|
The unique name of the software or project, linked to a URL providing more information. | One-line description | Released or Unreleased; date of last update | Fedora 2.2.x or Fedora 3.x | Individual and/or Organization |
A demonstration of how to use Fedora to provide data to the Kepler Scientific Workflow Engine | Experimental | Fedora 3.2+ | Rick Moore - Fedora Commons | |
A prototype, ruby-based workflow manager listening to the JMS | Prototype | Fedora 3.2+ | Chris Beer - WGBH | |
A Java program to listen to JMS messages from Fedora and launch an external script to handle those messages. Essentially it acts as a kind of "gateway" connecting JMS and a script (XProc, bash, JavaScript, Windows batch file, etc), analogously to how CGI connects HTTP and a script. | Released | Fedora 3.4+ | ||
| Fedora/Taverna Integration | A PHP-based microservices framework that listens to Fedora's JMS messages and launches triggered workflows to a Taverna Server. | Released 2014-01-20 | Fedora 3.6+ (possibly earlier versions) | Mark Leggott |
Feel free to add any Mailing lists, blogs, regular calls, IRC channels, etc. used by people working on this type of project.
If you don't know where else to look, check the Create Forum and use the fedora-commons-create google group.
Title and Link | Summary | Status | Compatibility | Contact |
|---|---|---|---|---|
The unique name of the software or project, linked to a URL providing more information. | One-line description | Released or Unreleased; date of last update | Fedora 2.2.x or Fedora 3.x | Individual and/or Organization |
Taverna is an open source tool for designing and executing workflows created by the myGrid project and funded through the OMII-UK. | Released | N/A | Open source project | |
Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration. | Released | N/A | Open source project |
Does it irk you when people keep doing things the "wrong" way? Document the best practices here and they'll (hopefully) learn!
What challenges and roadblocks so people hit when working on these types of projects? What topics and ideas do they get really excited about?