|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk
_______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
While it is no problem to use the handle server as it can be downloaded from handle.net, it is not possible to use a handle server that is in use with other software already. You can configure the handle server to either use its own storage, to use a custom postgresql database or to use a storage plugin as we do. With our code you can use one handle server for multiple DSpace instances but you still need one handle server which is solely dedicated to DSpace. You cannot use one single handle server for DSpace and for another software at the same time (unless you write your own plugin). That was the reason why I thought it would be good to make it as easy as possible to setup this handle server for DSpace.
If someone wants to use the handle server as it comes with DSpace he would have to add the jars the ExternalHandlePlugin depends on (gson and log4j), a property file for log4j and the ExternalHandlePlugin itself, of course. Right now, the ExternalHandleServer uses a system property to get the URLs of the DSpace instances whose handles it should resolve. To set this system property one has to edit the start script of the handle server. If you use the handle server as it comes from handle.net, it has one directory for the jars and scripts for all handle servers and one directory per server for its configuration. So we either have to clearly document how to copy and change the start script or we have to change the way how the ExternalHandleServer gets the URLs of the DSpace instances.