Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

See the Quick Start guide to getting Fedora 4 up and running as quickly as possible.

Excerpt

Although deploying

Excerpt
hiddentrue

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.

...

Table of Contents

...

Downloads

See the latest release for Fedora 4 WAR files to download.


Include Page
System Requirements
System Requirements

...

Deploying with Tomcat 7

  1. Download and install Tomcat 
  2. Set the Java properties for Tomcat (see: Application Configuration and Catalina Java Properties sections below)
  3. Copy the Fedora 4 WAR file into Tomcat's "webapps" directory (e.g. /

    etc

    var/

    default

    lib/tomcat7/webapps)

     mentioned in the following Application Configuration section 
  4. Drop the fcrepo-webapp (or your own distribution) WAR file into Tomcat's webapps directory.

Application Configuration

System config

  • fcrepo.modeshape.configuration defaults to "classpath:/config/single/repository.json"
  • fcrepo.infinispan.cache_configuration defaults to "config/infinispan/leveldb/infinispan.xml"
  • fcrepo.host defaults to "localhost"
  • fcrepo.port defaults to "8080"
  • fcrepo.ctxt defaults to "rest"
  • fcrepo.home can be set to a path (relative to the current working directory or absolute) in which fedora repository content will be written by default.  Any of the Modeshape and Infinispan configuration options below will default to being within this folder if unset or if set to a relative path.  If unset, content will be put in the "fcrepo4-data" directory within the current working directory.

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>
-Dfcrepo.ispn.alternative.CacheDirPath=<some-dir>
-Dfcrepo.ispn.binary.alternative.CacheDirPath=<some-dir>
-Dfcrepo.ispn.repo.CacheDirPath=<some-dir>

JMS  config

Code Block
-Dfcrepo.activemq.dir=<some-dir>
  1. Start the server
  2. 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

  1. Download and install Jetty
  2. Set the Java properties for Jetty  (see: Application Configuration and Catalina Java Properties sections below)
  3. Copy the Fedora 4 WAR file into Jetty's "webapps" directory (e.g. /var/lib/jetty/webapps)
  4. Start the server
  5. 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

Anchor
javaprops
javaprops
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/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>

...