This documentation covers an old version of Fedora. Looking for another version? See all documentation.
Upgrade utility not currently compatible with version 3.4.2
The upgrader utility is not currently compatible with version 3.4.2 of Fedora, due to the Java package renaming in this release.
This issue is currently being addressed, see the JIRA issue. We will announce on the mailing lists when a new version of the utility is available. In the meantime, you must upgrade to Fedora 3.3 as described below, then follow the instructions on Upgrading from 3.x.
This document explains how to migrate your Fedora repository from version 2.x to 3.x. Although it is written assuming 3.3, the same instructions apply if you are upgrading to an older 3.x release. Before continuing, you should familiarize yourself with the new Content Model Architecture. A basic understanding of how the CMA works will be helpful in understanding the migration process.
Throughout this guide,
OLD_FEDORA_HOME refers to the home directory of your Fedora 2.x installation, and
NEW_FEDORA_HOME refers to the home directory of your new Fedora 3.x installation.
NOTE: To reduce confusion during this process, if you have previously ingested the Fedora demo objects, you should purge them from your 2.x repository before starting with the migration process. The demo objects have changed significantly since 2.x, and if you'd like the new versions, we recommend that you ingest them after performing a successful migration of your old repository.
Follow the instructions in the Fedora Installation and Configuration Guide. When finished, start the server and verify your installation was successful by visiting the describeRepository page (e.g. http://localhost:8080/fedora/describe
). Finally, shut down Fedora. It should not be restarted again until later in the migration process.
Determine where your old object XML is stored. If you're unsure, consult
OLD_FEDORA_HOME/server/config/fedora.fcfg and find the value of
NEW_FEDORA_HOME/server/fedora.fcfg and change the value of
object_store_base the full path of your old object's directory.
NOTE: The upgrade process will transform the objects in
NEW_FEDORA_HOME/server/fedora.fcfg in place. Thus, by following the above instructions, the new upgraded files will exist in their old location. If that is not what is desired, then you could copy the old files (both objects and content) to their final location, point the
NEW_FEDORA_HOME/server/fedora.fcfg to that new location, and then continue the update process.
If you haven't already done so, make a backup of all original object XML files. These will be changed during the transformation part of the migration process, and if something goes wrong, this backup will be your only way of recovering.
Determine where your old Fedora Repository's managed Datastreams are stored. Again, you can check your old
fedora.fcfg file. Look for the value of
NEW_FEDORA_HOME/server/fedora.fcfg and change the value of
datastream_store_base the full path of your old Datastreams directory.
NOTE: The migration process will not make any changes to these files.
The migration utilities come as a separate download from the Fedora installation. They are all included, with source, in a single download fedora-migration-3.2.zip at sourceforge.net. Once unzipped, you will find the executable jars in the top directory.
Although the filename is fedora-migration-3.2.zip, the utilities will also work for migrating to Fedora 3.3
The analyzer examines all of your existing digital objects and looks for similarities. It outputs the following information in a directory you specify.
The analyzer does not make changes to any source objects.
The analyzer accepts a Java properties file for configuration.
In properties files, the "\" character must be escaped. When using Windows, this means paths like
c:\work\abc must be written with two backslashes as a path delimiter rather than one.
Create a file (e.g.
migration.properties) with the following content, filling in values appropriate to your environment:
The analyzer utility is an executable jar and takes the configuration file as a parameter. For example, if your configuration is in the current directory and is named migration.properties, enter the following:
If upgrading to Fedora 3.3 with an embedded Derby database (a configuration that is not recommended for production), you may notice an error similar to "java.sql.SQLException: Cannot close a connection". This does NOT indicate that the analyzer failed, and can be safely ignored.
The analyzer will produce several files in the output directory.
Generated content models will be in FOXML 1.1 format and will be named
cmodel-n.xml (where n is a number used for association). For each of these, there will be an associated
cmodel-n.members.txt file containing a list of PIDs that conform to the content model.
Each content model object will contain the following inline XML datastreams:
If the member objects had disseminators:
RELS-EXTDatastream. This RDF Datastream points to the original Behavior Definition (now known as Service Definition) objects via a Fedora-defined
fedora-model:hasServicerelationship. This relationship means that members of this content model should have the behaviors defined within the target SDef(s).
cmodel-n-deployments.txtfile in the output directory. For each Behavior Mechanism formerly used by the objects' disseminators, this file identifies the original BMech, specifies a PID for a new, similar Service Deployment, and specifies a set of Datastream input name changes that the copy should have. This information is used by the generator to create new content-model-specific Service Deployment objects.
Three additional files will be created in the output directory:
By default, the PIDs assigned to the generated content models are of the form,
changeme:CModelN. You should change these to use your own repository's namespace. You may also want to change the identifier part of the PID (e.g. myns:Journal).
To do this, open each
cmodel-n.xml file in an editor and change the following as desired:
RELS-EXTDatastream, change the part after
rdf:aboutattribute. For example, change
cmodel-n-deployments.txt files were created by the analyzer, you should also change any
NEW_DEPLOYMENT pid values specified within each before continuing. These PIDs will default to values like
changeme:CModel1-BMech1, but again, you should specify your own (e.g. myns:Journal-DefaultImpl).
DO NOT specify the same PID for
OLD_BMECH, as this will cause ingest problems later.
By default, the analyzer ensures that every data object is assigned to a content model. If you'd rather avoid assigning an explicit content model to an object, you may do so by a) removing its PID from the
cmodel-n-members.txt file in which it resides and b) adding it to the
nocmodel.txt file. This may be done for any number of objects.
In order for migration to work properly, the PID of every object in the source repository must occur exactly once in the set of PID list files.
The generator reads the output of the analyzer (along with any customizations you have made) and adds the following to the same directory:
The generator does not make changes to the source objects.
Like the analyzer, the generator accepts a Java properties file for configuration.
The configuration file should have the following content, with values filled in appropriate to your environment.
Since you already entered
migration.properties, you can minimize typing by just using that file, and adding the necessary
sourceDir parameter as shown below.
The generator utility also accepts the configuration file as a parameter. For example:
The generator will produce several files in the output directory. These files, along with those already produced by the analyzer, will be used in the next steps of the migration process.
One stylesheet will be written for each PID list:
nocmodel.xslt, and each
cmodel-n.members.xslt file. Each of these stylesheets will include transformation rules for upgrading the objects to FOXML1.1 and adding the necessary
fedora-model:hasModel relationship via
RELS-EXT, if necessary.
The generated stylesheet will cause a new
RELS-EXT Datastream to be created, or will amend the content of the latest revision of the
RELS-EXT Datastream, if it already exists.
The output will also include a new, generated Service Deployment object (
cmodel-n.deploymentN.xml) for each one listed in the input's
cmodel-n.deployments.txt files. This SDep will match the content of the source SDep in the repository, but it will have a different PID, will be in FOXML 1.1 format, and will use input part names consistent with the Datastream IDs specified in the associated content model's
The transformer applies stylesheets to FOXML stored in a Fedora repository. Although it directly accepts the output of the analyzer and generator, it can also be used outside of the migration process for making low-level changes to batches of objects. When running the transformer in this way, the repository should be shut down, and the
rebuilder should be run immediately afterward (see section below).
Here's how the transformer works: It scans a directory for PID list files, ending with .txt. For each, if a .xslt file exists with the same name, that stylesheet is applied to the repository's FOXML for each object in the PID list.
The transformer makes changes to object XML in the repository. It is possible to damage some, or all of the objects in the repository by using the transformer, so be sure to make a backup first!
Like the analyzer and generator, the transformer accepts a Java properties file for configuration. The transformer is configured with the same properties that the generator is configured with (see above), and also takes the following:
Although not required, it is strongly recommended that you run the transformer with
dryRun=true the first time, to ensure all transformations will fully succeed.
The transformer utility also takes the configuration file as a parameter. For example:
Now that all of your existing objects have been upgraded, you need to run the
rebuilder so Fedora's database is up-to-date with the files on disk. See the Rebuilder documentation for further details.
You MUST rebuild the SQL database. Rebuilding the Resource Index is required only if your Fedora 3.x Repository has been configured to enable the Resource Index.
Rebuilding the SQL database will take around double the time that the transformer took. Rebuilding the Resource Index may take significantly longer.
After the rebuilder has run successfully, you should restart your Fedora 3.x instance and visit the describe page (e.g. http://localhost:8080/fedora/describe
) again to make sure it started successfully.
Now you'll need to ingest all the new Content Model and Service Deployment objects created during the analyzer and generator steps. To do this:
fedora-admin.shand login to your new repository from the local machine.
The admin client may try to ingest all files in the directory, including the non-FOXML files. While harmless, you may wish to copy all FOXML files (all files in that directory that end in .xml) to a separate directory, and ingest from there.
You should now verify that the upgraded objects are behaving as expected. Pick a few from each
cmodel-n.members.txt file and do the following for each:
If you had Disseminators in your original repository, you are now making use of a NEW set of Service Deployment objects. You may now want to purge the original BMechs, since they are no longer in use. The simplest way to do this is with the
fedora-admin GUI. The PIDs of the old former BMechs are enumerated in the file