Workbook on Digital Private Papers > Installing - Fedora 2.1

Installing - Fedora 2.1

Acquiring the software and documentation

Download: the Fedora 2.1 software from http://www.fedora.info/download

The following screenshot shows us acquiring one of the rpms to be installed:

suse50c/thumbs/fedora-03.jpg

Download the Fedora Server binary distribution

suse50c/thumbs/fedora-05.jpg

Download the Fedora Client binary distribution

suse50c/thumbs/fedora-06.jpg

If you want to verify the downloaded distributions prior to using them you can also download their associated MD5 files.

suse50c/thumbs/fedora-07.jpg

Right Click on the MD5 links

suse50c/thumbs/fedora-08.jpg

Choose the same download location as the distributions. The Paradigm project will write these files to removable media for installation on our dark archive servers which have no direct access to the internet.

suse50c/thumbs/fedora-09.jpg

Before you progress to the installation, we would advise that you acquire a copy of the Fedora Installation Instructions and read them thoroughly.

suse50c/thumbs/fedora-10.jpg

Performing the installation via the command line

Open a terminal window and acquire root level privileges.

su
Password:

suse50c/thumbs/fedora-11.jpg

Our downloads have been put on a DVD in a directory called download this directory will be found in the mount directory /media/dvdrecorder/. We are installing Fedora in /usr/local - so we move to that directory and extract the distributions there.

cd /usr/local
tar xzf /media/dvdrecorder/download/fedora-2.1-server.tar.gz
tar xzf /media/dvdrecorder/download/fedora-2.1-client.tar.gz
tar xzf /media/dvdrecorder/download/fedora-2.1-src.tar.gz

suse50c/thumbs/fedora-24.jpg

Change the permissions of the files in the server/bin and client/bin directories so that we can execute them:

chmod 755 /usr/local/fedora-2.1/server/bin/*
chmod 755 /usr/local/fedora-2.1/client/bin/*

and create an alias 'fedora' for 'fedora-2.1' to make it easier to perform future upgrades:

ln -s fedora-2.1 fedora

suse50c/thumbs/fedora-28.jpg

Prepare the global environment variables by creating the file /etc/profile.d/fedora.sh :

kate /etc/profile.d/fedora.sh

suse50c/thumbs/fedora-29.jpg

Enter the following lines:

#
# /etc/profile.d/fedora.sh
#

#
#
export FEDORA_HOME=/usr/local/fedora
export FEDORA_DEV=/usr/local/fedora-src
export PATH=$FEDORA_HOME/server/bin:$FEDORA_HOME/client/bin:$PATH

suse50c/thumbs/fedora-32.jpg

Add the global environment variables to our current shell (note: don't omit the "dot ." at the beginning of the command):

. /etc/profile.d/fedora.sh

suse50c/thumbs/fedora-32b.png

Check that the executable path has been set:

echo $PATH

suse50c/thumbs/fedora-32c.png

Create the directory root for storage of Fedora repository objects, datastreams, resource index and logs:

mkdir -p /var/data/fedora/logs

suse50c/thumbs/fedora-32d.png

Pre-creating a MySQL database instance for Fedora

We need to pre-create the Fedora Mysql database which Fedora will populate when first initialised.

mysql-config /usr root "" fedoraAdmin fedoraAdmin fedora21 true

Press enter when prompted for a password or supply a valid dba password if one has already been set.

suse50c/thumbs/fedora-33b.png

The result will should be this:

suse50c/thumbs/fedora-33c.png

You can remove the creation script now, or later if you prefer to examine it first.

suse50c/thumbs/fedora-33d.png

Type localhost/phpMyAdmin into the location bar of a browser to check that the empty Fedora database has been created:

suse50c/thumbs/fedora-33e.png

Configuring the Fedora Server

1: Run the Fedora Setup Utility to establish your base security settings!

Before starting for the first time, the Fedora Setup Utility (fedora-setup) must be run to select a base security configuration . Once fedora-setup has been run you can then customise the generated configuration files as needed.

In Fedora 2.1, you can choose from four different security configurations. Consult the Securing Your Repository Guide for a description of security configuration options.  To create a configuration equivalent to that present in Fedora 2.0 (no SSL, API-M authentication, open API-A) select the "no-ssl-authenticate-apim" option as demonstrated below.  You can change to more secure configurations at any time by rerunning the Fedora Setup Utility.

Run the Fedora Setup Utility.

fedora-setup no-ssl-authenticate-apim

  • suse50c/thumbs/fedora-34.jpg
  • 2:  Customise settings in the Fedora Server Configuration File (fedora.fcfg).

    The Fedora server configuration file contains:

    1. global parameters for the Fedora server
    2. configuration parameters for each server module
    3. configuration parameters for each persistent data store of the Fedora server

    We need to edit the configuration file, so ask the console to open the file using the Kate editor:

    kate $FEDORA_HOME/server/config/fedora.fcfg

    suse50c/thumbs/fedora-33.jpg

    The opened configuration file should look something like this:

    suse50c/thumbs/fedora-34e.png

    You will need to modify the value of some of these parameters to suit your installation. The following is a list of parameters changed in Paradigm's base installation together with the values substituted and the line no. at which they can be found in the configuration file.

    Line Parameter Value

    3 repositoryName
    ParadigmFedora Repository

    19 fedoraServerPort
    8085

    23fedoraShutdownPort
    8010

    27fedoraRedirectPort
    8448

    31fedoraServerHost
    localhost

    35object_store_base
    /var/data/fedora/objects

    40datastream_store_base
    /var/data/fedora/datastreams

    55log_dir
    /var/data/fedora/logs

    134REPOSITORY-POLICIES-DIRECTORY
    /var/data/fedora/fedora-xacml-policies/repository-policies

    135SURROGATE-POLICIES-DIRECTORY
    /var/data/fedora/fedora-xacml-policies/surrogate-policies

    136 REPOSITORY-POLICY-GUITOOL-POLICIES-DIRECTORY
    /var/data/fedora/fedora-xacml-policies/repository-policies-generated-by-policyguitool

    192pidNamespace
    paradigm

    193retainPIDs
    demo test paradigmfedora-bdef fedora-bmech tutorial

    337level
    1

    343repositoryName
    Paradigm Personal Papers Repository

    344repositoryDomainName
    paradigm.ac.uk

    345adminEmails
    oai-admin@paradigm.ac.uk susan@paradigm.ac.uk renhart@paradigm.ac.uk

    634path
    /var/data/fedora/resourceIndex

    3:  Start Fedora Service.

    We can now start Fedora by keying the following in the console:

    cd /var/data/fedora/logs

    fedora-start

    suse50c/thumbs/fedora-34c.png

    Verify that the Fedora MySQL database has been initialised with the Fedora tables by keying localhost/phpMyAdmin into the location bar of a browser:

    suse50c/thumbs/fedora-34d.jpg

    4: Testing Fedora Services.

    http://localhost:8085/ should bring up the default Fedora Tomcat container:

    suse50c/thumbs/fedora-35.jpg

    http://localhost:8085/fedora/search should bring up the default Fedora Repository search screen:

    suse50c/thumbs/fedora-36.jpg

    To test the Fedora Admin GUI client, open a console and type:

    fedora-admin

    This will launch the client:

    suse50c/thumbs/fedora-37.jpg

    In our configuration we changed the server port from 8080 to 8085, so at login we must reflect this by substituting 8080 for 8085 in the 'Fedora Server' field. If you didn't change the default username and password in the fedora.fcfg file, both of these will be fedoraAdmin.

    Yippee the long march is over and we're in!

    suse50c/thumbs/fedora-38.jpg

     

    suse50c/thumbs/fedora-39.jpg