<!DOCTYPE html>
<html>
<head>
    <title>Upgrade i2b2 Software</title>
    <meta charset="UTF-8">
    <meta name="description" content="Upgrading the i2b2 Software to the latest version" />
    <meta name="keywords" content="i2b2, release, upgrade, 1.7.10" />
<!--    <link rel="stylesheet" type="text/css" media="all" href="/stylesheets/i2b2-wiki.css" /> -->
</head>
<body>
    <h1 class="releaseHeading" id="upgradeVersion-current">Upgrade to Release 1.7.10 from 1.7.09c</h1>
</body>
</html>


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.09cSee 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

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.




/opt/jboss-as-7.1.1.Final/standalone/deployments/i2b2.war/




/opt/<wildfly-17.0.0.Final and above versions>/standalone/deployments/






Step-by-Step Instructions for JBoss



Stop JBoss


$ /opt/jboss-as-7.1.1.Final/bin/jboss-cli.sh --connect command=:shutdown




Backup your existing i2b2.war directory


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/ 




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


$ rm /opt/jboss-as-7.1.1.Final/standalone/deployments/i2b2.war.deployed



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.



$ cp -r deployments /opt/jboss-as-7.1.1.Final/standalone




Start JBoss



$ /opt/jboss-as-7.1.1.Final/bin/standalone.sh -b 0.0.0.0 &




Verify your upgrade



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


$ /opt/wildfly-10.0.0.Final/bin/jboss-cli.sh --connect command=:shutdown




Backup your existing i2b2.war directory


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/ 




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


$ rm /opt/wildfly-10.0.0.Final/standalone/deployments/i2b2.war.deployed



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.



$ cp -r deployments /opt/wildfly-10.0.0.Final/standalone




Start WildFly



$ /opt/wildfly-10.0.0.Final/bin/standalone.sh -b 0.0.0.0 &




Verify your upgrade



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



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