Hi Alan, > Normally you would publish the component onto myExperiment (or an equivalent > component registry). You can do this just by creating a family on > myExperiment and copying your component into it. (You will need a login > account on myE to do this.) In the workflow, you will need to replace your > local component by the myE component > Your component on myE will be, by default, private - so you will need to pass > your credentials to the workflow run. If you want other people to be > able to run the workflow and its components, you can use the sharing > permissions on myE to specify who can see it (including making it fully > public).
Thanks for the information. I am not sure it would be feasible to use external component registry for this particular project that I am working on. You have mentioned an equivalent component registry. Can such component registry be set up in-house? Is there a documentation on this? Also, is there is a documentation on how to configure Taverna server to use " equivalent component registry "? Thanks! Alex. -----Original Message----- From: Alan R Williams [mailto:[email protected]] Sent: Tuesday, July 22, 2014 10:56 AM To: [email protected] Subject: Re: [Taverna-users] Taverna 2.5 server / BeanShell / Class: JSONObject not found in namespace On 22/07/2014 15:09, Kotliarov, Alex (NIH/NLM/NCBI) [C] wrote: [snip] > Another question just poped-up and it is regarding how to properly deploy > component(s) for a run. > > A workflow that I try to run uses a component: > > <net.sf.taverna.t2.component.ComponentActivityConfigurationBean > xmlns:ns9="http://taverna.sf.net/2008/xml/t2flow"; xmlns=""> > > <registryBase>file:/C:/Users/kotliaro/AppData/Roaming/taverna-core-2.5.0/components/ > </registryBase> > <familyName>Smart</familyName> > <componentName>REST_action</componentName> > <componentVersion>1</componentVersion> > </net.sf.taverna.t2.component.ComponentActivityConfigurationBean> > > > I assume that I would need to upload this component to one of the run's > directories. Also, what about <registryBase> element? How Taverna server > resolves where to get the component from? > Of course it all runs in the workbench, but seems like when server executes > this workflow and gets to executing this component I get ""Service not > executable" error. Normally you would publish the component onto myExperiment (or an equivalent component registry). You can do this just by creating a family on myExperiment and copying your component into it. (You will need a login account on myE to do this.) In the workflow, you will need to replace your local component by the myE component. Your component on myE will be, by default, private - so you will need to pass your credentials to the workflow run. If you want other people to be able to run the workflow and its components, you can use the sharing permissions on myE to specify who can see it (including making it fully public). Alan ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ 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/ ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ 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/
