Difference between revisions of "SUNScholar/Prepare Ubuntu"

From Libopedia
Jump to navigation Jump to search
Line 5: Line 5:
 
*'''<font color="red">It is essential that you have first completed the [[SUNScholar/Install_Ubuntu|installation of Ubuntu]]. If you have not, please do so now.</font>'''
 
*'''<font color="red">It is essential that you have first completed the [[SUNScholar/Install_Ubuntu|installation of Ubuntu]]. If you have not, please do so now.</font>'''
 
----
 
----
== [[SUNScholar/Install_Ubuntu|Previous Procedure]]==
 
 
==[[SUNScholar/Prepare Ubuntu/S01|Step 1. Login to the remote server]]==
 
==[[SUNScholar/Prepare Ubuntu/S01|Step 1. Login to the remote server]]==
 
==[[SUNScholar/Prepare Ubuntu/S02|Step 2. Become the "root" user]]==
 
==[[SUNScholar/Prepare Ubuntu/S02|Step 2. Become the "root" user]]==
Line 15: Line 14:
 
==[[SUNScholar/Prepare Ubuntu/S08|Step 8. Setup the environment variables]]==
 
==[[SUNScholar/Prepare Ubuntu/S08|Step 8. Setup the environment variables]]==
 
==[[SUNScholar/Prepare Ubuntu/S09|Step 9. Check the installation]]==
 
==[[SUNScholar/Prepare Ubuntu/S09|Step 9. Check the installation]]==
 +
==[[SUNScholar/Install_Ubuntu|Previous Procedure]]==
 
==[[SUNScholar/Install_Dspace|Next Procedure]]==
 
==[[SUNScholar/Install_Dspace|Next Procedure]]==
  

Revision as of 15:31, 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


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

Previous Procedure

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.

Sunscholar-load-year.png

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.

Sunscholar-disk-usage-year.png

We have more than enough compute muscle.

Sunscholar-cpu-year.png

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.

Sunscholar-memory-year.png

Back to DSpace