...

As the names imply, these files contain default configuration. If you want to change you configurations (which you likely will), copy any or all of those three files and remove the "default." prefix. Files named, "runtime.properties", "applicationSetup.n3", and "developer.properties" will that precedence over the default configurations. Note: If you make non-default configurations, make sure that the files are readable by the system user under which the Tomcat or Jetty service is being run.

Digest File

In order to manage the state of VIVO home directory a digest.md5 file has been introduced. It will afford maintaining customizations through restarts and upgrades. The implementation can be found in VitroHomeDirectory.java.

On first startup

• packed vivo home tar file is untarred into vivo home
  • if file already exists it will be overwritten*
• digest.md5 file is created of a checksum per tar entry

On restart

• digest.md5 is read in to determine if any files have changed
• packed vivo home tar file is untarred
  • if file already exists and matches digest checksum and does not match tar entry checksum, file is overwritten
• digest.md5 file is created of a checksum per tar entry

*if it is desired to keep VIVO home directory customizations on upgrade from previous version the following command can generate an initial digest.md5

find /vivo/home -type f | cut -c3- | grep -E '^bin/|^config/|^rdf/' | xargs md5sum > /vivo/home/digest.md5

Application Name

By default, the VIVO software uses "vivo" as its application name. This name is used in two places:

...