See the Quick Start guide to getting Fedora up and running as quickly as possible. |
Although deploying Fedora is as easy as downloading the WAR file and copying to your servlet container's webapps directory, this document details the process. |
Downloads
See the latest release for Fedora WAR files to download.
Deploying with Tomcat 8
- Download and install Tomcat
- Set the Java properties for Tomcat (see: Application Configuration and Catalina Java Properties sections below)
Copy the Fedora WAR file into Tomcat's "webapps" directory (e.g. /var/lib/tomcat8/webapps)
- Start the server
- Go to the browser page that matches your Fedora WAR file name (e.g. http://localhost:8080/fcrepo-webapp-x.x.x/rest)
Deploying with Jetty 9
- Download and install Jetty
- Set the Java properties for Jetty (see: Application Configuration and Catalina Java Properties sections below)
- Copy the Fedora WAR file into Jetty's "webapps" directory (e.g. /var/lib/jetty/webapps)
- Start the server
- Go to the browser page that matches your Fedora WAR file name (e.g. http://localhost:8080/fcrepo-webapp-x.x.x/rest)
Catalina Java Properties
fcrepo.home=<some-writable-directory>
Sets the home for Fedora's persisted data. Without this setting Fedora tries to use the current-working-directory as the home of persisted data. If the Tomcat user does not have write access to the installation area (e.g. /var/lib/tomcat8), then Fedora will not deploy. Set this system property to a directory writable by the tomcat process.
JVM Tuning Properties
We have a separate page with suggested VM options for general Java tuning.
Clustering Properties (only effective in a clustered configuration)
-Djgroups.tcp.address=<ip-address>
-Dfcrepo.ispn.numOwners=<num-nodes-in-cluster>
-Djava.net.PreferIPv4Stack=true
-Dfcrepo.ispn.replication.timeout=<timeout-in-ms> |
- fcrepo.ispn.replication.timeout can be used to set the timeout of infinispan replication in a clustered environment