On 17/06/2015 10:44, Daniele Tartarini wrote:
I developed a series of taverna components most of them nested. I would like to deploy them on a taverna server instance on a different machine.How can this be done in reliable way?
Since you're talking about local components, you have two basic options right now. Option 1: Upload the components to myExperiment (strictly anything that talks the API, but myE is the only service I know of that actually does that). You do not need to make the components public, but you'll need to set a workflow run to have appropriate username/password pair for myExperiment to access them if you use non-public components. (That's actually obviously necessary, once you think about it.) If you're making the components public, this is actually very convenient indeed. Option 2: Put the components on the server somewhere and edit the workflows to know about that server-local location. This is what I did with components in the SCAPE project, and it actually works really well (I was merging the components into the customised server build that we were using, but I also had a really complicated workflow rewriter that made that sort of thing really easy). The downside is that the workflow that you run on the server is not the workflow that you run on your desktop. NOT AN OPTION: Just uploading the workflow and hoping that it will all magically work. We don't have that sort of magic. :-D The server has a different filesystem to your client; the local component registry address doesn't map to anywhere else. Donal.
<<attachment: donal_k_fellows.vcf>>
