On Wed, Nov 9, 2011 at 15:43, Alan R Williams <[email protected]> wrote: > In Soaplab2 it creates a set of webservices that wrap the calling of the > tool. Those webservices are then hosted, for example, in Apache Tomcat. > The webservices are, by default, callable by anyone.
Just a note - this can be a good thing, it would mean that your workflow and services would be easier to share and reuse if your services are accessible world-wide. However, if your service goes down or changes significantly, your workflow would also stop working. Running the scripts locally might mean installing Python and various libraries on every machine you want to run the workflow on. Some scripts might be specific for a specific local installation details and not be as portable, such as operating system dependency, file encoding defaults and file paths. Small Python scripts which are completely defined within the Tool definition and only use standard libraries should however be much easier to move along with the workflow. So it's a fine balance - perhaps you might want to start with using the Tool definition to quickly prototype your script and workflow, and then later progress to wrap the script as say a soaplab2 service, to make your workflow more easily available to the general public or other colleagues. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester ------------------------------------------------------------------------------ Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex infrastructure or vast IT resources to deliver seamless, secure access to virtual desktops. With this all-in-one solution, easily deploy virtual desktops for less than the cost of PCs and save 60% on VDI infrastructure costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox _______________________________________________ taverna-users mailing list [email protected] [email protected] Web site: http://www.taverna.org.uk Mailing lists: http://www.taverna.org.uk/about/contact-us/
