Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
faqs [2012/05/22 19:22]
webadmin
faqs [2013/09/13 16:45] (current)
Line 5: Line 5:
  
  
-The default database is an [[http://​db.apache.org/​derby/​|Apache Derby database]], which is flat files-based,​ relational database that the Shepherd Project ​auto-creates on your file system in the Tomcat root directory. However, because we use DataNucleus,​ you can use a large number of database software and database types with the Shepherd Project. [[http://​www.datanucleus.org/​products/​accessplatform_2_1/​datastores.html|Please see this listing from DataNucleus.]] To define a new database type, you must set the appropriate DataNucleus properties in the bundled file commonConfiguration.properties. If you change entries in this file, you must also restart your J2EE contain (e.g., Tomcat) for the change to take effect.+The default database is an [[http://​db.apache.org/​derby/​|Apache Derby database]], which is flat files-based,​ relational database that Wildbook ​auto-creates on your file system in the Tomcat root directory. However, because we use DataNucleus,​ you can use a large number of database software and database types with Wildbook. [[http://​www.datanucleus.org/​products/​accessplatform_2_1/​datastores.html|Please see this listing from DataNucleus.]] To define a new database type, you must set the appropriate DataNucleus properties in the bundled file jdoConfig.properties. If you change entries in this file, you must also include the related JDBC JAR file for the selected database in Wildbook WEB-INF/lib directory and finally ​restart your J2EE contain (e.g., Tomcat) for the change to take effect.
  
 Our experience is that Derby does not scale to meet the needs of large projects, and PostgreSQL can fail on complex queries due to errors in its JDBC connector. We have had the best success using MySQL. Our experience is that Derby does not scale to meet the needs of large projects, and PostgreSQL can fail on complex queries due to errors in its JDBC connector. We have had the best success using MySQL.
Line 20: Line 20:
 **I have a lot of existing mark-recapture data. Do I have to manually enter it in through the web interface?​** **I have a lot of existing mark-recapture data. Do I have to manually enter it in through the web interface?​**
  
-No, you can also use the Shepherd Project ​API to build your own custom data importer, which will read in your data and create the corresponding org.ecocean.Encounter and org.ecocean.MarkedIndividual objects for persistence.+No, you can also use Wildbook ​API to build your own custom data importer, which will read in your data and create the corresponding org.ecocean.Encounter and org.ecocean.MarkedIndividual objects for persistence.