Release date: 2018-01-17
The Apache Taverna (incubating) team is pleased to announce the release of:
This announcement is also available at: https://s.apache.org/taverna-server-3.1.0
Apache Taverna Server enables you to set up a dedicated server for remotely executing Taverna workflows, exposed as REST Web APIs and WSDL Web Services. This enables integration of Taverna workflows into web portals, mobile applications, as well as allowing desktop users to execute remotely on local server or cloud infrastructure. Taverna Server can be configured for POSIX user isolation (e.g. sudo) and can restrict which workflows to execute.
Download apache-taverna-server 3.1.0-incubating: https://taverna.incubator.apache.org/download/server/
Apache Taverna Server relies on these earlier releases:
Major changes since Taverna Server 2.5.4 are described below:
Workflows are now executed with Apache Taverna Command-line Tool 3.1.0-incubating, which adds support for executing SCUFL2 workflows using the Apache Taverna Engine.
Package names have changed to
org.apache.taverna.server.* and source code modules have been reorganized. See the Javadoc for details.
This release adds the taverna-server-client library, which can be used by Java clients to connect to the Taverna Service REST API.
These activities are no longer supported directly by Apache Taverna:
For details of bug fixes since Taverna Server 3.0, see:
See the included taverna-server README for details on how to build the source code.
For full documentation of installing, configuring and using Taverna Server, see https://taverna.incubator.apache.org/documentation/server/
Please subscribe to and contact the dev@taverna mailing list for any questions, suggestions, and discussions about Apache Taverna.
Bugs and feature plans are tracked in the JIRA Issue tracker under the corresponding components. Anyone may add, comment or work on an issue!
Apache Taverna is an effort undergoing incubation at The Apache Software Foundation (ASF) sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.