Web Config Crop Module

Add crop

• Create a PostgreSQL database for the given database name with nomenclature for crop database as “gobii_cropname”, e.g. gobii_maize, gobii_wheat, gobii_rice

• Populate the newly created database with basic liquibase seed data (context: general, seed_general)

• Load the given seed data for PI contacts (typically provided by the organization/client)

• Duplicate the WAR file of an existing crop (ex. gobii_dev.war, gobii_wheat.war) as gobii_<cropname>.war

• Ensure that the new WAR file is expanded by tomcat (usually via the manager’s redeploy/deploy functionality)

• Add the corresponding entries to the gobii-web.xml file (the entire crop xml block)

• Create the new crop’s subdirectory in gobii_bundle/crops/*

• Create the corresponding cron jobs for the new crop

• Redeploy the new gobii-*.war application

HIGH

 Edit crop

•  Rename PostgreSQL database for the given database name to new name

• Rename the WAR file of an existing crop (ex. gobii_dev.war, gobii_wheat.war) as gobii_<newcropname>.war

• Ensure that the new WAR file is expanded by tomcat (usually via the manager’s redeploy/deploy functionality)

• Edit the corresponding entries to the gobii-web.xml file (the entire crop xml block)

• Rename the crop’s subdirectory in gobii_bundle/crops/*

• Rename the corresponding cron jobs for the new crop

• Redeploy the new gobii-*.war application

 MEDIUM

Delete crop

• Backup GDM (including files and database)

• Drop PostgreSQL database for the given database name

• Edit liquibase to reflect changes

• Stop web service for crop in Tomcat

• Remove crop service from Tomcat

• Edit the corresponding entries to the gobii-web.xml file (the entire crop xml block)

• Delete crop’s subdirectory in gobii_bundle/crops/*

• Remove the corresponding cron jobs for crop

LOW