Yes of course.
To enable Sword v2, in Dspace 1.8 we did the following:
1) Defined an extra context path in /opt/tomcat/conf/server.xml
<!-- DEFINE A CONTEXT PATH FOR DSpace swordv2 -->
<Context path="/swordv2" docBase="/opt/dspace/webapps/swordv2" debug="1"
reloadable="true" cachingAllowed="false"
allowLinking="true"/>
2) Amended the swordv2-server.cfg file in /opt/dspace/config/modules
#---------------------------------------------------------------#
#----------------SWORD 2.0 SERVER CONFIGURATIONS----------------#
#---------------------------------------------------------------#
# These configs are only used by the SWORD Server interface, #
# version 2.0 (used by DSpace to accept ingest packages via #
# SWORD 2.0 protocol) #
#---------------------------------------------------------------#
# the base url of the sword 2.0 system
#
# the default if {dspace.url}/swordv2
#
#url = http://www.myu.ac.uk/swordv2
url = http://vmerdmsdspace01.ex.ac.uk/swordv2
# The base URL of the SWORD collection. This is the URL from
# which DSpace will construct the deposit location urls for
# collections.
#
# The default is {dspace.url}/swordv2/collection
#
# In the event that you are not deploying DSpace as the ROOT
# application in the servlet container, this will generate
# incorrect URLs, and you should override the functionality
# by specifying in full as below:
#
# collection.url = http://www.myu.ac.uk/swordv2/collection
collection.url = http://vmerdmsdspace01.ex.ac.uk/swordv2/collection
# The base URL of the SWORD service document. This is the
# URL from which DSpace will construct the service document
# location urls for the site, and for individual collections
#
# The default is {dspace.url}/swordv2/servicedocument
#
# In the event that you are not deploying DSpace as the ROOT
# application in the servlet container, this will generate
# incorrect URLs, and you should override the functionality
# by specifying in full as below:
#
# servicedocument.url = http://www.myu.ac.uk/swordv2/servicedocument
servicedocument.url = http://vmerdmsdspace01.ex.ac.uk/swordv2/servicedocument
AND what I had omitted to do was:
3) Add a proxy setting to /etc/httpd/conf/hosts/rdms.conf (see the swordv2 code
lines at the bottom of this following):
[root@vmerdmsdspace01 httpd]# cat /etc/httpd/conf/hosts/rdms.conf
<VirtualHost *:80>
Include conf/hosts/rdms.inc
ProxyPass /repository ajp://localhost:8009/repository
ProxyPassReverse /repository ajp://localhost:8009/repository
ProxyPass /oai ajp://localhost:8009/oai
ProxyPassReverse /oai ajp://localhost:8009/oai
ProxyPass /standard ajp://localhost:8009/standard
ProxyPassReverse /standard ajp://localhost:8009/standard
ProxyPass /manager ajp://localhost:8009/manager
ProxyPassReverse /manager ajp://localhost:8009/manager
ProxyPass /sword ajp://localhost:8009/sword
ProxyPassReverse /sword ajp://localhost:8009/sword
ProxyPass /swordv2 ajp://localhost:8009/swordv2
ProxyPassReverse /swordv2 ajp://localhost:8009/swordv2
RedirectMatch 301 ^/$ /repository/
RedirectMatch 301 ^$ /repository
</VirtualHost>
Hope this helps.
Best regards and thanks to everyone who helped on this.
Ian
------------
Ian Wellaway
Senior System Support & Development Officer - Academic Systems (Room 911)
Wednesdays only
&
Technical Developer, Open Exeter - Infrastructure Systems (Room 54) Monday -
Tuesday, Thursday - Friday
Exeter IT
Laver Building
University of Exeter
EX4 4QE
UK
tel +44 1392 722852
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of helix84
Sent: 21 June 2012 13:12
To: Wellaway, Ian
Cc: [email protected]
Subject: Re: [Dspace-tech] Sword 2 with Dspace
On Thu, Jun 21, 2012 at 2:06 PM, Wellaway, Ian <[email protected]>
wrote:
> FYI, we’ve fixed this issue. The way our server is set up required a
> proxy entry in one of the http files.
Good to hear that. Can you please be more specific to help any potential
visitors of this thread from the future?
Regards,
~~helix84
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech