Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Relational Database: (PostgreSQL or Oracle).

  • PostgreSQL 8.2 3 to 8.4 PostgreSQL can be downloaded from the following location: http://www.postgresql.org/ . It is highly recommended that you try to work with Postgres 8.4 or greater, however, 8.2 3 or greater should still work. Unicode (specifically UTF-8) support must be enabled. This is enabled by default in 8.0+. Once installed, you need to enable TCP/IP connections (DSpace uses JDBC). In postgresql.conf: uncomment the line starting: listen_addresses = 'localhost'. Then tighten up security a bit by editing pg_hba.conf and adding this line: host dspace dspace 127.0.0.1 255.255.255.255 md5. Then restart PostgreSQL.
  • Oracle 10g or greater Details on acquiring Oracle can be downloaded from the following location: http://www.oracle.com/database/. You will need to create a database for DSpace. Make sure that the character set is one of the Unicode character sets. DSpace uses UTF-8 natively, and it is suggested that the Oracle database use the same character set. You will also need to create a user account for DSpace (e.g. dspace) and ensure that it has permissions to add and remove tables in the database. Refer to the Quick Installation for more details.
    • NOTE: DSpace uses sequences to generate unique object IDs — beware Oracle sequences, which are said to lose their values when doing a database export/import, say restoring from a backup. Be sure to run the script etc/update-sequences.sql.
    • For people interested in switching from Postgres to Oracle, I know of no tools that would do this automatically. You will need to recreate the community, collection, and eperson structure in the Oracle system, and then use the item export and import tools to move your content over.

...

  1. Download the DSpace source from SourceForge and unzip it (WinZip will do this)
  2. Ensure the PostgreSQL service is running, and then run pgAdmin III (Start -> PostgreSQL 8.0 -> pgAdmin III). Connect to the local database as the postgres user and:
    • Create a 'Login Role' (user) called dspace with the password dspace
    • Create a database called dspace owned by the user dspace, with UTF-8 encoding
  3. Wiki Markup
    Update paths in _\[dspace-source\]\dspace\config\dspace.cfg_
    • Note: Use forward slashes / for path separators, though you can still use drive letters, e.g.: dspace.dir = C:/DSpace Also, make sure you change all of the parameters with file paths to suit, specifically:
      Code Block
      dspace.dir
      config.template.log4j.properties
      config.template.log4j-handle-plugin.properties
      config.template.oaicat.properties
      assetstore.dir
      log.dir
      upload.temp.dir
      report.dir
      handle.dir
  4. Create the directory for the DSpace installation (e.g. C:/DSpace)
  5. Generate the DSpace installation package by running the following from command line (cmd) :
    Code Block
    cd [dspace-source]/dspace/
    mvn package
    
    • Wiki Markup
      _Note #1:_ This will generate the DSpace installation package in your _\[dspace-source\]/dspace/target/dspace-\[version\]-build/_ directory.
    • Note #2: Without any extra arguments, the DSpace installation package is initialized for PostgreSQL. If you want to use Oracle instead, you should build the DSpace installation package as follows:
      Code Block
      mvn -Ddb.name=oracle package
  6. Wiki Markup
    Initialize the DSpace database and install DSpace to _\[dspace\]_ (e.g. _C:\DSpace_) by running the following from command line from your _\[dspace-source\]/dspace/target/dspace-\[version\]-build/_ directory:
    Code Block
    ant fresh_install
    • Note: to see a complete list of build targets, run: ant help
  7. Wiki Markup
    Create an administrator account, by running the following from your _\[dspace\]_ (e.g. _C:\DSpace_) directory:
    Code Block
    [dspace]\bin\dspace create-administrator
  8. Wiki Markup
    Copy the Web application directories from _\[dspace\]\webapps_ to Tomcat's webapps dir, which should be somewhere like _C:\Program Files\Apache Software Foundation\Tomcat\webapps_
    • Wiki Markup
      Alternatively, Tell your Tomcat installation where to find your DSpace web application(s). As an example, in the _<Host>_ section of your _\[tomcat\]/conf/server.xml_ you could add lines similar to the following (but replace _\[dspace\]_ with your installation location): 
      Code Block
      <!-- DEFINE A CONTEXT PATH FOR DSpace XML User Interface  -->
      <Context path="/xmlui" docBase="[dspace]/webapps/xmlui" debug="0"
      	reloadable="true" cachingAllowed="false"
      	allowLinking="true"/>
      
      <!-- DEFINE A CONTEXT PATH FOR DSpace JSP User Interface  -->
      <Context path="/jspui" docBase="[dspace]/webapps/jspui" debug="0"
      	reloadable="true" cachingAllowed="false"
      	allowLinking="true"/>
      
      <!-- DEFINE A CONTEXT PATH FOR DSpace OAI User Interface  -->
      <Context path="/oai" docBase="[dspace]/webapps/oai" debug="0"
      	reloadable="true" cachingAllowed="false"
      	allowLinking="true"/>
      
      <!-- DEFINE ADDITIONAL CONTEXT PATHS FOR OTHER DSPACE WEB APPLICATIONS (SOLR, SWORD, LNI, etc.). 
           CHANGE THE VALUE OF "[app]" FOR EACH APPLICATION YOU WISH TO ADD -->
      <Context path="/[app]" docbase="[dspace]/webapps/[app]" debug="0"
      	reloadable="true" cachingAllowed="false"
      	allowLinking="true"/>
      
  9. Start the Tomcat service
  10. Browse to either http://localhost:8080/jspui or http://localhost:8080/xmlui. You should see the DSpace home page for either the JSPUI or XMLUI, respectively.

...