Proxy Settings For OAI Harvester In XMLUI

[Gavin Spomer]

When testing the settings for the harvester in DSpace 6.3 / xmlui, it eventually times out with error "OAI server could not be reached". I'm guessing it's because of being behind our campus web proxy, but I've configured the host and port in both Tomcat's setenv.sh:

   JAVA_OPTS="$JAVA_OPTS -Dhttp.proxySet=true -Dhttp.proxyHost=our.proxyhost.edu -Dhttp.proxyPort=3128"

and my local.cfg file:

   http.proxy.host = our.proxyhost.edu

   http.proxy.port = 3128

Shouldn't that be enough? Which proxy settings does the harvester in xmlui use? 

[Gavin Spomer]

I tried using a "fake oai server" for the harvester test in xmlui that was internal to our university and not only did it output something other than "OAI server could not be reached" (was "OAI did not respond to ListMetadataFormats query (:null ; :null): null"), but it didn't hang for a long time either. So I'm reasonably sure the problem is that it's not using our campus web proxy to contact the bepress oai server. Checked both the tomcat and dspace logs, but nothing in there related to this.

If someone knows which proxy settings the xmlui harvest test uses (tomcat, local.cfg or ???), I'd really appreciate it.

[Gavin Spomer]

Throwing in the towel on this; something I rarely do. Nothing I've tried is able to get the harvester to reach our Bepress host.

I've had good luck importing an item via command line / simple archive format, so I'm going to write my own script that fetches the metadata and files via OAI and create the archive / item directories.

 - Gavin