Property files for a Mine

Each Mine needs to be correctly configured using attributes set in a few properties files.

<MINE>.properties

This file holds the properties needed during the build process and deployment of the web application. The <MINE>.properties defines the location of databases to be used and some configuration for InterMine behaviour. It should be located in <HOME>/.intermine.

An example file, flymine.properties:

Error: Macro Include(source:trunk/intermine/doc/example/flymine.properties) failed

'NoneType' object has no attribute 'get_node'

Note: this file extends default properties found in malariamine/default.intermine.integrate.properties.

suffixes

It's possible to use several properties files by adding a suffix. Here's an example scenario:

1. add a suffix to the name of your property file:
   • malariamine.properties.dev - points to the development database and a webapp
2. use the -Drelease ant target

   # `dev` is the suffix on the properties filename
   
   # malariamine/integrate
   ant build-db -Drelease=dev
   
   # malariamine/webapp
   ant default remove-webapp release-webapp -Drelease=dev
   

class_keys.properties

Specifies keys for classes in the data model. Fields specified in this file will be links in the results table in the webapp. Only objects with key fields defined can be saved in lists

Error: Macro Include(source:trunk/flymine/dbmodel/resources/class_keys.properties) failed

'NoneType' object has no attribute 'get_node'

Mine properties shared between users

In addition to the user properties above, each mine needs two global properties file. These should be in the root directory of the mine - e.g. in the malariamine directory.

• default.intermine.integrate.properties - used by the loading/integration stage
• default.intermine.webapp.properties - used by the intermine webapp code when running inside Tomcat.

In general these files can be copied from another mine, eg. MalariaMine, as very little customisation is needed.