Skip to end of metadata
Go to start of metadata

Taverna Server 2.5 is the build of Taverna Server that uses the Taverna 2.5.0 Execution Engine core. It also has a substantial number of new and extended features over Taverna Server 2.4. The supported release of Taverna Server 2.5 is 2.5.4, which requires at least Java 7.

Contents

First Time Here?

Start with the Conceptual Interface to learn how to use an installation of Taverna Server, or the Installation Guide to learn how to get Taverna Server on your system.

Features

Taverna Server 2.5.4 supports all features including run bundle/provenance generation. It requires Java 7 (OpenJDK 7 is recommended but not mandatory) or later.

To summarise the features, they are:

  • Upload and execute arbitrary Taverna 2 workflows
    • Based on Taverna 2.5.0 Workflow Engine, Enterprise edition
    • Includes support for Taverna Components and User Interaction processors in workflows
    • Workflow run inputs may be single values or lists of values
    • Workflow runs are created by giving a workflow to the server, either by value (literal document) or by reference (URL)
    • Introspection of the server and the runs you create on it
      • The server describes its abstract capabilities, what features it supports
      • Workflow runs can have arbitrary names attached to them
      • Workflow runs can be asked to supply a description of their inputs and outputs
  • Access by REST and SOAP interfaces
    • Supports clients in many programming languages; you don't need to code in Java to use Taverna Server
      • Taverna Player is the strongly recommended Ruby client library for use with Ruby-on-Rails
      • We also provide a t2-server gem for general Ruby client use
    • All functionality available through both interfaces
  • Manage files for workflows
    • Make files, read files, delete files
    • Create subdirectories, list directory contents
    • Access intermediate data and logs
    • Can download a whole directory structure as a ZIP
  • Tidies up when workflow runs expire
    • Expiry time fully configurable
    • Can force immediate deletion of a workflow run
  • Generates metadata about workflow runs
    • Produces standard description of resources used during run
    • Produces Run Bundleswhen requested
      • Special ZIP file that contains formal description of the workflow run, designed for sharing, including the inputs, outputs and provenance trace
  • Secured workflow execution
    • Encrypted communication supported
    • Multiple users
      • Users isolated from each other (via sudo)
      • Workflows isolated from server
      • Users may grant access to other users
    • Specify credentials for workflows to access back-end services
  • Management interface to allow tuning of service limits
    • Administrative access to all server's tunable parameters
    • Authenticated web interface, JMX
    • Usage monitoring/accounting
  • Numerous general quality improvements
    • Improved speed
    • Improved robustness
      • State can persist over (limited) server restarts
    • Improved installation
      • Self-contained server package
    • Support for transfer of large data files

Known Limitations

There is a known limitation of 100MB on the size of individual atomic values that may be present on a workflow port, processor port or datalink of a Workflow. With a list, this is a restriction on the size of the elements in the list, and not on the total size of the list’s items, though it is recommended that lists be kept substantially smaller than this to ensure that they fit in memory. The recommended workaround for this is to keep large values in files on disk or in a database, and to only pass references to those files (i.e., filenames) along datalinks.

Labels
  • None