[Dspace-tech] dspace migration
Hi All, I inherited a Dspace setup, I don't have much background with Dspace (or apache tomcat for that matter) and was wondering if anyone could help me with a few issues that I am running into. What I would like to do is just copy the existing dspace directories over to the new server. I am trying to migrate our existing Dspace server from windows to a linux server. It looks like there are 2 dspace directories one is in the tomcat webapps directory named dspace. The other is named dspace-1.4.1, it contains a config directory with the dspace.cfg. So my questions are: 1) Are those the only 2 directories I need to worry about? 2) I assume I put the directory that is in the webapp folder, in the webapp folder on the new server. But where do I place the other directory how do I make tomcat aware of it. Any help would be appreciated, --Brian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace migration
Stuart Lewis wrote: So my questions are: 1) Are those the only 2 directories I need to worry about? No. There is one more. When you read DSpace documentation, you'll often see references to [dspace] and [dspace-src]: - [dspace] is where DSpace gets installed, holds the configuration, logs, item files etc. - [dspace-src] is where DSpace is downloaded to, and then built. It will also contain your local customisations if you have any. When it builds, it creates [dspace], and a dspace.war file which when placed in [tomcat]/webapps will expand to create the [tomcat]/webapps/dspace directory containing the web application. Your folder called dspace-1.4.1 may be either [dspace] or [dspace-src] [dspace] contains directories such as assetstore, log, and upload. [dspace-src] contains directories such as src, jsp, docs. So you have two of the three required. In theory you can recreate the tomcat/webapps/dspace folder easily from [dspace-src]. 2) I assume I put the directory that is in the webapp folder, in the webapp folder on the new server. But where do I place the other directory how do I make tomcat aware of it. If you just place the 'dspace' directory in the tomcat webapps folder, like where you got it from, then restart tomcat, it should recognise that it is there. You've not mentioned the database at all. Are you happy with how that is configured, and copying that too (if it is a local database server)? Ok both of these responses really helped thank you. The directories that I am going to move are: ..\webapps\dspace ..\dspace-1.4.1 ..\dspace-1.4.1-source in the webapps\dspace directory there is a file WEB-INF\web.xml I am going to modify that file with path to the new location of the dspace-1.4.1\config\dspace.cfg As far as the database it is running on a different host on the same vlan so I don't think anything should change there. Thanks for the help, if I have missed anything let me know. --Brian - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace migration
Hi Brian, Ok both of these responses really helped thank you. The directories that I am going to move are: ..\webapps\dspace ..\dspace-1.4.1 ..\dspace-1.4.1-source in the webapps\dspace directory there is a file WEB-INF\web.xml I am going to modify that file with path to the new location of the dspace-1.4.1\config\dspace.cfg As far as the database it is running on a different host on the same vlan so I don't think anything should change there. That all sounds good. Thanks for the help, if I have missed anything let me know. Are you running a handle server? If so, I'll email instructions for moving that too. If you're not sure, look in [dspace]/config/dspace.cfg for 'handle.prefix', and see if it set to 123456789. If is is set to something different, then you will be running a handle server. Thanks, Stuart _ Gwasanaethau Gwybodaeth Information Services Prifysgol Aberystwyth Aberystwyth University E-bost / E-mail: [EMAIL PROTECTED] Ffon / Tel: (01970) 622860 _ - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] dspace migration
Hi Gregory,
just to be on the save side, check the setting in the
[dspace]/config/dpace.cfg
The directories where DSpace is installed and keeps it's non-db data are
defined there.
Check for:
dspace.dir (the installation directory)
assetstore.dir = ${dspace.dir}/assetstore
history.dir = ${dspace.dir}/history
log.dir = ${dspace.dir}/log
upload.temp.dir = ${dspace.dir}/upload
search.dir = ${dspace.dir}/search
report.dir = ${dspace.dir}/reports/
handle.dir = ${dspace.dir}/handle-server
There might be other directory defined for the assetstore. It's common
practice to seperate the installation directory from the data directory.
Hope that helps
Claudia Jürgen
Ok both of these responses really helped thank you. The directories that
I am going to move are:
..\webapps\dspace
..\dspace-1.4.1
..\dspace-1.4.1-source
in the webapps\dspace directory there is a file WEB-INF\web.xml I am going
to modify that file with path to the new
location of the dspace-1.4.1\config\dspace.cfg
As far as the database it is running on a different host on the same vlan
so I don't think anything should change there.
Thanks for the help, if I have missed anything let me know.
--Brian
-
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK win great
prizes
Grand prize is a trip for two to an Open Source event anywhere in the
world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Error when uploading bitstreams
Hello everyone, I hate having to post an error message here, hoping that someone can help me, but I'm clueless on this one. Our DSpace was working fine, but now, every time someone tries to upload a bitstream we get the error message. Can anyone at least point out what I should be looking at? Is there some problem with the path where the bitstreams are stored? Thank you very much. java.io.IOException: No such file or directory at java.io.UnixFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:883) at edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486) at org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamStorageManager.java:332) at org.dspace.content.Bitstream.create(Bitstream.java:194) at org.dspace.content.Bundle.createBitstream(Bundle.java:375) at org.dspace.app.xmlui.aspect.administrative.FlowItemUtils.processAddBitstream(FlowItemUtils.java:399) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:230) at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244) at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:1134) at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:190) at org.mozilla.javascript.continuations.ContinuationInterpreter.interpret(ContinuationInterpreter.java:138) at org.mozilla.javascript.continuations.InterpretedFunctionImpl.call(InterpretedFunctionImpl.java:121) at org.mozilla.javascript.ScriptRuntime.call(ScriptRuntime.java:1244) at org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1591) at org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:852) at org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:123) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:107) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.PreparableMatchNode.invoke(PreparableMatchNode.java:130) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:116) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:234) at org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:192) at org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:265) at org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:110) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:102) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:46) at org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:107) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:142) at org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:68) at org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:92) at
