...

The application needs a directory of sufficient size (depending on your expected load) for storing application state files as well as receiving space data both from the DPN node as well as from DuraCloud.  The tomcat user must have read/write access to the directory. 

Create log directory

The bridge application will attempt to write logs to /var/log/duracloud. To make this possible, create that directory, and set permissions to allow the bridge application to write to it.

sudo mkdir /var/log/duracloud
sudo chown tomcat7 /var/log/duracloud

Setup Tomcat

1. Set up tomcat server credentials for automatic deployment on build

   1. in your settings.xml file (~/.m2/settings.xml)  add the following to the servers element:

      Code Block
      <server> <id>tomcat-server</id> <username>tomcat</username> <password>password</password> </server>

   2. Set up environment with the following settings:

      1. duracloud.bridge.root.username - the username used for initializing the instance (default root).

      2. duracloud.bridge.root.password - the password used for initializing the instance (default rpw).

      3. duracloud.bridge.root.email  - an email associated with the root account that will send email regarding bridge server events.

      4. duracloud.bridge.root.dir - a directory that will receive data as well as store non-database application state and settings.

      5. in the /etc/default/tomcat7 file add the following parameters to your JAVA_OPTS environmental variable

         Code Block
         JAVA_OPTS="$JAVA_OPTS -Dduracloud.bridge.root.password=<your password> -Dduracloud.bridge.root.email=<your email> -Dduracloud.bridge.root.dir=<your root dir>"

...