Application Configuration

The Fedora 4 web-application supports several deploy-time, system-level configuration options. These configuration elements are set via the definition of System Properties.

...

Deployments

Four means of deploying Fedora 4 have Fedora have been verified

• Tomcat 7 8 servlet container
• Jetty 9 servlet container
• Maven jetty:run plugin - for testing
• One-Click Run - for testing

Each of these deployment approaches has its own way of setting System Properties.

Anchor
tomcat tomcat

Tomcat

...

8

On Debian Linux systems, the typical way of setting System Properties is to update the following file:

/etc/default/tomcat7tomcat8

Within that file, new properties can be added per the example below:

JAVA_OPTS="${JAVA_OPTS} -Dfcrepo.modeshape.configuration=classpath:/config/file-simple/repository.json -Dfcrepo.home=/mnt/fedora-data"

Additional information regarding the configuration of System Properties in Tomcat 7 8 can be found here.

Windows notes

Alternatively on Windows systems you can set the following file:

...

set CATALINA_OPTS=%CATALINA_OPTS% -Dfcrepo.modeshape.configuration=classpath:/config/file-simple/repository.json

Reverse Proxy

If you have a reverse proxy for serving HTTPS that uses Tomcat's HTTP port, you will also need to set up a RemoteIPValve in your server.xml in order for Tomcat to rewrite links with HTTPS.

To do this you will first need to make sure the X-Forwarded-Proto header is set in your server config (example with Apache):

<VirtualHost *:443>
    RequestHeader set X-Forwarded-Proto "https"
    ServerName dummy-host.example.com

    SSLEngine on
    SSLCertificateFile  /etc/ssl/certs/localhost.crt
    SSLCertificateKeyFile /etc/ssl/private/localhost.key

    ProxyPreserveHost On
    ProxyRequests Off
    ProxyPass / http://localhost:8080/
    ProxyPassReverse / http://localhost:8080/

    DocumentRoot "/opt/fedora/apache-tomcat-8.5.66/webapps/fcrepo-webapp"
</VirtualHost>

Then you will need to add a Valve to the localhost Engine in Tomcat's server.xml:

        <Valve className="org.apache.catalina.valves.RemoteIpValve"
               protocolHeader="x-forwarded-proto" />

Anchor
jetty jetty

Jetty 9

On Debian Linux systems, one way of setting System Properties is to update the following file:

...

There are a number of configuration elements that can be optionally be set when starting the Fedora 4 webFedora web-application, noted below within brackets: <>. The only configuration element that is required to be set is "fcrepo.modeshape.configuration".

...

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.

fcrepo.external.content.allowed=</path/to/allowed.txt>

This provides the path to a file defining a list of allowed external binary content paths. If this parameter is not provided, then clients will be disallowed from creating external binary resources. See the external content allowed paths configuration for more details.

Anchor
modeispn modeispn

Modeshape

...

Contains the internal Lucene index used by Modeshape/Admin Search. 

fcrepo.activemq.directory

Contains the reliable messaging information maintained by ActiveMQ.

com.arjuna.ats.arjuna.common.ObjectStoreEnvironmentBean.default.objectStoreDir
com.arjuna.ats.arjuna.objectstore.objectStoreDir

...

The standard configuration chain is as follows:

1. fcrepo4fcrepo/fcrepo-webapp/src/main/webapp/WEB-INF/web.xml contains a context-param element with param-name "contextConfigLocation".  The param-value points to a repository.xml which includes either the default fcrepo-config.xml or your spring configuration file (as defined by the fcrepo.spring.configuration property.
2. Your spring configuration file contains a property repositoryConfiguration defining the location of your repository.json
3. fedora-node-types.cnd is defined in repository.json