On Wed, Apr 29, 2009 at 11:45, Jerzy Orlowski <[email protected]> wrote: > I is similar question "remote execution problem". > More specific: Is there any ar does anyone plan to make a SOAP or other > web service that has two inputs (scufl or t2 flow file as first and > workflow input data xml file as a second input) and returns XML file > with workflow results?
Several solutions for this have been made, one of them from myGrid: http://www.mygrid.org.uk/tools/taverna/associated-tools/taverna-remote-execution/ However - the service is designed for long-running workflow, so there's not a single 'post and wait' method - you have to first upload your workflow, then your data (as a baclava document), then a job combining these two and putting it on the execution queue, then check the status of that job, check it again, check it again, ok, finished, then fetch the results (as a baclava document). The service uses Taverna 1 under the hood, and the interface is a RESTful one. There's client libraries for Java, Python and Ruby. If you have a service, you can register it with myExperiment to execute workflows on your behalf. As workflows are allowed to do all sorts of things, you can't have a general web service open to the world to execute any random workflow. For instance, I could then upload a workflow that contained a beanshell script that deleted all the files on the server. (or more likely way of abuse: Started sending thousands of emails about Viagra). There's two ways out of this: a) Limit which workflows to run - someone will pre-approve a workflow b) Limit which users are allowed to run workflows - someone will have to pre-approve the user The execution service uses the b) approach. David has also built a t2platform based execution service that is very similar and I believe also with a RESTful interface, this is to be released in the next few weeks, however I don't know much details about that. David..? We've also talked about letting the service take an uploaded workflow, "approve" it, and then generate a WSDL interface for that particular workflow. The WSDL operation would then have input and output parameters matching the workflow input and output ports, so the caller wouldn't need to know Baclava, what are the required ports, etc. - even not knowing that it's a Taverna workflow at all. The caGrid team did a prototype that can do this 'workflow as a service', which you can read more about in an upcoming paper by Wei Tan et al from IEEE 7th International Conference on Web Services (ICWS 2009). We'll post to this list when this paper has been published. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ taverna-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/taverna-users Documentation: http://www.mygrid.org.uk/usermanual1.7/ FAQ: http://www.mygrid.org.uk/wiki/Mygrid/TavernaFaq Biological Services: http://www.mygrid.org.uk/wiki/Mygrid/BiologicalWebServices
