...

java -Dfcrepo.home=my-fcrepo-6-home -jar fcrepo-webapp-<latest fedora 6 version>-jetty-console.jar --headless

FAQs

Why isn't Fedora showing my migrated data?

The very first time Fedora starts it initializes the database and indexes any resources on disk. On subsequent starts these steps are not executed. If you started Fedora once and either your migrated content was not in place or there was some other configuration problem that needed addressed, then Fedora initialized to an empty state and it will not see your content until it has been instructed to reindex all of the resources in the repository.

Until FCREPO-3611 is complete, the only way to instruct Fedora to reindex is by dropping or truncating its tables in the database. So, you can fix the problem by:

1. Stop Fedora
2. Drop/truncate its tables in the database
3. Start Fedora

If you are testing Fedora and are not yet using an external database, then you can fix the problem by deleting the H2 database files found at FCREPO_HOME/data/fcrepo-h2.mv.db and FCREPO_HOME/data/fcrepo-h2.trace.db.

When you start Fedora after clearing the database, you should see it reindex the repository and your resources should now be available as expected.