Back to index page

Installing Fedora (2.2.1/3.0) and Fedora-related information

Here, we're following the official Fedora instructions for installing Fedora 2.2.1

Installation instructions for other versions of Fedora are similar and can be found at:

I've now tested Fedora 2.2.1 and Fedora 3.0 with the GS3 web services demo-client application, where Fedora 2.2.1 was installed on Linux and Fedora 3.0 on Windows.

Sections

A Preliminary Steps

  1. You need Greenstone 3.
    Since we will be working with Greenstone 3 documents stored in Fedora's repository as "Fedora Digital Objects", Greenstone 3 is needed for its functionality to convert GS3 documents into FedoraMETS format and put them into the Fedora repository.
    (If you only want a walkthrough on installing Fedora, then you don't need Greenstone 3 of course and can skip the parts of this document relating to that.)
  2. Fedora 2.2.1 requires Java 5 (I used jdk1.5.0_10).
    If you wish to compile it yourself, you will need Apache Ant 1.6.5 and put it on your PATH.
  3. Defining environment variables. See the official instructions for further details on this.

    Let's assume that when you have downloaded Fedora 2.2.1 and extracted it (as you will in Section B below), the Fedora executable stuff will go into a folder called "fedora" whose location is /full/path/to/fedora. With that in mind, we need to set the following environment variables:

    If you're on Linux, you can set the environment variables by editing your ~/.profile file and then, after saving the edits, logging out or doing a "source ~/.profile" in the x-term.
    For example:

    export JAVA_HOME=/opt/jdk1.5.0_10/
    export FEDORA_HOME=/my/path/to/fedora
    export CATALINA_HOME=$FEDORA_HOME/tomcat
    
    PATH=/opt/jdk1.5.0_10/bin:/opt/jdk1.5.0_10/bin/javac:/my/path/to/apache-ant-1.6.5:$FEDORA_HOME/server/bin:$FEDORA_HOME/client/bin:$PATH
    

    On Windows, adjustments to your PATH variable, and creation of new variables (like FEDORA_HOME, CATALINA_HOME, JAVA_HOME) are made by going to:

    Start > Control Panel > (Performance and Maintenance icon OR click on Switch to Classic View on the left >) System > Advanced tab. Press the Environment Variables button. Add new System Variables and edit the Path variable.
    Note that on Windows, you use the ; sign to append new items to your path, and when referring to previously declared environment variables you have to surround them with % signs: E.g.
    PATH=<whatever-was-on-your-path-before>;%FEDORA_HOME%/server/bin

B Installing Fedora 2.2.1

  1. Download Fedora 2.2.1 from http://www.fedora.info/download/.
    (Although I've not tried it, you could also try Fedora 2.2.2 or even Fedora 3 which are available from the Fedora Commons main page.)
  2. Extract it.
  3. Make sure you have the environment variables set as described in Preliminary Steps above. In an Linux x-term, move into extracted directory (e.g. fedora-2.2.1-src/) and type in xterm:
    ant installer
    Then go into the dist folder of the extraction directory (e.g. fedora-2.2.1-src/dist/) and type:
    java -jar fedora-2.2.1-installer.jar
  4. This will run the command-line installer. Choose "quick" installation.
  5. Accept everything as given and set a password for your Fedora Administrator account whose default username is "fedoraAdmin". By accepting the defaults, it will the server is set to run on localhost, port 8080 (with shutdown port 8005).
You will need to remember the following details of your installation:

C How to run Fedora (and how to stop it)

  1. First start up fedora server by typing the following in xterm:
    $FEDORA_HOME/tomcat/bin/startup.sh
  2. Point your browser to
    http://localhost:8080/fedora/
    (or
    http://HOST:PORT/fedora
    with whatever host and port you chose to install it on).
  3. An authorization dialogue will pop up, asking you to enter the username and password you chose upon installation.
If you ever want to stop the Fedora server, you will need to type in the X-term
$FEDORA_HOME/tomcat/bin/shutdown.sh

D Creating the custom Greenstone 3 pid prefix

In order to work with the Greenstone3 client application, you will need to create a custom pid prefix for Greenstone 3 in fedora, and call it "greenstone".
To do this, you will need to:
  1. Shutdown the fedora server
    $FEDORA_HOME/tomcat/bin/shutdown.sh
  2. Open up fedora's configuration file in a text editor
    $FEDORA_HOME/server/config/fedora.fcfg
  3. Go down to where it says:
    <param name="retainPIDs" value="demo test changeme fedora-bdef fedora-bmech tutorial">
    And append greenstone to the list of values, so you get something like:
    <param name="retainPIDs" value="demo test changeme fedora-bdef fedora-bmech tutorial greenstone">
  4. Restart the fedora server
    $FEDORA_HOME/tomcat/bin/startup.sh

Having made the change in the fedora config file, it will now recognise "greenstone" as a valid PID and allow you to create/ingest digital data objects with a pid where the prefix is "greenstone".
For more information, you may want to look at the Fedora Release Notes:

"PID generation has been activated. Upon ingestion, Fedora objects that pass validation are automatically assigned a unique persistent identifer or PID. The namespace prefix on the PID is determined by the namespace parameter in the fedora.cfg configuration file."

E Exporting Greenstone documents into Fedora's repository

There is nothing in our Fedora repository yet. We want to have Greenstone 3 documents exported into Fedora format stored here. This is what we need Greenstone 3 for. We will be using its functionality for converting Greenstone 3 docs into FedoraMETS and exporting them into Fedora.

Use the FLI—Fedora Librarian Interface—application to do this. Refer to the document Running FLI for information on how to do this.

http://trac.greenstone.org/browser/gsdl/trunk/bin/script/g2f-buildcol.pl
http://trac.greenstone.org/browser/gsdl/trunk/bin/script/g2f-import.pl
Greenstone to Fedora scripts. Similar to import.pl and buildcol.pl, g2f-import.pl first converts documents into FedoraMETS and then g2f-buildcol.pl ingests them into a Fedora repository. Needs to have FEDORA_HOME set.

F Further Information