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:
We'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.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 existing 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
ant installerThen 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
$FEDORA_HOME/tomcat/bin/startup.shor if you're on Windows:
%FEDORA_HOME%\tomcat\bin\startup.bat
http://localhost:8080/fedora/(or
http://HOST:PORT/fedorawith whatever host and port you chose to install it on).
$FEDORA_HOME/tomcat/bin/shutdown.shor if you're on Windows:
%FEDORA_HOME%\tomcat\bin\shutdown.bat
$FEDORA_HOME/tomcat/bin/shutdown.sh
$FEDORA_HOME/server/config/fedora.fcfg
<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">
$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."
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.cd $FEDORA_HOME/client fedora-admin.sh
http://HOST:PORT/fedora/searchwhere HOST and PORT depend on what you chose when you installed it. E.g. http://localhost:8080/fedora/search