Hi Charlene,
are you doing this setup for test/development purposes or for actual
production usage?
We generally advise against deploying multiple DSpaces in the same Tomcat
because:
- If you need to update or restart one of your DSpaces, you will often need
to restart your entire tomcat. In this setup, it would mean that an update
to one DSpace will also bring down & restart the other DSpace as well.
- When you experience performance issues, it becomes much harder to debug &
find the culprit when running 2 dspaces in the same tomcat.
This could also be the reason why documentation on this kind of setup is
scarce.
As an alternative, you could run 2 tomcats and deploy them on different
ports.
best regards,
Bram
--
[image: logo]
*Bram Luyten* *@mire*
*2888 Loker Avenue East, Suite 315, Carlsbad, CA. 92010*
*Esperantolaan 4, Heverlee 3001, Belgium*
www.atmire.com<http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=braml>
On Thu, Dec 12, 2013 at 4:27 AM, Charlene Chinda Barina <[email protected]>wrote:
> For posterity's sake, here's what I ended up doing to make this work - I
> edited the server.xml file for Tomcat to look something like this:
>
> Right before </Host> I put these two lines:
>
> <Context path="/instance1" docBase="/dspace/instance1/webapps/xmlui"
> allowLinking="true"/>
> <Context path="/instance2" docBase="/dspace/instance2/webapps/xmlui"
> allowLinking="true"/>
>
> And as a result when I go to http://mydomain/instance1 xmlui version for
> instance1 loads up, and same situation for http://mydomain/instance2.
>
> I didn't have to change any URLs in dspace config files, but I'm getting
> incorrect password reset links and all, so I may reconfirm that for later.
>
> --Charlene
>
>
> On Wed, Dec 11, 2013 at 10:15 AM, Charlene Chinda Barina
> <[email protected]>wrote:
>
>> Hi all,
>>
>> A question about multiple DSpace instances. I looked through the
>> documentation and there's a bit - but from a 1.8 release and referring to
>> .war files, which doesn't seem to be applicable to the default situation of
>> uncompressed directories for 3.2.
>>
>> What I have is:
>>
>> 1. Two separate source directories, which I'm building separately for
>> each instance.
>> 2. Two separate databases, with their separate users
>> 3. The install directory being subdirectories for each under /dspace,
>> e.g., /dspace/instance1 and /dspace/instance2
>> 4. dspace.install.dir being set to these subdirectories for each
>> source directory in build.properties.
>> 5. In tomcat (/usr/share/tomcat7/conf/Catalina/localhost/instance2,
>> for example) I have a instance2.xml file that has this:
>> <?xml version="1.0" encoding="UTF-8"?>
>> <Context docBase="/dspace/instance2/webapps" path="/instance2" />
>>
>> Every things to build and install/update fine, but I can't see anything
>> when loading under http://localhost/instance2 or
>> http://localhost/instance2/xmlui.
>>
>> Things I'm not sure about:
>>
>> 1. Not sure what to set dspace.baseURL to be in this situation in
>> build.properties and what dspace.url should be in dspace.cfg.
>> 2. If I've set up tomcat properly to look in the right places when
>> going to that URL in regards to webapps.
>> 3. Something else I'm completely unaware of
>>
>> Appreciate any guidance in this, and I'll happily update documentation on
>> the DSpace site once I can make sure it's working...
>>
>> Thanks,
>> Charlene
>>
>> 1. Set the Dspace.install.dir to be
>>
>> --
>> Charlene Barina, MPH
>> Research Analyst 2, U.S. IMPACT Study
>> The Information School
>> 303-359-6347 | Skype: cbarina
>> facebook.com/ImpactSurvey | twitter.com/impactsurvey
>>
>
>
>
> --
> Charlene Barina, MPH
> Research Analyst 2, U.S. IMPACT Study
> The Information School
> 303-359-6347 | Skype: cbarina
> facebook.com/ImpactSurvey | twitter.com/impactsurvey
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics
> Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette