Difference between revisions of "SUNScholar/Prepare Ubuntu"
| Line 16: | Line 16: | ||
==[[SUNScholar/Prepare Ubuntu/S09|Step 9. Check the installation]]== | ==[[SUNScholar/Prepare Ubuntu/S09|Step 9. Check the installation]]== | ||
==[[SUNScholar/Install_Dspace|Next Procedure]]== | ==[[SUNScholar/Install_Dspace|Next Procedure]]== | ||
| + | |||
| + | {{SS-GRAPHS}} | ||
'''[[SUNScholar/Dspace|Back to DSpace]]''' | '''[[SUNScholar/Dspace|Back to DSpace]]''' | ||
| − | |||
| − | |||
__NOTOC__ | __NOTOC__ | ||
__NOEDITSECTION__ | __NOEDITSECTION__ | ||
Revision as of 15:30, 15 September 2012
Introduction
Before DSpace can be installed and setup we have to prepare the server with the software needed by DSpace.
- Print this page and manually tick off the steps as you complete them.
Requirements
- It is essential that you have first completed the installation of Ubuntu. If you have not, please do so now.
Previous Procedure
Step 1. Login to the remote server
Step 2. Become the "root" user
Step 3. Install Java Software Dependencies
Step 4. Setup Maven Java Installer
Step 5. Setup Tomcat Java Webapp Server
Step 6. Install PostgreSQL
Step 7. Setup the Postfix mail server
Step 8. Setup the environment variables
Step 9. Check the installation
Next Procedure
|
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 DSpace
