Chris - Many "local installations" of Metacat make use of our existing LDAP system in which we manage users with and without organizational affiliations. I believe an initial Metacat installation points to the Ecoinformatics LDAP server by default, and only requires that your host be networked and able to access ldap.ecoinformatics.org. -ben
On Jan 1, 2010, at 3:40 PM, Chris Weed wrote: > I have to admit setting up the metacat server seems a little > daunting, especially the > LDAP settings, which I am not familiar with. The documentation > doesn't seem to > imply that I need to setup something for this, but that seems > unlikely. > Chris > > On Thu, Dec 31, 2009 at 12:47 PM, Matt Jones <jones at nceas.ucsb.edu> > wrote: > Hi Chris, > > The remote repository in Kepler allows you to store, share, and search > for workflows using a storage server that is accessed using a web > service API. Although technically any server that implements the API > can be used, in practice we have only used the Metacat system for this > -- http://knb.ecoinformatics.org/software/metacat > > You can install your own Metacat and configure Kepler to use it in the > development version of Kepler. Ben Leinfelder, Mike Daigle, and Chad > Berkley should be able to answer any questions you have on setting up > this system. Note that at this point having multiple repositories is > experimental, but it has worked for us. The upcoming Kepler 2.0 should > improve support for workflow repositories. > > Happy New Year, > Matt > > On Thursday, December 24, 2009, Chris Weed <chrisweed at gmail.com> > wrote: > > Hi,I noticed there is an option in Kepler for remote repositories > at library.kepler-project.org and localhost:8080.What are these > repositories, and how can I setup my own repository at localhost: > 8080 or elsewhere on my network to store and access workflows? > > Thanks,Chris > > >
