Thank you João Melo and Helix84.
Sorry, I was so confused that can't even explain the problem correctly.
Yes João Melo, that is my problem: there is a well specified domain (
www.ourDomain.mainDomain.edu) in one machine with IP x.y.z.w, and should to
continue so; now, we developped a DSpace repository in another machine,
with IP a.b.c.d, and this appplication should answer on the URL
www.ourDomain.mainDomain.edu//friendlyNameForOurDSpaceApplication<http://x.y.z.w/friendlyNameForOurDSpaceApplication>
keeping both machines working.
I will read about the new concepts (for me) and try to implement a solution.
Thank you both,
Josi Perez
2012/6/16 helix84 <[email protected]>
> On Sat, Jun 16, 2012 at 5:06 AM, João Melo <[email protected]> wrote:
> > sorry for the intromission, i think the problem isn't related with the
> > tomcat neither with DSpace on a.b.c.d. As Josefina stated, DSpace
> > successfully answers requests on IP a.b.c.d (xmlui interface).
> >
> > If a.b.c.d differs from x.y.z.w, i assume that there are two different
> > machines (am i correct?)
> >
> > If Josefina wants to access to DSpace using
> > x.y.z.w/friendlyNameForOurDSpaceApplication it must now look at the
> server
> > listening on ip x.y.z.w and somehow establish a 'bridge' to the a.b.c.d,
> i
> > would say that Josefina must contact the administrator of the
> > domain www.ourDomain.mainDomain.edu and request for this 'brigde'.
> >
> > For this purpose, it would be good to have an apache server at x.y.z.w,
> if
> > so, there are many ways of achieving this goal, proxypass (need another
> > apache on a.b.c.d), mod_rewrite or (the solution i would recommend)
> mod_jk.
> >
> > Hope this helps.
> >
> > PS - Congratulations Helix84
>
> Oh, the whole time I was thinking we're talking about migration of
> DSpace from a.b.c.d to x.y.z.w.
>
> So you want to keep DSpace on a.b.c.d and only make make x.y.z.w a
> reverse proxy? Like João said, there are multiple ways to achieve
> that, all of them should be described on
> <https://wiki.duraspace.org/display/DSPACE/DspaceOnStandardPorts>.
>
> The one I recommend is via mod_proxy_ajp. Make sure to define an AJP
> connector in Tomcat's server.xml:
> <Connector port="8009" protocol="AJP/1.3" redirectPort="8443"
> URIEncoding="UTF-8" />
>
> dspace.cfg should be fine like I told you:
> dspace.hostname = www.ourDomain.mainDomain.edu
> dspace.baseUrl = http://www.ourDomain.mainDomain.edu
> dspace.url =
> http://www.ourDomain.mainDomain.edu/friendlyNameForOurDSpaceApplication
>
> Restart Tomcat and run "netstat -tulpn | grep 8009" to make sure AJP
> is listening on all interfaces, not just localhost (ou should see
> :::8009 or 0.0.0.0:8009, not 127.0.0.1:8009).
>
> On the machine with Apache, configure the other end of the AJP connection:
> ProxyPass /friendlyNameForOurDSpaceApplication ajp://a.b.c.d:8009/
> ProxyPassReverse /friendlyNameForOurDSpaceApplication ajp://a.b.c.d:8009/
>
> 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
