I'm trying to figure out what the config settings dspace.hostname dspace.baseUrl dspace.url
really do. I'm trying to figure out if I can configure a virtual host to "transparently" run dspace through apache, without the xmlui path component or any tomcat port numbers etc. So far: I have tomcat running dspace. I did not copy the webapps files over to tomcat's dir, rather I edited tomcat6/server.xml so that the Host container has: appBase="/dbase/webapps" I have an apache virtual host "mysite.edu" that hooks up to tomcat via mod_jk with the key vhost config line being: JkMount /* worker1ajp13 But at this point, I have to use my site via a url like: "https://mysite.edu/xmlui";. Without the xmlui (or jspui), I just get a tomcat 404 (resource not available). Is it possible to instead have "https://mysite.edu"; point directly at our dspace software, have links on pages look good to users (in other words, they shouldn't see "xmlui" either) and not break the other "subapps" I find in the webapps directory ( lni, oai, solr, sword)? If so, how is this most easily done? Currently, I have: dspace.hostname = mysite.edu dspace.baseUrl = http://mysite.edu:8080 dspace.url = ${dspcae.baseUrl}/xmlui I'm iffy on the baseUrl setting becausej it's pointing to a tomcat port directly, but maybe that's what it's supposed to be? We are eventually going to firewall 8080 so that only apache running on the same host will be able to talk to it. I sort of thought that setting dspace.url with xmlui would do what I wanted. The docs: "URL that determines whether JSPUI or XMLUI will be loaded by default. Include port number etc., but NOT trailing slash. Change to /xmlui if you wish to use the xmlui (Manakin) as the default.." But what, really does that mean? Thanks for any ideas. -glenn ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
