Taverna has now moved to the Apache Software Foundation. For updated information, see Apache Taverna (incubating).

Taverna Server 2.5

This version of the Server is based on Taverna 2.5 and is called Taverna Server 2.5.4. Documentation for the Server is available on-line.


Download the Taverna Server 2.5.4 WAR and follow the installation instructions.

  • Taverna Server 2.5.4 (WAR, 196 MiB)
    • MD5: 20d27405b27a3418b783777171734514
    • SHA1: d2909ad0b222a001639c5337171b9e2b553f1cbc
  • Installation Guide (PDF, 7 MiB)
    • MD5: a91d2ccb0aca9322a92e9d456a1389aa
    • SHA1: d90daf85c09035caca48536cefd4d2d557aeca3a
  • User Guide (PDF, 13 MiB)
    • MD5: 25f75e419a018d03252c63fbcd111a5f
    • SHA1: d080ea3765e8ef41a8cecc6564bf2aaf11b78199

The software distributor Launchpad has an archive of earlier releases of Taverna Server.

System Requirements

Operating system

The Server can currently be installed on Linux and Mac OS X.


You will need a Java 7 installation or newer. Either OpenJDK 7 or Oracle Java 7 are recommended.

If using Oracle Java 7, you must install the Java Cryptography Extension extension for Java 1.7 and follow the included README on how to install the JCE to lib/security/ of your Java installation. This is not necessary for OpenJDK 7.

WebApp container

You will need a suitable servlet container.

The Server has been developed using Tomcat 6.0.26 as the servlet container, but other versions of Tomcat are known to work (back to at least Tomcat 6.0.20, and up to Tomcat 7.0.53) and other containers may also function correctly as no Tomcat-specific APIs are used in the deployable code. We welcome feedback on which containers work, as well as on how to configure them.

Source Code

The source code to Taverna Server is available from the Taverna project’s space on GitHub. The 2.5.4 release was made automatically using Apache Maven from the 2.5.4 git tag; you may download the exact source tree if you wish, but it is easier to fork and check out the code.

If you encounter any problems, please submit an issue report either to our JIRA issue tracker or using the GitHub issue system; both are monitored. You can also report problems to our support email address.

Related products