[Dspace-general] Multiple instances of DSpace?

Richard Jones richard.jones at ub.uib.no
Thu Nov 17 10:45:49 EST 2005


Hi,

(not quite sure which list this originated from, so apologies for the
cross posting)

> The only way I know to pull this off is to run a new instance of
> Tomcat for each dspace you need.

I don't think it's that difficult.  You need a separate database for
each instance.  e.g.

dspace-1
dspace-2
dspace-3

and a separate config for each instance

dspace-1.cfg
dspace-2.cfg
dspace-3.cfg

and separate install directories:

/srv/dspace-1
/srv/dspace-2
/srv/dspace-3

now run the fresh_install target of ant with each of the relevant config
files:

ant -Dconfig=/path/to/dspace-x.cfg fresh_install

this should put all the code in /srv/dspace-x and the dspace.war and
dspace-oai.war in the build directory, and the data in the dspace-x
database.

Now just stick the war files in the [tomcat]/webapps directory as, for
example, dspace-x.war and dspace-x-oai.war

The thing to be careful of, if building from the same source tree is
that you empty [dspace-source]/build in between each fresh_install (or
update), else you might have problems with the web.xml file.

Anyway, do this for your 3 instances, so you should have 3 separate
dspace-x.war and dspace-x-oai.war files in your webapps directory.
Restart tomcat and you should be able to get them at:

http://my.dspace.edu:8080/dspace-x

Since they are now effectively entirely separate applications, there
shouldn't be any cross over between config or data if the original
configurations for each one are correct.

I tend to do this with different source trees, as I mostly run different
versions in parallel, and I have never had any problems; let me know if
there are any gotchas that I've missed.

>   If you using modjk with Apache to talk to Tomcat then you can just
> assign each instance of modjk to a new port.  You then can use one URL
> and just map each instance like so:
> my.dspace.edu/dspace1
> my.dspace.edu/dspace2
> 
> If you are just using Tomcat you can simple bind each instance to a
> new port like so:
> 
> my.dspace.edu:8080 (dspace1)
> my.dspace.edu:8081 (dspace2)
> 
> If you would like more information on how to do this please let me
> know and I can send you some documentation.
> 
> Cody
> 
> On 11/14/05, bryce benton <brycebenton at gmail.com> wrote:
>         I'm attempting to install multiple instances of DSpace on the
>         same
>         machine. I've followed the instructions for setting up dspace,
>         but
>         I've used the user dspace2, dspace3 and created databases
>         named
>         similarly.
>         
>         Everything works fine in the build process, but when I visit
>         the URL,
>         I see that the new DSpace instance is reading from the
>         original DSpace
>         database.
>         
>         Additionally, it seems that the new DSpace instances are
>         getting their 
>         configuration data from the original dspace.cfg file. Doing
>         /dspace/bin/install-configs updates all 3 installations,
>         whereas
>         /dspace2/bin/install-configs has no effect.
>         
>         Is it possible to run more than one instance of DSpace on the
>         same 
>         machine? If so, how do I connect the new installations to the
>         proper
>         databases and configuration files? It seems there's a crucial
>         step
>         that I'm missing.

Cheers,

-- 
Richard
-------
Richard Jones                    |
Overingeniør                     | Senior Engineer
Universitetsbiblioteket i Bergen | University of Bergen Library

e: richard.jones at ub.uib.no
t: +47 55 58 25 37

BORA: http://bora.uib.no/




More information about the Dspace-general mailing list