Info |
---|
See the Quick Start guide to getting Fedora 4 up and running as quickly as possible. |
Excerpt |
---|
Although deploying Fedora 4 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 4 WAR files to download.
Include Page |
---|
| System Requirements |
---|
| System Requirements |
---|
|
Deploying with Tomcat 7
- Download and install Tomcat
- Set the Java properties for Tomcat (see: Application Configuration and Catalina Java Properties sections below)
Copy the Fedora 4 WAR file into Tomcat's "webapps" directory (e.g. /var/lib/tomcat7/webapps)
- Start the server
- Go to the browser page that matches your fedora 4 WAR file name (e.g. http://localhost:8080/fcrepo-webapp-4.0.0-beta-4-SNAPSHOT/rest)
Deploying with Jetty 8
- Download and install Jetty
- Set the Java properties for Jetty (see: Application Configuration and Catalina Java Properties sections below)
- Copy the Fedora 4 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 4 WAR file name (e.g. http://localhost:8080/fcrepo-webapp-4.0.0/rest)
Include Page |
---|
| Application Configuration |
---|
| Application Configuration |
---|
|
Catalina Java Propertiesfcrepo.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/tomcat7), then Fedora 4 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)
Code Block |
---|
-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
System Requirements
- Java7
- Servlet 3.0 container
The github repository has a post-commit hook that trigger a build on ci.fcrepo.org. This build publishes maven artifacts to sonatype, and pushes the fcrepo-kitchen-sink war to futures6: http://fcrepo4.fcrepo.org/fcrepo/rest/.
Fedora 3 is also deployed on futures6: http://fcrepo4.fcrepo.org/fedora.
Deploying with Tomcat
- Set the Java properties (e.g. /etc/default/tomcat7) mentioned in the following Application Configuration section
- Drop the fcrepo-webapp (or kitchen sink, or your own distribution) WAR into Tomcat
Application Configuration
System config
Code Block |
---|
-Dfcrepo.host=<hostname>
-Dfcrepo.port=<port>
-Dfcrepo.ctxt=<context> |
- fcrepo.host defaults to "localhost"
- fcrepo.port defaults to "8080"
- fcrepo.ctxt defaults to "rest"
Modeshape and Infinispan config
Code Block |
---|
-Dcom.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.default.objectStoreDir=<some-dir>
-Dcom.arjuna.ats.arjuna.objectstore.objectStoreDir=<some-dir>
-Dfcrepo.ispn.CacheDirPath=<some-dir>
-Dfcrepo.ispn.binary.CacheDirPath=<some-dir>
-Dfcrepo.modeshape.index.location=<some-dir> |
JMS config
...