Webapp Configuration

This page lists the various files needed to correctly configure an InterMine web application.

Webapp settings

• ~/build.properties.flymine
  • Every project imports ~/build.properties as the very first properties file imported. You can therefore override practically any property globally, for all projects, by defining it in ~/build.properties. See the example file for a few that might be useful.
• <MODEL_NAME>/webapp/resources/web.properties
  • Properties used to configure the web application - details
  • e.g. the text on the home page, the content of example on the list upload page, etc

Model specific Struts definitions

• <MODEL_NAME>/webapp/resources/struts-config-model.xml
  • the content of this file is appended to the intermine/webapp/resources/struts-config.xml file.
  • This file should be used to define model specific struts actions. The corresponding Action source should go in <MODEL_NAME>/webapp/src, and jsp pages in <MODEL_NAME>/webapp/resources/webapp/model/
• <MODEL_NAME>/webapp/resources/tiles-defs-model.xml
  • works in the same way as struts-config-model.xml, only for tiles.

Model dependent configuration

• <MODEL_NAME>/webapp/resources/webapp/WEB-INF/webconfig-model.xml
  • Sets which fields are highlighted on the report page. This can be fields belonging to object references, eg. for Exon: identifier, chromosomeLocation.start
  • Triggers which fields are displayed in the online table (showInInlineCollection=true/false) and in the results table (showInResults=true/false)
  • Custom data displayers

Definition of class keys

• bio/core/props/resources/class_keys.properties
  • Specifies keys for classes in the data model.
  • Define which objects can be stored in lists
  • Used for porting lists to new releases
  • Define which fields are links in the results table