Upgrade to Release 1.7.10 from 1.7.09c

Version Information

Current Version:1.7.10
Release Date:May 14, 2018
License:i2b2 Open Source License

Download

Descriptioni2b2 Released VersionMinimum Version RequiredDownload LinkRequirements
Files to upgrade the i2b2 server to 1.7.101.7.101.7.09ci2b2_upgrade_1.7.09c_to_1.7.10.zipSee Technical Details section on the i2b2 Upgrades page.
Files to upgrade the i2b2 Database to 1.7.101.7.10  i2b2createdb-1710.zip 
Files to upgrade the i2b2 Web Client to 1.7.101.7.10  i2b2webclient-1710.zip 

 Notes

    • Release 1.7.10 contains changes to the i2b2 database and Web Client. Therefore in addition to the i2b2upgrade-1710.zip file you also need to download the i2b2createdb-1710.zip and i2b2webclient-1710.zip files. The process of installing the i2b2 Web Client has not changed. If you have questions on how this is done you can find additional information in Chapter 7. i2b2 Web Client Install of the i2b2 Installation Guide.
    • The i2b2 Admin module no longer needs to be setup on the i2b2 server. This is due to a new feature introduced in release 1.7.10 that enables a single sign-on location for both the Web Client and Admin Module. Please see the 1.7.10 Release Notes for additional information.
    • If you are upgrading to 1.7.10 from a release prior to 1.7.09c it is important you read the upgrade documentation before upgrading your system because earlier upgrades had changes to properties files. When a release has a change to a property file as did 1.7.09 we will make note of it and outline the steps to merge the changes into your local properties file.

Upgrade Instructions

The release of i2b2 1.7.08 introduced a major platform change in which the JBoss 7 application server was replaced with WildFly 10 (formerly known as “JBoss” 10), and JDK 8 became required.

With consideration that you may be using custom ports, proxies, HTTPS, and other custom configurations that must be re-setup in WildFly from scratch and/or may be incompatible with WildFly, we have introduced a new upgrade path for using your existing JBoss 7 with i2b2 by providing drop-in JARs.

Knowing some sites have remained on JBoss 7 while some have upgraded to WildFly 10, we have gone ahead and provided Step-by-Step Instructions for both scenarios. For the most part the overall process is very similar. What is different, is the path in which the files reside. Expand the box below to see an example of the differences between the two path names.

 

 

Example Paths to i2b2.war
JBoss 7 path

 


 

WildFly 10 path

 



Step-by-Step Instructions for JBoss


Stop JBoss

 

Linux Example  Expand source

 

 

Backup your existing i2b2.war directory


Linux

On Linux, make a copy of /opt/jboss-as-7.1.1.Final/standalone/deployments/i2b2.war/ and save it to a different location outside of /opt/jboss-as-7.1.1.Final/ 

 


 

Windows

On Windows, make a copy of c:\opt\jboss-as-7.1.1.Final\standalone\deployments\i2b2.war\ and save it to a different location outside of c:\opt\jboss-as-7.1.1.Final\ 

 

 

Delete i2b2.war.deployed file

 

Linux Example  Expand source

 

 

DO NOT delete your existing i2b2.war directory. The zip file contains only a subset of files to add/replace in your existing i2b2.war directory.

 

 

Extract / copy the deployment files from the upgrade zip file to your JBoss deployments directory


 

 

Copy the deployments directory into your existing JBoss standalone directory, replacing any existing files when prompted.

 

 

Linux Example  Expand source

 

 

Start JBoss



Linux Example  Expand source

 

 

Verify your upgrade

 

 

Test Web Client

Navigate to your local i2b2 Web Client in your preferred browser and verify you are able to log on and perform standard i2b2 functions. (e.g. Run queries, retrieve previous queries, view breakdowns, etc.)

 

 

Step-by-Step Instructions for WildFly


Stop WildFly


Linux Example  Expand source

 

 

Backup your existing i2b2.war directory


Linux

On Linux, make a copy of /opt/wildfly-10.0.0.Final/standalone/deployments/i2b2.war/ and save it to a different location outside of /opt/wildfly-10.0.0.Final/ 

 


 

Windows

On Windows, make a copy of c:\opt\wildfly-10.0.0.Final\standalone\deployments\i2b2.war\ and save it to a different location outside of c:\opt\wildfly-10.0.0.Final

 

 

Delete i2b2.war.deployed file

 

Linux Example  Expand source

 

 

DO NOT delete your existing i2b2.war directory. The zip file contains only a subset of files to add/replace in your existing i2b2.war directory.

 

 

Extract / copy the deployment files from the upgrade zip file to your WildFly deployments directory


 

 

Copy the deployments directory into your existing WildFly standalone directory, replacing any existing files when prompted.

 

 

Linux Example  Expand source

 

 

Start WildFly



Linux Example  Expand source

 

 

Verify your upgrade

 

 

Test Web Client

Navigate to your local i2b2 Web Client in your preferred browser and verify you are able to log on and perform standard i2b2 functions. (e.g. Run queries, retrieve previous queries, view breakdowns, etc.)

 

 

 


 

Contents of the Zip File

 

i2b2upgrade-1709c-to-1710.zip

 

database/

Crcdata/

scripts/

oracle/

query_demo_insert_data.sql

postgresql/

query_demo_insert_data.sql

sqlserver/

query_demo_insert_data.sql

crc_create_query_oracle.sql

crc_create_query_postgresql.sql

crc_create_qyert_sqlserver.sql

Pmdata/

upgrade_oracle_i2b2pm_tables.sql

upgrade_postgresql_i2b2pm_tables.sql

upgrade_sqlserver_i2b2pm_tables.sql

 

deployments/

deployments/i2b2.war/ 

deployments/i2b2.war/WEB-INF/

deployments/i2b2.war/WEB-INF/lib/

deployments/i2b2.war/WEB-INF/lib/CRC-core.jar

deployments/i2b2.war/WEB-INF/lib/FR-core.jar

deployments/i2b2.war/WEB-INF/lib/i2b2Common-core.jar

deployments/i2b2.war/WEB-INF/lib/IM-core.jar

deployments/i2b2.war/WEB-INF/lib/Ontology-core.jar

deployments/i2b2.war/WEB-INF/lib/ProjectManagement-core.jar

deployments/i2b2.war/WEB-INF/lib/Workplace-core.jar

deployments/i2b2.war/WEB-INF/services/

deployments/i2b2.war/WEB-INF/services/CRC.aar

deployments/i2b2.war/WEB-INF/services/FR.aar

deployments/i2b2.war/WEB-INF/services/IM.aar

deployments/i2b2.war/WEB-INF/services/ProjectManagement.aar

deployments/i2b2.war/WEB-INF/services/Ontology.aar

deployments/i2b2.war/WEB-INF/services/Workplace.aar

deployments/i2b2.war.dodeploy