Workflow Launcher enables stand-alone running of workflows from the command line. It runs Taverna workflows without popping up the GUI. Nice for running those big things on some server with lots of memory, but it also means you will not get much progress feedback while it is running.
It is currently only available for Taverna 1.7.x. Similar tool for Taverna 2.1 will be available in the first quarter of 2010 according to our Roadmap.
executeworkflow script
executeworkflow script runs Taverna 1.7.x workflows without popping up the GUI. Nice for running those big things on some server with lots of memory, but it also means you will not get much progress feedback while it is running.
The executer works like this:
C:\taverna-1.7.2> executeworkflow -help
usage: executeworkflow <workflow> [..]
Execute workflow and save outputs. Inputs can
be specified by multiple -input options, or
loaded from an XML input document as saved from
Taverna. By default, a new directory is created
named workflow.xml_output unless the –output
or –outputdoc options are given. All files to
be read can be either a local file or an URL.
-help print this message
-input <name filename> load the named input from file or URL
-inputdoc <document> load inputs from XML document
-output <directory> save outputs as files in directory, default is
to make a new directory workflowName_output
-outputdoc <document> save outputs to a new XML document
-report <file> save progress report in file, default is
progressReport.xml in the output directory
So simple examples would be:
executeworkflow file:myworkflow.xml
executeworkflow -input swiss_in swiss_in.txt file:myworkflow.xml
executeworkflow -inputdoc file:inputdoc.xml file:myworkflow.xml
or in *NIX:
sh ./executeworkflow.sh file:myworkflow.xml
sh ./executeworkflow.sh -input swiss_in swiss_in.txt file:myworkflow.xml
sh ./executeworkflow.sh -inputdoc file:inputdoc.xml file:myworkflow.xml
This would create a new directory myworkflow.xml_output containing files for the outputs. If you would like, you can add -outputdoc outputs.xml and view outputs.xml using dataviewer. Similarly, you can save complex inputs (i.e. lists) by making them in Taverna 1.7.x Workbench, and saving the input document. This input document can be used as -inputdoc inputs.xml
workflowlauncher application
The workflowlauncher application shows how workflows can be executed programmatically outside of Taverna.
- Source for workflowlauncher using Taverna 1.7.1.0
- Using the Taverna API to programmatically execute a workflow from the Taverna 1.7 manual







