Upgrade i2b2 Server: Precompiled JARs
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 1.7.09b by providing drop-in JARs.
A zip file containing a precompiled version of i2b2 1.7.09c has been provided in the Download section of this document. The contents of the zip file can be dropped into your existing instance of i2b2 to upgrade it. The JARs were compiled with JDK 7 and will run in your existing JBoss 7 or WildFly application server. The upgrade technique will work on both Linux and Windows environments.
The following requirements must be met in order to use this upgrade path:JBoss 7 (tested on JBoss
<!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>
|Release Date:||May 14, 2018|
|License:||i2b2 Open Source License|
|Description||i2b2 Released Version||Minimum Version Required||Download Link||Requirements|
|Files to upgrade the i2b2 server to 1.7.10||1.7.10||1.7.09c||See Technical Details section on the i2b2 Upgrades page.|
|Files to upgrade the i2b2 Database to 1.7.10||1.7.10||i2b2createdb-1710.zip|
|Files to upgrade the i2b2 Web Client to 1.7.10||1.7.10||i2b2webclient-1710.zip|
- 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.
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.
|Description||i2b2 Released Version||Minimum Version Required||File Size||Download Link||Requirements|
|Files to upgrade the i2b2 server from at least 1.7.05 to 1.7.09c.||1.7.09c||1.7.05||i2b2upgrade-1705-to-1709c.zip||See Technical Details section.|
- These upgrade instructions are to upgrade the software for only the i2b2 server. It does not include any changes to made to the i2b2 Database or the i2b2 Web Client software. Depending on the current version of your i2b2, you may need to also get the latest i2b2 Web Client and Data zip files to deploy. If you are upgrading from 1.7.09b you do not need these other components as release 1.7.09c contains server changes only.
- In April 2016, we provided instructions to patch a potential security vulnerability in JBoss 7, specifically in the commons-collections-3.2.1.jar shipped with JBoss 7.
Step-by-Step Instructions for JBoss
Step-by-Step Instructions for WildFly
Contents of the Zip File