Skip to content

Workflow Runner API

Soumya Brahma edited this page Feb 5, 2016 · 57 revisions

Table of Contents

Status
The first implementation of this API is made to interface the Taverna Server, and is under development. A deployment of the latest snapshot is available at http://sandbox.wf4ever-project.org/runner/default/ - which accesses http://sandbox.wf4ever-project.org/taverna-server/

API function overview

Research Objects, for the purpose of Wf4Ever, will generally contain workflows. In order to assess if a workflow is functional, it is generally useful to be able to (re)-execute a workflow.

Different workflow systems have different ways of running a workflow. For instance, Taverna has the Taverna Server, while Wings has a portal and a Pegasus/Condor engine in the backend. This API intends to provide a common lightweight interface within Wf4Ever for features such as "Run this workflow please" and "Show me the data from that workflow run".

At its heart, this API mirrors the RODL API, but the ROs exposed by this service each represent a particular workflow run, structured to show inputs, outputs, console logs, provenance and annotations containing wfprov and wfdesc mappings. Thus it intends to be possible to use existing RODL compatible tools with this service, for instance adding from the RO command line tool, browsing with the Portal or transforming to wfdesc using the Workflow Transformer service.

http://www.webapps-bg.net/Webproxy/browse.php?u=uPjByaXUV1cPhBSWpHzS3345%2B110MEcj7lbHoMJh7oT48qx63RoJmUJLP5U6DI1f%2FqpEoIQRN2kG%2F1LEZ9as%2F2hm2cXShlXotdXrTjNZnJOJIUV9aWSjNe9e4jKM5SHw67BlHiOT%2BbazCnJgiAnad%2Fv4onZr1uzVYg%3D%3D&b=29

Clone this wiki locally