Difference between revisions of "SUNScholar/DSpace"
| Line 19: | Line 19: | ||
# Change ALL instances of the default "dspace" username to another username, except for the main Ubuntu "dspace" account created during the server installation. | # Change ALL instances of the default "dspace" username to another username, except for the main Ubuntu "dspace" account created during the server installation. | ||
| − | You have been warned ! | + | '''You have been warned !''' |
| + | |||
| + | {{SS-GRAPHS}} | ||
'''[[SUNScholar/Practical_guidelines_for_starting_an_institutional_repository_(IR)|Back to Guidelines]]''' | '''[[SUNScholar/Practical_guidelines_for_starting_an_institutional_repository_(IR)|Back to Guidelines]]''' | ||
| − | |||
| − | |||
__NOTOC__ | __NOTOC__ | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
Revision as of 02:10, 8 September 2012
The following wiki pages describe the procedures to install a "vanilla" DSpace version 1.7.2 instance using an Ubuntu 10.04 LTS server as we did for our SUNScholar server.
Please click here to find out why Ubuntu was selected as the server platform.
If you intend to use these wiki pages for an installation workshop on your campus, then make sure each computer and server has open and unrestricted access to the internet.
We are currently investigating using cloud services to provision repository systems. Click here to find out how the investigation is going.
It is essential that you follow the procedures step-by-step !
Procedure 1: Install Ubuntu
Procedure 2: Prepare Ubuntu
Procedure 3: Install DSpace
Warning:
If you use the above procedures to setup a production machine open to the Internet, then ensure the following.
- Change ALL instances of the default "dspace" password to a very secure secret password.
- Change ALL instances of the default "dspace" username to another username, except for the main Ubuntu "dspace" account created during the server installation.
You have been warned !
|
All our tweaks and optimisations seem to be working. The load dropped when we started using "authbind" for Tomcat thereby eliminating the need for the Apache "mod_jk" module, which was creating extra processing overhead.
|
Looks like we have enough disk space in the /home partition for the next 3yrs at least, at our current rate of submissions. The /var partition which holds the database was reduced in size by tweaking the bitstream checker properties and then running a full database vacuum.
|
|
We have more than enough compute muscle.
|
Our memory usage stabilised when we stopped using the JSPUI. However after the upgrade to DSpace 1.8.2 and enabling discovery we are back to a memory intensive system.
|
Back to Guidelines
