Stop WildFly

$ /opt/wildfly-{version}.Final/bin/jboss-cli.sh --connect command=:stop

> \opt\wildfly-{version}.Final\bin\standalone stop

Backup existing deployment directory containing i2b2.war file

On Linux, copy the /opt/wildfly-{version}.Final/standalone/deployments/ and save it to a different location outside of /opt/wildfly-{version}.Final/ 

On Windows, copy the c:\opt\wildfly-{version}.Final\standalone\deployments\ and save it to a different location outside of c:\opt\wildfly-{version}.Final\

Upgrade deployments folder

Copy all the files from the extracted downloaded deployment folder into your existing WildFly standalone/deployments directory.

Example your deployments folder: /opt/<wildfly-17.0.0.Final >/standalone/deployments/

Example extracted deployments folder: i2b2core-upgrade-181\i2b2\deployments

Update  datasource (*-ds.xml) files  

In your deployment directory, copy *-ds.xml files from the backup folder to wildfly-17.0.#.Final/standalone/deployments

Replace ALL the <driver>{something}.jar</driver> with latest drivers as below

Edit the following files crc-ds.xml, ont-ds.xml, pm-ds.xml, work-ds.xml  with the above jar file name

Migrate cell properties to 1.8.1 1a if needed. In 1.7.12, cell properties have been moved to the database, in a table called hive_cell_params. If any cell properties were previously changed, they will need to be manually updated in the database. After this, the properties files can be deleted to prevent confusion.

More documentation on setting cell properties is available at this page. Most commonly, the AGG_SERVICE_ACCOUNT password will need to be updated. Generally, the cell URLs do not need to be configured anymore, as the hostname and port is now auto-detected.

Steps to perform db upgrade:

• Backup your existing data folder
• Copy all the folders created by extracting the latest version into your existing  data Upgrade folder. This will replace existing Crcdata, Hivedata, Metadata, PMdata folders. Example:  Downloads\i2b2core-upgrade-181\i2b2\data to C:\opt\edu.harvard.i2b2.data\Release_1-8\Upgrade\.
• Copy the db.properties files from your back up into the respective locations (namely Crcdata, Hivedata, Metadata, PMdata )
• Open the command prompt and navigate to each cell folder and run the following upgrade ant commands on your i2b2 database instance, where {db} can  be Oracle, sqlserver or postgresql.
  Alternative to above Step, you can run individual SQL scripts on your db instance in place of ant commands.
• In datafolder\Release_1-8\Upgrade\  run the ant commands under each individual cell folder as below

Backup existing webclient folder to a different location outside of your current webclient installation folder

Install new webclient 

• Extract the i2b2webclient-181.zip 
• Replace your existing webclient folder on your web server with the  extracted new webclient folder

• i2b2_config_data.js has been renamed to i2b2_config_domain.json. Edit the i2b2_config_domain.json  using your existing i2b2_config_data.js from your backed up web directory. Details are provided here

Start WildFly 

You can either run WildFly standalone or as a service.

$ /opt/wildfly-{version}.Final/bin/standalone.sh -b 0.0.0.0 &

> \opt\wildfly-{version}.Final\bin\standalone start

Test Webclient

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.)