Hi Thomas,
The route I would go is to have a distinct tomcat instance for each
client/instance. You can restart one tomcat with affecting the other.
(Assuming you've got ample memory on your boxes). And you'll need to tweak
those instances so they run on distinct ports. (Multiple tomcats can't each
claim 8080, 8443, 8009)
So: /var/tomcat-dspace-4-earth and /var/tomcat-dspace4-moon
Then you'll have to change server.port, connector.port,
connector.redirectport, http, https, and AJP.
You'll need to configure your web server (apache / nginx) to then route the
vhost properly. Let's see, postgres should be fine, have distinct dbnames,
or if you have an external db server, that is likely already the case.
Also, you'll need to change some DSpace configs, especially with SOLR for
the other instances to not run on 8080. If you use ElasticSearch, ensure
that you give a unique index name for each instance.
________________
Peter Dietz
Longsight
www.longsight.com
[email protected]
p: 740-599-5005 x809
On Wed, Oct 8, 2014 at 10:32 AM, Adan Roman <[email protected]> wrote:
> Hi all
>
> It can be done as Thomas say, but is not recommended in production systems
> .
> Any problems that hang tomcat will prevent access to all applications it
> contains, and maintenance is more complicated, stops will halt all
> applications and start and stop times will be higher.
>
> regards
>
> Hi Thomas,
>
> You can run multiple DSpace’s on one server. Are you using Tomcat as a
> web server?
>
> We did this previously on our server by installing the different DSpaces
> in different directories, with different assetstores and different database
> schema names. We then configured tomcat to run more than one web
> application with different hostnames. You do this within the
> tomcat/conf/server.xml to point to different directories on the server.
> With a context path for each web app within the individual DSpace. We used
> apache to forward all requests on port 80 to 8080 e.g.
>
>
> <Host name=“www.testdspace1.com" appBase="webapps"
> unpackWARs="true" autoDeploy="true">
>
> <!-- Access log processes all example.
> Documentation at: /docs/config/valve.html
> Note: The pattern used is equivalent to using
> pattern="common" -->
> <Valve className="org.apache.catalina.valves.AccessLogValve"
> directory="logs"
> prefix=“localhost_dspace1_access_log." suffix=".txt"
> pattern="%h %l %u %t "%r" %s %b" />
>
> <Context path="/solr"
> docBase="/Users/dspace/dspace1/webapps/solr" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
> <Context path="/" docBase="/Users/dspace/dspace1/webapps/jspui"
> reloadable="true" cachingAllowed="false" allowLinking="true"/>
> <Context path="/sword"
> docBase="/Users/dspace/dspace1/webapps/sword" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
>
> </Host>
>
> <Host name=“www.testdspace2.com" appBase="webapps"
> unpackWARs="true" autoDeploy="true">
>
> <!-- Access log processes all example.
> Documentation at: /docs/config/valve.html
> Note: The pattern used is equivalent to using
> pattern="common" -->
> <Valve className="org.apache.catalina.valves.AccessLogValve"
> directory="logs"
> prefix="localhost_dspace2_access_log." suffix=".txt"
> pattern="%h %l %u %t "%r" %s %b" />
>
> <Context path="/solr"
> docBase="/Users/dspace/dspace2/webapps/solr" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
> <Context path="/" docBase="/Users/dspace/dspace2/webapps/jspui"
> reloadable="true" cachingAllowed="false" allowLinking="true"/>
> <Context path="/sword"
> docBase="/Users/dspace/dspace2/webapps/sword" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
>
> </Host>
>
> Or if you just want to do this in a local dev environment you can have
> lots of contexts under localhost (this is what I do on my dev pc) e.g.
>
> <Host name="localhost" appBase="webapps"
> unpackWARs="true" autoDeploy="true">
>
> <Context path=“/dspace1/solr"
> docBase="/Users/dspace/dspace1/webapps/solr" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
> <Context path=“/dspace1"
> docBase="/Users/dspace/dspace1/webapps/jspui" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
> <Context path=“/dspace1/sword"
> docBase="/Users/dspace/dspace1/webapps/sword" reloadable="true"
> cachingAllowed="false" allowLinking="true”/>
> <Context path="/dspace2/solr"
> docBase="/Users/dspace/dspace2/webapps/solr" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
> <Context path="/dspace2"
> docBase="/Users/dspace/dspace2/webapps/jspui" reloadable="true"
> cachingAllowed="false" allowLinking="true"/>
> <Context path=“/dspace2/sword"
> docBase="/Users/dspace/dspace2/webapps/sword" reloadable="true"
> cachingAllowed="false" allowLinking="true”/>
>
> </Host>
>
>
> You can then see the Dspace on http://localhost:8080/dspace1 You may
> need to increase the startup parameters for Tomcat if it starts running out
> of memory. Tomcat can also get slow to start-up if you have a lot of
> webapps.
>
> Cheers,
>
> Claire
>
> --
> Claire Knowles
> Library Digital Development Manager
> Library and University Collections, Information Services
> University of Edinburgh
>
>
>
> From: <Avino>, "Thomas W. [LITES] (LARC-B702)" <[email protected]>
> Date: Wednesday, 8 October 2014 13:01
> To: dspace-tech <[email protected]>
> Subject: [Dspace-tech] Running 2 different Dspace instances on 1 server
>
> Is it possible to create a new Dspace instance onto an existing
> server? This would be a completely different Dspace application, not just
> a copy.
>
> We have 5 different Dspace library applications running and I don’t want
> to setup a new machine. I have a development box, and I want to install 2
> different Dspace’s. Is this possible, and how?
>
>
>
> Thank you!
>
>
>
> Thomas W. Avino
>
> [image:
> http://t3.gstatic.com/images?q=tbn:ANd9GcRnrGOajbLG51OH18dELWjFdU65XUjF7Rb1nhkW034bbGRqm9BoQU4IlnV-]
>
> *NASA Langley Research Center*
>
> Bldg 1194 Room 302B
>
> Mail Stop 185
>
> Hampton, VA 23681-2199
>
> Phone: (757) 864-8495
>
> Fax: (757) 864-6649
>
>
>
>
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog
> Analyzerhttp://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
>
>
>
> _______________________________________________
> DSpace-tech mailing
> [email protected]https://lists.sourceforge.net/lists/listinfo/dspace-tech
> List Etiquette:
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
> --
>
>
>
> ------------------------------
> <http://www.avast.com/>
>
> Este mensaje no contiene virus ni malware porque la protección de avast!
> Antivirus <http://www.avast.com/> está activa.
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
>
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&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
>
------------------------------------------------------------------------------
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
http://pubads.g.doubleclick.net/gampad/clk?id=154622311&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
