Page History

...

Code Block
cd /home/dspace/.m2/repository/org/apache/maven/plugins/maven-site-plugin/

From [http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin|http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-site-plugin] get 2.0-beta-6/maven-site-plugin-2.0-beta-6.jarand get maven-metadata.xmlbut rename maven-metadata.xml as maven-metadata-central.xml and choose the site-plugin version that works best.

...

see 5.1.1. of 1.6.2 DSpace Manual for description of elements in dspace.cfg
compare the default values in ./dspace.cfg with mappings defined in ../pom.xml
dspace.dir = /usr/local/dspace
dspace.url = set
# dspace.hostname = set as `hostname --fqdn`#
dspace.name = Training DSpace at Library of Nineveh #
db.name = postgres
# db.username = set to postgresql createdb credentials#
db.password = as above#
mail.server = localhost
# mail.from.address = set#
feedback.recipient = set
# mail.admin = set#
alert.recipient = set
# registration.notify = set#
default.locale = set

# default.language = set

Code Block

 cd /home/dspace/src/LATEST/dspace
 mvn clean package > /var/tmp/mvn_clean_package_log 2>&1

 # to view progress, at another terminal window, use
 tail /var/tmp/mvn_clean_package_log

 # at this stage, if there are warnings about missing environment variables
 # you should refer to the section on setting environment variables above

 # on completion, you should see

[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7 minutes 48 seconds
[INFO] Finished at: Mon Jan 12 12:35:07 EST 2009
[INFO] Final Memory: 23M/51M
[INFO] ------------------------------------------------------------------------

 # if the target directory does not exist
 # go through the mvn_clean_package_log and look for
 # any lines with the word 'missing'
 # a network resource could have been unreachable

 cd /home/dspace/src/LATEST/dspace/target/dspace-1.5.1-build.dir

 # to initialise and install the database and DSpace
 ant fresh_install

 # to create the administrator account
 cd /usr/local/dspace/bin
 ls -l create-administrator
  -rwxrw-r-- 1 dspace dspace 2121 Jan 13 15:45 create-administrator
 ./create-administrator

 # you then see ...
  Creating an initial administrator account
  E-mail address: [change]
  First name: [set]
  Last name: [set]
  WARNING: Password will appear on-screen.
  Password:
  Again to confirm:
  Is the above data correct? (y or n): y
  Administrator account created

Later, after making new changes to dspace.cfg, apply its settings across applications
by the ant init_configs or install_configs methods, described below, and you
may need to restart services such as tomcat5 for the settings to really apply

...

See 5.1.1. of 1.6.2. Dspace Manual

Code Block

## in the build target directory, to expose the ant switches

$ ant -p
Buildfile: build.xml

====================== DSpace platform build file ======================

Common usage:

  Fresh install, including database setup and registry loading:
    % ant fresh_install

  Update existing installation, leaving data and configuration intact:
    % ant -Dconfig=/installdir/config/dspace.cfg update

========================================================================

Main targets:

 build_webapps_wars  Compress Web Applications into .war files
 clean_database      Removes DSpace database tables, destroying data
 fresh_install       Do a fresh install of the system, overwriting any data
 load_registries     Load initial contents of registries
 setup_database      Create database tables
 update              Update installed code and web applications (without clobber
ing data/config)
 update_code         Update installed code (without clobbering data/config)
 update_webapps      Update Web Applications (without clobbering data/config)
Default target: help

Code Block

 when you change DS_SRC/LATEST/dspace/config/dspace.cfg
 go to DS_SRC/LATEST/dspace/target/dspace-X.Y.Z-build.dir and
 run '''ant init_configs''' for settings to apply

 when you change DS_DST/config/dspace.cfg
 run DS_DST/bin/install_configs for settings to apply

 for settings to apply across applications you may need
 to restart processes such as tomcat5

Replace the javamail.jar file

After you have installed DSpace, one RHEL-provided jar needs to be manually swapped to the one provided by DSpace. If you do not, you will see "javax.mail.NoSuchProviderException" error messages whenever you attempt to send mail from DSpace:

Code Block


cd /var/lib/tomcat5/common/lib/ && sudo rm [javamail].jar
sudo alternatives --install /usr/share/java/javamail.jar javamail /dspace/webapps/xmlui/WEB-INF/lib/mail-1.4.jar 4289
sudo alternatives --config javamail

Connect Tomcat5 and DSpace then TEST

...

To install the JAI components, download the Java Advanced Imaging API (jre version) and the Java Advanced Imaging - Image I/O Tools from [http://java.sun.com/products/java-media/jai/current.html|http://java.sun.com/products/java-media/jai/current.html].

...

download the zip file eg: I used a stable daily build such as: [http://download.java.net/media/jai-imageio/builds/daily/2008-09-02/jai-imageio-1_2-pre-dr-b04-lib-linux-i586-02_Sep_2008.zip|http://download.java.net/media/jai-imageio/builds/daily/2008-09-02/jai-imageio-1_2-pre-dr-b04-lib-linux-i586-02_Sep_2008.zip]*
unzip the I/O tools zip archive
* copy both of the extracted files (clibwrapper_jiio.jar and jai_imageio.jar) from lib/ext to your $JRE_HOME/lib/ext directory

...

Page tree

Versions Compared

Old Version 4

New Version Current

Key

Replace the javamail.jar file

Connect Tomcat5 and DSpace then TEST