The Fedora 4 web-application supports several deploy-time, system-level configuration options. These configuration elements are set via the definition of System Properties.
Four means of deploying Fedora 4 have been verified
Each of these deployment approaches has its own way of setting System Properties.
On Debian Linux systems, the typical way of setting System Properties is to update the following file:
/etc/default/tomcat7 |
Within that file, new properties can be added per the example below:
JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.home=/mnt/fedora-data" |
Additional information regarding the configuration of System Properties in Tomcat 7 can be found here.
On Debian Linux systems, one way of setting System Properties is to update the following file:
/etc/default/jetty |
Within that file, new properties can be added per the example below (note the use of JAVA_OPTIONS instead of JAVA_OPTS):
JAVA_OPTIONS="${JAVA_OPTIONS} -Dfcrepo.home=/mnt/fedora-data" |
Additional information regarding the configuration of System Properties in Jetty 9 can be found here.
System Properties can be set when using the Maven jetty:run plugin by passing them per the example below:
mvn -Dfcrepo.home=/mnt/fedora-data jetty:run |
If the One-Click Run is started from the command line, System Properties can be passed in per the example below:
java -Dfcrepo.home=/mnt/fedora-data -jar fcrepo-webapp-jetty-console.war |