Apache Taverna
 |
|
Taverna Workbench
|
|
| Developer(s) | Apache Software Foundation (myGrid for 2.x) |
|---|---|
| Stable release | 2.5 / April 16, 2014 |
| Development status | Active |
| Written in | Java |
| Operating system | Linux, Mac OS X, Microsoft Windows |
| Type | Scientific workflow system |
| License | Apache License 2.0 (LGPL for 2.x) |
| Website | taverna |
Apache Taverna is an open source software tool for designing and executing workflows, initially created by the myGrid project under the name Taverna Workbench, now a project under the Apache incubator. Taverna allows users to integrate many different software components, including WSDL SOAP or REST Web services, such as those provided by the National Center for Biotechnology Information, the European Bioinformatics Institute, the DNA Databank of Japan (DDBJ), SoapLab, BioMOBY and EMBOSS. The set of available services is not finite and users can import new service descriptions into the Taverna Workbench.[1][2][3][4][5][6][7][8]
Taverna Workbench provides a desktop authoring environment and enactment engine for scientific workflows. The Taverna workflow engine is also available separately, as a Java API, command line tool or as a server.
Taverna is used by users in many domains, such as bioinformatics,[9][10] cheminformatics,[11] medicine, astronomy,[12] social science, music, and digital preservation.[13]
Some of the services for the use in Taverna workflows can be discovered through the BioCatalogue - a public, centralised and curated registry of Life Science Web services. Taverna workflows can also be shared with other people through the myExperiment social web site for scientists. BioCatalogue and myExperiment are another two product from the myGrid consortium.
Taverna is used in over 350 organizations around the world, both academic and commercial. As of 2011, there have been over 80,000 downloads of Taverna across different versions.
Capabilities
Taverna workflows can invoke general SOAP/WSDL or REST Web services, and more specific SADI, BioMart, BioMoby and SoapLab Web services. It can also invoke R statistical services, local Java code, external tools on local and remote machines (via ssh), do XPath and other text manipulation, import a spreadsheet and include sub-workflows.
Taverna Workbench includes the ability to monitor the running of a workflow and to examine the provenance of the data produced, exposing details of the workflow run as a W3C PROV-O RDF provenance graph,[14] within a structured Research Object bundle[15] ZIP file that includes inputs, outputs, intermediate values and the executed workflow definition.[16]
Taverna includes the ability to search for services described in BioCatalogue to invoke from workflows. However, services do not need to be described within BioCatalogue to be included in workflows as they can be added from a WSDL Web Service description or entered as a REST URI pattern.
Taverna also includes the capability to search for workflows on myExperiment. The Taverna Workbench can download, modify and run workflows discovered on myExperiment, and also upload created workflows in order to share them with others using the social aspects of myExperiment.
Taverna workflows do not need to be executed within the Taverna Workbench. Workflows can also be run by:
- a command line execution tool
- remote execution server that allow Taverna workflows to be run on other machines, on computational grids, clouds, from Web pages and portals
- online workflow designer and enactor OnlineHPC
Taverna allows pipelining and streaming of data.[17] This means that services downstream in the workflow can start as soon as the first data item is received, without waiting for the whole data list to become available from upstream services and iterations. Taverna services execute in parallel when possible, as Taverna workflows are primarily data-driven rather than control-driven.[18]
Open source community
Taverna has been an open-source project since 2003,[19] with contributors from multiple academic and industry institutions. In 2014-10, Taverna became an independent Apache incubator project,[20] and changed name to Apache Taverna (incubating). The project is developing Apache Taverna 3.x,[21] which license change from LGPL 2.1 to Apache License 2.0.
External links
- Apache Taverna at the Apache incubator
- Taverna homepage (pre-Apache)
- OnlineHPC online workflow designer homepage
References
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
