Table of Contents

  1. Upgrading from Fedora 2.1 to Fedora 2.1.1
  2. Upgrading from Fedora 2.0 to Fedora 2.1.1
  3. Upgrading from versions prior to 2.0

1. Upgrading From Fedora 2.1 to Fedora 2.1.1

The move from Fedora 2.1 to Fedora 2.1.1 is quite simple and does not require migration of objects or rebuilding of the resource index. There are, however, important configuration and script changes between 2.1 and 2.1.1. These changes include the following:

Follow these steps to upgrade your Fedora server from 2.1 to 2.1.1.

  1. Backup: it is highly recommended that you create a backup of your existing Fedora 2.1 repository
  2. Download: download the Fedora 2.1.1 software from
  3. Install: install the Fedora 2.1.1 software
  4. Run the Fedora Setup Utility.  In Fedora 2.1.1, you can choose among four different security configurations.  Consult the Securing Your Repository Guide for a description of security configuration options.  To have an equivalent configuration to what was in Fedora 2.0 (no SSL, API-M authentication, open API-A) select the "no-ssl-authenticate-apim" option as demonstrated below.  You can easily change to more secure configurations at any time by rerunning the Fedora Setup Utility. 
    C:\fedora-2.1.1> fedora-setup no-ssl-authenticate-apim


  5. Configure Object Storage Location:  in the Fedora 2.1.1 server configuration file (fedora.fcfg) set the object storage location to point to that of of the Fedora 2.1.1 repository, for example:
    <param name="object_store_base" value="C:\fedora2_1_objects" isFilePath="true"/>


  6. Configure Datastream Storage Location: in the Fedora 2.1.1 server configuration file (fedora.fcfg) set the datastream storage location to point to that of of the Fedora 2.1 repository, for example:
    <param name="datastream_store_base" value="C:\fedora2_1_datastreams" isFilePath="true"/>


  7. Configure the Resource Index Storage Location: in the Fedora 2.1.1 server configuration file (fedora.fcfg) set the resource index storage location to point to that of of the Fedora 2.1 repository, for example:
    <datastore id="localKowariTriplestore">
    <comment>local Kowari Triplestore used by the Resource Index</comment>
    <param name="connectorClassName" value="org.trippi.impl.kowari.KowariConnector"/>
    <param name="remote" value="false"/>
    <param name="path" value="C:\fedora2_1_resourceIndex"/>
    <param name="serverName" value="fedora"/>
    <param name="modelName" value="ri"/>
    <param name="poolInitialSize" value="3"/>
    <param name="poolMaxGrowth" value="-1"/>
    <param name="readOnly" value="false"/>
    <param name="autoCreate" value="true"/>
    <param name="autoTextIndex" value="false"/>
    <param name="memoryBuffer" value="true"/>
    <param name="autoFlushDormantSeconds" value="5"/>
    <param name="autoFlushBufferSize" value="20000"/>
    <param name="bufferFlushBatchSize" value="20000"/>
    <param name="bufferSafeCapacity" value="40000"/>


  8. Configure the SQL Database Location:  in the Fedora 2.1.1 server configuration file (fedora.fcfg) set the relational database location topoint to the pre-existing database (used by the Fedora 2.1 repository), for example (if using MySQL):
    <datastore id="localMySQLPool">
      <param name="dbUsername" value="fedoraAdmin"/>
      <param name="dbPassword" value="fedoraAdmin"/>
      <param name="jdbcURL" value="jdbc:mysql://localhost/fedora21?useUnicode=true&amp;characterEncoding=UTF-8&amp;autoReconnect=true"/>
      <param name="jdbcDriverClass" value="com.mysql.jdbc.Driver"/>
      <param name="ddlConverter" value="fedora.server.utilities.MySQLDDLConverter"/>
      <param name="maxActive" value="100"/>
      <param name="maxIdle" value="10"/>
      <param name="maxWait" value="-1"/>
      <param name="minIdle" value="0"/>
      <param name="minEvictableIdleTimeMillis" value="1800000"/>
      <param name="numTestsPerEvictionRun" value="3"/>
      <param name="timeBetweenEvictionRunsMillis" value="-1"/>
      <param name="testOnBorrow" value="true"/>
      <param name="testOnReturn" value="true"/>
      <param name="testWhileIdle" value="true"/>
      <param name="whenExhaustedAction" value="1"/>

     If you are using Oracle or mckoi as your database, update the appropriate datastore configuration.

  9. Configure the fedoraServerHost and fedoraServerPort: in the Fedora 2.1.1 server configuration file (fedora.fcfg) set the values for fedoraServerHost and fedoraServerPort to match those of your Fedora 2.1 server configuration, for example:
    <param name="fedoraServerPort" value="8080">
    <comment>Defines the port number on which the Fedora server runs;
    default is 8080.</comment>
    <param name="fedoraShutdownPort" value="8005">
    <comment>Defines the port number used to shutdown the Fedora sever;
    default is 8005.</comment>
    <param name="fedoraRedirectPort" value="8443">
    <comment>Defines the redirect port of the Fedora sever; default is
    <param name="fedoraServerHost" value="localhost">
    <comment>Defines the host name for the Fedora server, as seen from the
    outside world.</comment>


  10. Start the Fedora 2.1.1 server
    C:\fedora-2.1.1> fedora-start
    Starting the Fedora server...
    2006-04-04 12:37:57PM EDT - Waiting for startup to begin
    2006-04-04 12:38:12PM EDT - Starting Fedora Server instance
    2006-04-04 12:38:12PM EDT - Initializing Server
    2006-04-04 12:38:13PM EDT - Fedora Version: 2.1.1
    2006-04-04 12:38:13PM EDT - Fedora Build: 1
    2006-04-04 12:38:13PM EDT - Server Host Name: localhost
    2006-04-04 12:38:13PM EDT - Server Port: 8080
    2006-04-04 12:38:13PM EDT - Debugging: OFF
    2006-04-04 12:38:13PM EDT - Initializing Modules
    2006-04-04 12:38:16PM EDT - Post-Initializing Modules
    2006-04-04 12:38:17PM EDT - Initializing XACML Authorization Module
    2006-04-04 12:38:24PM EDT - Started
    Finished. To stop server, use fedora-stop.


  11. You are done!

2. Upgrading From Fedora 2.0 to Fedora 2.1.1

When moving from Fedora 2.0 to Fedora 2.1.1 you will be able to do a simple software upgrade without having to migrate digital objects via a mass export and ingest. After you install Fedora 2.1.1, you can configure it to point to your existing repository datastores (both the existing repository directory storage locations and the existing relational database).  This involves changing parameters in the Fedora 2.1.1 server configuration file (fedora.fcfg) that define the storage directory paths and database location.  See the instructions in section 1 above for details.

Note that the Resource Index model changed between 2.0 and 2.1, hence a rebuild of the Resource Index is necessary if upgrading from 2.0 to 2.1.1. See the intructions for rebuilding the Resource Index.

3. Upgrading from versions prior to 2.0

To upgrade from a Fedora version prior to 2.0, you must first migrate to version 2.0, then follow the appropriate upgrade steps above.