Page History
html-text |
---|
<!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.1212a" /> <!-- <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.12 from 1.7.09c</h1> </body> </html> |
Anchor | ||||
---|---|---|---|---|
|
Version Information
Anchor | ||||
---|---|---|---|---|
|
Download
Description | i2b2 Released Version | Minimum Version Required | Download Link | Requirements |
---|---|---|---|---|
Files to upgrade the i2b2 server to 1.7. |
12a | 1.7. |
12a | 1.7.09c |
See Technical Details section on the i2b2 Upgrades page. |
Anchor | ||||
---|---|---|---|---|
|
Notes
Release 1.7.12 contains changes to the i2b2 core Server, database and Web Client.
Therefore in addition to the i2b2upgrade-1712.zip file you also need to download the i2b2createdb-1712.zip and i2b2webclient-1712.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. Anchor
- The upgrade process is now made easier using a pre-built war file and the properties files are now stored in the database.
- The prebuilt-war file has all the core, web and database files packaged together and available as single download zip file.
Note: If you are running your application on JBoss, please upgrade to Wildfly before proceeding with the upgrade.
Upgrade Instructions
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Knowing some sites have remained on JBoss 7 while some have upgraded to WildFly 10, we have gone ahead and provided Below are 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 namesafter you have upgraded to Wildfly.
UI Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
|
Anchor | ||
---|---|---|
|
|
|
Step-by-Step Instructions for
WildFly
In the following instructions the variable { version } refers to your version of Wildfly installed. We have tested with Wildfly 10, 14, and 17.
UI Steps | ||
---|---|---|
| ||
|
|
|
|
|
|
|
|
|
|
|
Delete i2b2.war.deployed file
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
$ rm /opt/jboss-as-7.1.1.Final/standalone/deployments/i2b2.war.deployed |
Warning |
---|
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.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
$ cp -r deployments /opt/jboss-as-7.1.1.Final/standalone |
Start JBoss
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
$ /opt/jboss-as-7.1.1.Final/bin/standalone.sh -b 0.0.0.0 & |
Verify your upgrade
UI Expand | ||
---|---|---|
| ||
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
size | small |
---|
Stop WildFly
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
$ /opt/wildfly-10.0.0.Final/bin/jboss-cli.sh --connect command=:shutdown |
|
|
|
|
|
|
Delete i2b2.war.deployed file
|
$ rm /opt/wildfly-10.0.0.Final/standalone/deployments/i2b2.war.deployed
Warning |
---|
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.
language | powershell |
---|---|
title | Linux Example |
collapse | true |
|
|
Anchor | ||||
---|---|---|---|---|
|
Contents of the Zip File
title | i2b2upgrade-1709c-to-1711.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
Metadata/
ont_oracle.sql
ony_postgresql.sql
ont_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