...
Each of these deployment approaches has its own way of setting System Properties.
Anchor | ||||
---|---|---|---|---|
|
On Debian Linux systems, the typical way of setting System Properties is to update the following file:
...
Additional information regarding the configuration of System Properties in Tomcat 7 can be found here.found here.
Windows notes
Alternatively on Windows systems you can set the following file:
No Format |
---|
CATALINA_BASE/bin/setenv.bat (windows) |
Within that file, new properties can be added per the example below:
Code Block |
---|
set CATALINA_OPTS=%CATALINA_OPTS% -Dfcrepo.ispn.repo.CacheDirPath=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.CacheDirPath 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.CacheDirPath\data\MANIFEST-000002: The handle is invalid. |
Anchor | ||||
---|---|---|---|---|
|
On Debian Linux systems, one way of setting System Properties is to update the following file:
...
Additional information regarding the configuration of System Properties in Jetty 9 can be found here.
Windows notes
Alternatively on Windows systems you can set the following file:
No Format |
---|
{JETTY_DIST}/start.ini |
Within that file, new properties can be added per the example below:
Code Block |
---|
--exec
-Dfcrepo.home=/mnt/fedora-data |
Maven jetty:run
System Properties can be set when using the Maven jetty:run plugin by passing them per the example below:
Code Block |
---|
mvn -Dfcrepo.home=/mnt/fedora-data jetty:run |
One-Click Run
If the One-Click Run is started from the command line, System Properties can be passed in per the example below:
Code Block |
---|
java -Dfcrepo.home=/mnt/fedora-data -jar fcrepo-webapp-jetty-console.war |
Anchor | ||||
---|---|---|---|---|
|
There are a number of configuration elements that can be optionally be set when starting the Fedora 4 web-application. No configuration elements are required to be set, as they all default values (noted below within brackets: <>).
No Format |
---|
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 Format |
---|
fcrepo.modeshape.configuration=<classpath:/config/repository.json | file:/path/to/repository.json> |
This specifies the configuration for the underlying Modeshape repository. See other available options for this value within the source tree. The default file is located within the WAR file under WEB-INF/classes/config.
No Format |
---|
fcrepo.infinispan.cache_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.
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.
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 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 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.CacheDirPath |
Contains the serialized repository resource properties.
No Format |
---|
fcrepo.modeshape.index.location |
Contains the internal Lucene index used by Modeshape/Admin Search.
No Format |
---|
fcrepo.activemq.dir |
Contains the reliable messaging information maintained by ActiveMQ.
No Format |
---|
com.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.default.objectStoreDir
com.arjuna.ats.arjuna.objectstore.objectStoreDir |
Contain JBoss JTA transaction engine artifacts.