OpenELIS-Global 1 to 2 Conversion

Notes:

Be sure to create a backup BEFORE attempting this!

Choosing a Path

Path 1 is going to be the easiest and most reliable method of upgrading from version 1 to 2, but requires having a spare machine to place OpenELIS-Global 2 on.

Path 2 is a less reliable way to move from version 1 to 2, but can be done without using a spare machine.

Backups

Before attempting any upgrade paths, be sure you have accessible backups of your currently running version of OpenELIS-Global 1 available on another drive/server.

For path 1 this involves checking to make sure you are able to successfully restore from your backup file

For path 2, it is recommended to have a backup of your entire system, not just the database.

Testing New Installation

• Ensure you can log in (check more than just admin account)

• Ensure old data can be properly found (ex. Search for an old patient)

Path 1: Migrate Server to New Machine

This is the recommended method of upgrading

ENSURE YOU BACK UP YOUR DATABASE FIRST

Dump Database on Old Server

1. make a logical backup of your database

2. sudo -u postgres pg_dump -d clinlims > OpenELIS-backup.sql

Install OpenELIS-Global 2 on New Server

1. Follow normal install instructions for OpenELIS-Global 2

2. Currently located here

Pause Docker containers on New Server

1. Run the following command

2. sudo docker kill openelisglobal-webapp external-fhir-api

Restore Database Dump on New Server

1. Copy OpenELIS-backup.sql from old server onto new server

2. Copy OpenELIS-backup.sql into the docker db container

3. sudo docker cp OpenELIS-backup.sql openelisglobal-database:/OpenELIS-backup.sql

4. Recreate the database and import the dump

5. sudo docker exec openelisglobal-database psql -Uadmin -dpostgres -c 'DROP DATABASE clinlims;'

6. sudo docker exec openelisglobal-database psql -Uadmin -dpostgres -c 'CREATE DATABASE clinlims;'

7. sudo docker exec openelisglobal-database psql -Uadmin -dpostgres -c 'ALTER DATABASE clinlims OWNER TO clinlims;'

8. sudo docker exec openelisglobal-database psql -Uadmin -dclinlims -f /OpenELIS-backup.sql

Migrate Passwords (If Unmigrated) on New Server

1. Follow password migration instructions

2. Currently located here

Migrate Encrypted Values on New Server

1. sudo docker exec -it openelisglobal-database psql -Uclinlims -dclinlims

2. SELECT id, name, value FROM clinlims.site_information WHERE encrypted = 't';

3. record the "value" column for each row

4. UPDATE clinlims.site_information SET value = '' WHERE encrypted = 't';

5. \q

6. re-add the values using the front end once the server is back up and running

Run Liquibase on New Server

1. Download the old liquibase files and if there is a custom branch, change to it

2. git clone https://github.com/I-TECH-UW/Liquibase-Outdated.git

3. cd Liquibase-Outdated

4. git checkout <branch>

5. Run the liquibase command

6. put the correct connection values in ./liquibase.properties

7. java -jar -Dfile.encoding=utf-8 ./lib/liquibase-1.9.5.jar --defaultsFile=./liquibase.properties --url=jdbc:postgresql://localhost:5432/clinlims --contexts=<context> update

8. if it complains about md5 checksums, run

   1. sudo docker exec -it openelisglobal-database psql -Uclinlims -dclinlims -c "UPDATE clinlims.databasechangelog SET md5sum = NULL;"

9. if Liquibase exits citing that a changeset failed, then that changeset will need to be updated in the proper branch to accommodate that DB. Fixing a changeset can occur in many ways and should be done by a developer who understands OpenELIS and its relationship with the DB.

   1. If the changeset is doing an operation that is non-essential for your context (ie updating an Organization that doesn't exist in your DB), your context can be dropped from that changesets list of contexts

   2. If the changeset relies on a previous changeset to run first (dropping a constraint from a table that is missing one), that previous changeset can be added to your context

   3. If the changeset is updating based on some value that is different in this DB, the SQL should be updated to accommodate both values (ie test section called Microbiology vs Microbiologie)

Update Installation on New Server

1. Run upgrade script from OE2 Installer directory

2. sudo python2 setup_OpenELIS.py

Path 2: Update Server in Place

ENSURE YOU HAVE BACKED UP YOUR DATABASE AND SERVER FIRST

Backup Postgres

1. Run the following command

2. sudo -u postgres pg_dump > OpenELIS-backup.sql

Uninstall Tomcat from Server

Upgrade Ubuntu to Target Version

1. Update packages

2. sudo apt-get update

3. sudo apt-get upgrade

4. Update current distribution 3. sudo apt-get dist-upgrade

5. Upgrade to next version 4. sudo apt-get install update-manager-core 5. sudo do-release-upgrade 6. Will run for a while...

6. Check if running target version 7. lsb_release -a

7. If version does not match target version, repeat from step 1

Update/Install Installation

1. Follow normal install/upgrade instructions for OpenELIS-Global 2

2. Currently located here

Restore Database Dump into new DB

1. Copy OpenELIS-backup.sql into the docker db container

2. sudo docker cp OpenELIS-backup.sql openelisglobal-database:/OpenELIS-backup.sql

3. Recreate the database and import the dump

4. sudo docker exec openelisglobal-database psql -Uadmin -dpostgres -c 'DROP DATABASE clinlims;'

5. sudo docker exec openelisglobal-database psql -Uadmin -dpostgres -c 'CREATE DATABASE clinlims;'

6. sudo docker exec openelisglobal-database psql -Uadmin -dpostgres -c 'ALTER DATABASE clinlims OWNER TO clinlims;'

7. sudo docker exec openelisglobal-database psql -Uadmin -dclinlims -f /OpenELIS-backup.sql

Migrate Passwords (If Unmigrated)

1. Follow password migration instructions

2. Currently located here

Migrate Encrypted Values on New Server

1. sudo docker exec -it openelisglobal-database psql -Uclinlims -dclinlims

2. SELECT id, name, value FROM clinlims.site_information WHERE encrypted = 't';

3. record the "value" column for each row

4. UPDATE clinlims.site_information SET value = '' WHERE encrypted = 't';

5. \q

6. re-add the values using the front end once the server is back up and running

Run Liquibase on New Server

1. Download the old liquibase files and if there is a custom branch, change to it

2. git clone https://github.com/I-TECH-UW/Liquibase-Outdated.git

3. cd Liquibase-Outdated

4. git checkout <branch>

5. Run the liquibase command

6. put the correct connection values in ./liquibase.properties

7. java -jar -Dfile.encoding=utf-8 ./lib/liquibase-1.9.5.jar --defaultsFile=./liquibase.properties --url=jdbc:postgresql://localhost:5432/clinlims --contexts=<context> update

8. if it complains about md5 checksums, run

   1. sudo docker exec -it openelisglobal-database psql -Uclinlims -dclinlims -c "UPDATE clinlims.databasechangelog SET md5sum = NULL;"

Update Installation

1. Run upgrade script from OE2 Installer directory

2. sudo python setup_OpenELIS.py