Upgrades

Upgrading Mifos

Guide on how to upgrade Mifos to a new version.

The goal of this document is to serve as a general guideline for the steps to be followed when upgrading a customer to a new version of Mifos.

Before upgrading to a new version, collect the following information about the existing environment:

Review version-specific upgrade instructions.
Screen shot of the System Info page. This includes Mifos revision, DB revision, etc.
Note server's environment usage - disk space available, memory available, CPU usage when current Mifos deployment is running.
Note environment settings for Java including JAVA_HOME and JAVA_OPTS.
Review the Mifos install guide to determine if the upgrade will require updates to supporting tools such as MySQL, Java, and BIRT.
Determine if upgrade is going to increment the Database revision. This will impact the rollback procedure. Need to document roll back procedure for both cases - DB version the same revision, and DB version triggers a DB upgrade. For documentation on manual MySQL database upgrades, please visit our wiki.
Backup BIRT reports
Backup MySQL data

Install any necessary updates to supporting tools.
Download Mifos upgrade and deploy on a test server that has a copy of the latest production data.
Check system info page to confirm newer war has been deployed on test server.
Monitor batch job processes on test server.
Execute selected User Acceptance Tests to ensure functionality is working.

Schedule production deployment with users.
Stop tomcat
Backup MySQL data
Install any necessary updates to supporting tools.
Move existing mifos.war file from $CATALINA_HOME/webapps (Mifos 1.6-2.1) or $JETTY_HOME/webapps (Mifos 2.2-2.3) to safe backup location.
Deploy new war file to $CATALINA_HOME/webapps (Mifos 1.6-2.1) or $JETTY_HOME/webapps (Mifos 2.2-2.3).
Delete $CATALINA_HOME/webapps/mifos (Mifos 1.6-2.1).
Delete $CATALINA_HOME/work/Catalina/localhost/mifos (Mifos 1.6-2.1).
Start Tomcat (Mifos 1.6-2.1) or Jetty (Mifos 2.2-2.5).
Check system info page to confirm newer war has been deployed on production server.
Restore BIRT reports that might have been removed during deployment of new war file.
Monitor batch job processes on production server.
Execute selected User Acceptance Tests to ensure functionality it working.

Send upgrade results to your customer support representative to record your current environment.
After users are back on the system, check log files for unexpected errors after upgrade.