Re: [Dspace-tech] Manakin and Admin Utilities With Apache Redirection

2009-04-02 Thread Sean Carte 
2009/4/1 Sean Carte sean.ca...@gmail.com:
 I've been trying to get the XMLUI interface to work with Apache
 redirection, but I can't access the admin utilities (everything else
 works):

 For example, this URL: http://10.4.36.18/admin/metadata-registry

 results in this error:

 HTTP Status 404 - /admin/metadata-registry
 type Status report
 message /admin/metadata-registry
 description The requested resource (/admin/metadata-registry) is not 
 available.

...
 I have noticed that, when using the xml ui, if I append xmlui to the
 URL, everything works, e.g.:

 http://10.4.36.18/xmlui/admin/metadata-registry

Here's a simple workaround:

Override the header in your xsl file and replace

a
xsl:attribute name=href
xsl:value-of
select=/dri:document/dri:meta/dri:userMeta/

dri:metada...@element='identifier' and @qualifier='loginURL']/
/xsl:attribute

with:

a href=xmlui/login


This makes the 'Login' link at the top right of the screen include the
'xmlui', which from then on will be part of the path.

Thereafter, it's a simple matter of persuading admin users to use that
link to log in.

Sean
-- 
Sean Carte
esAL Library Systems Manager
+27 72 898 8775
+27 31 373 2490
fax: 0866741254
http://esal.dut.ac.za/

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

[Dspace-tech] Manakin and Admin Utilities With Apache Redirection

2009-04-01 Thread Sean Carte 
I've been trying to get the XMLUI interface to work with Apache
redirection, but I can't access the admin utilities (everything else
works):

For example, this URL: http://10.4.36.18/admin/metadata-registry

results in this error:

HTTP Status 404 - /admin/metadata-registry
type Status report
message /admin/metadata-registry
description The requested resource (/admin/metadata-registry) is not available.

With this in the Apache access log:

10.4.36.100 - - [01/Apr/2009:08:09:29 +] GET
/admin/metadata-registry HTTP/1.0 404 1018 http://10.4.36.18/;
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032711
Ubuntu/8.10 (intrepid) Firefox/3.0.8

There's nothing in the dspace.log, nor in the Apache error log.

But if I switch over to the jspui interface, it all works:

10.4.36.100 - - [01/Apr/2009:08:15:54 +] GET
/dspace-admin/metadata-schema-registry HTTP/1.0 200 9649
http://10.4.36.18/dspace-admin/; Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:1.9.0.8) Gecko/2009032711 Ubuntu/8.10 (intrepid)
Firefox/3.0.8
10.4.36.100 - - [01/Apr/2009:08:15:54 +] GET /styles.css.jsp
HTTP/1.0 20018497
http://10.4.36.18/dspace-admin/metadata-schema-registry; Mozilla/5.0
(X11; U; Linux i686; en-US; rv:1.9.0.8) Gecko/2009032711 Ubuntu/8.10
(intrepid) Firefox/3.0.8

I have the following in /dspace/config/dspace.cfg:

dspace.url = http://10.4.36.18:8080/jspui
#dspace.url = http://10.4.36.18:8080/xmlui

And the following in /usr/share/tomcat5.5-webapps:

lrwxrwxrwx  1 root root   22 2009-04-01 09:58 ROOT - /dspace/webapps/jspui/
lrwxrwxrwx  1 root root   22 2009-03-26 10:16 ROOT_xmlui -
/dspace/webapps/xmlui/

When switching between the interfaces, I change the ROOT symlink and
the dspace.url appropriately, then restart tomcat.

I have the following in /etc/apache2/mods-enabled/proxy.conf:

ProxyPass  /  ajp://localhost:8009/
ProxyPassReverse  /  ajp://localhost:8009/

I have noticed that, when using the xml ui, if I append xmlui to the
URL, everything works, e.g.:

http://10.4.36.18/xmlui/admin/metadata-registry

But that's exactly what I hoped to avoid.

Have I gone wrong somewhere?

Sean
-- 
Sean Carte
esAL Library Systems Manager
+27 72 898 8775
+27 31 373 2490
fax: 0866741254
http://esal.dut.ac.za/

--
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech