...
On Debian Linux systems, the typical way of setting System Properties is to update the following file:
| No Formatcode |
|---|
/etc/default/tomcat7 |
Within that file, new properties can be added per the example below:
...
Alternatively on Windows systems you can set the following file:
| No Formatcode |
|---|
CATALINA_BASE/bin/setenv.bat (windows) |
...
| Code Block |
|---|
set CATALINA_OPTS=%CATALINA_OPTS% -Dfcrepo.ispn.repo.cache=F:\fedora\cache |
| Note |
|---|
| When starting up tomcat on windows if you receive an error like the following it may be necessary to include a fcrepo.ispn.repo.cache like above. |
| Code Block |
|---|
Caused by: org.fusesource.leveldbjni.internal.NativeDB$DBException: IO error: F:\apache-tomcat-7.0.50-windows-x64\apache-tomcat-7.0.50\bin\fcrepo4-data\fcrepo.ispn.repo.cache\data\MANIFEST-000002: The handle is invalid.home=f:\fedora-data |
| Anchor | ||||
|---|---|---|---|---|
|
On Debian Linux systems, one way of setting System Properties is to update the following file:
| No Formatcode |
|---|
/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):
...
Alternatively on Windows systems you can set the following file:
| No Formatcode |
|---|
{JETTY_DIST}/start.ini |
Within that file, new properties can be added per the example below:
...
There are a number of configuration elements that can be optionally be set when starting the Fedora 4 web-application, noted below within brackets: <>. The only configuration element that is required to be set is "fcrepo.modeshape.configuration".
| No Formatcode |
|---|
fcrepo.home=<cwd/fcrepo4-data> |
This can be set to a path (relative to the current working directory or absolute) to which Fedora repository content will be written. 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.
| No Formatcode |
|---|
fcrepo.modeshape.configuration=<classpath:/config/repository.json | file:/path/to/repository.json> |
This specifies the configuration for the underlying Modeshape repository and is required to be set. See other available options for this value within the source tree. Example repository.json configurations are located within the WAR file within sub-directories under WEB-INF/classes/config. Note: this configuration file must be readable by the servlet container process.
| No Format |
|---|
fcrepo.ispn.configuration=<config/infinispan.xml> |
This specifies the underlying Infinispan cache configuration. This value has a tested default set in the modeshape.json file mentioned above; and therefore, can usually be left as is. The default file is located within the WAR file under WEB-INF/classes/config.
| Code Block |
|---|
| No Format |
java.io.tmpdir=</tmp on Linux, $TMPDIR on MacOSX, and %TEMP% on Windows> |
This specifies the directory for writing temp files. You may need to set this property to a larger disk/filesystem to upload large files, particularly on Linux where /tmp is sometimes on a small partition.
| No Formatcode |
|---|
fcrepo.jms.baseUrl=<http://localhost:8080/fcrepo/rest> |
...
Note: If you have multiple instances of Fedora running, the following system properties must be set to avoid messaging port conflicts:
| No Formatcode |
|---|
fcrepo.dynamic.jms.port=<default-of-61616> fcrepo.dynamic.stomp.port=<default-of-61613> |
This specifies the ports used by the embedded JMS-based message broker, both for OpenWire and STOMP protocols.
| No Formatcode |
|---|
fcrepo.velocity.runtime.log=<$fcrepo.home/velocity.log> |
The HTML template code uses Apache Velocity, which generates a runtime log called velocity.log. By default this is placed inside fcrepo.home, but it is possible to override the location to have it written to an alternate location.
| Anchor | ||||
|---|---|---|---|---|
|
...
The Modeshape and Infinispan configurations mentioned above have a number of more detailed configuration elements that can optionally be set. To see exactly which elements are available to be set, inspect the repository.json and infinispan.xml files file specified above. Those files can be browsed in the source tree in:
- the ModeShape configuration directories and,the Infinispan configuration directories.
Some common elements for Modeshape and Infinispan relate Modeshape relate to the directories in which application information is persisted. As mentioned above, if no fcrepo.home property is set then application information will be persisted under the directory "fcrepo4-data" in the application's current working directory. There will then be several directories within "fcrepo4-data" that are named by default with the name of the property that can be set to configure each of those directories.
Below are some common examples of these directories:
| No Format |
|---|
fcrepo.ispn.repo.cache |
Contains the serialized repository resource properties.
| No Formatcode |
|---|
fcrepo.modeshape.index.directory |
Contains the internal Lucene index used by Modeshape/Admin Search.
| No Formatcode |
|---|
fcrepo.activemq.directory |
Contains the reliable messaging information maintained by ActiveMQ.
| No Formatcode |
|---|
com.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.default.objectStoreDir com.arjuna.ats.arjuna.objectstore.objectStoreDir |
...