> An alternative mechanism could be to have some filespace accessible by the > Taverna Server and to put your components into it. > The workflows would have to be transformed to change the registry location. > That should be possible with a simple edit or an xslt.
This approach works. I have copied components directory to a filespace accessible by Taverna Server and replaced content of `registryBase` xml elements of the workflow xml document with a fully qualified path file:///my/registry/components/ Thanks! Alex. -----Original Message----- From: Alan R Williams [mailto:[email protected]] Sent: Tuesday, July 22, 2014 3:43 PM To: [email protected] Subject: Re: [Taverna-users] Taverna 2.5 server / BeanShell / Class: JSONObject not found in namespace On 22-Jul-14 16:26, Kotliarov, Alex (NIH/NLM/NCBI) [C] wrote: > Hi Alan, Hello >> 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? An equivalent component registry would have to implement the component registry REST API. That is described at http://wiki.myexperiment.org/index.php/Developer:Components One way to do this would probably be to set up your own "myExperiment". The person who knows most abut the myE codebase is back from holiday tomorrow so I can ask him for the best way to do this. Several groups do have their own "myExperiment" so it is do-able. An alternative mechanism could be to have some filespace accessible by the Taverna Server and to put your components into it. The workflows would have to be transformed to change the registry location. That should be possible with a simple edit or an xslt. > Also, is there is a documentation on how to configure Taverna server > to use " equivalent component registry "? Once you have a filesystem that Taverna Server can access or your own myExperiment then Taverna Server will be able to access the components. You should not need to do anything. If you do not want to continue using components, then you should be able to "open them" and see the corresponding nested workflow. There is a trick you can use to the component by the equivalent workflow. I can give details if you want. > Thanks! > > Alex. 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/
