Hi Helix84,
Thank you very much for your answer, and have much success on DSpace!

I forgot to say that:
- www.ourDomain.mainDomain.edu is under IP x.y.z.w and have a specific
content
- our DSpace installation is under IP a.b.c.d,

- tomcat defines default path to xmlui and declares oai, jspui, and so on
in docBase
- tomcat is running on port 80 following the steps here:

http://thelowedown.wordpress.com/2010/08/17/tomcat-6-binding-to-a-privileged-port-on-debianubuntu/

then, if we call http://a.b.c.d we receive our dspace installation in xmlui.
But, my brain doesn't get to visualize what is Tomcat configuration and
what is dspace configuration, or even ourDomain configuration to call
http://x.y.z.w/friendlyNameForOurDSpaceApplication
and receive the content of http://a.b.c.d

Where I declare the directory? Like a virtual host on Tomcat?
But, the test below didn't work:
         <Host name="www.ourDomain.mainDomain.edu"   unpackWARs="true"
autoDeploy="true"
                            xmlValidation="false" xmlNamespaceAware="false"
appBase="/dspace/webapps">
<!-- Trying aliases -->
<Alias>ourDomain.mainDomain.edu <http://www.ourDomain.mainDomain.edu>
</Alias>
<Alias>ourDomain.mainDomain.edu <http://www.ourDomain.mainDomain.edu>/
friendlyNameForOurDSpaceApplication</Alias>

<!-- Define a new context path for all DSpace web apps -->
[...]
</Host>

Can you help to clear my mind?

Thanks in advance,
Josi Pérez



2012/6/14 helix84 <[email protected]>

> On Wed, Jun 13, 2012 at 7:06 PM, Josefina Perez Alvarez
> <[email protected]> wrote:
> > We use our dspace test by ip and now we are planning change to an URL
> like
> > www.ourDomain.mainDomain.edu/dspaceX
>
> Hi Josi,
> if your Tomcat is listening directly on port 80, your dspace.cfg
> should look like this:
>
> dspace.hostname = www.ourDomain.mainDomain.edu
> dspace.baseUrl = http://www.ourDomain.mainDomain.edu
> dspace.url = http://www.ourDomain.mainDomain.edu/dspaceX
>
> But it's more likely that you have Apache HTTPD in front of Tomcat, in
> that case you should have the port Tomcat is listening on in
> dspace.cfg:
>
> dspace.hostname = www.ourDomain.mainDomain.edu
> dspace.baseUrl = http://www.ourDomain.mainDomain.edu:8080
> dspace.url = http://www.ourDomain.mainDomain.edu:8080/dspaceX
>
> > We don't have access to define mainDomain, but we have contact with the
> > administrators from ourDomain.
> > The initial configuration failed because the URL above stayed fixed and
> we
> > lost the handle when navigating by itens.
>
> Your local handle server is usually referred to by IP, so unless also
> your IP changed, this shouldn't break. If the IP changed, all that
> should be necessary is to change all instances of "bind_address" in
> your config.dct to the new IP and restart your handle server (if I
> remember correctly).
>
> 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

Reply via email to