Developers Getting Started With i2b2
Space shortcuts
Space Tools
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

The deployment process at this stage of the installation will install the full i2b2 war file on the Wildfly Web Server. This page discuss the new "build war from source" method. To obtain and install a pre-compiled version, see the overview page "server install on 1.7.12 and higher".

Deploy edu.harvard.i2b2.server-common (Build from source)

The following steps will walk you through the deployment process. The commands on a Windows Server may differ slightly on a Unix Machine. This difference will be noted when appropriate.

Step 1: Change working directory

The first step in the cell configuration process is to change your working directory to the location of your folder.

Change Directory Command
CD YOUR_I2B2_SRC_DIR\edu.harvard.i2b2.server-common


The change directory command shown above is written for Windows. The command itself is the same for both Linux and Windows with the only exceptions being the slashes in the path name and Linux does not include the "drive".

  • Linux Path: use a forward slash.
  • Windows Path: use a backward slash.


Linux Command:  CD /opt/i2b2/edu.harvard.i2b2.server-common
Windows Command:  CD C:\opt\i2b2\edu.harvard.i2b2.server-common

Step 2: Build the i2b2.war file

The second step in the deployment process is to run the Ant script to deploy edu.harvard.i2b2.server-common.

Select the command line that is appropriate for your environment.

Linux Run Command

ant clean dist war

Run Command

%ANT_HOME%\bin\ant.bat clean dist war


If the command %ANT_HOME% does not work it may be because you did not set your environment variables as suggested in the Requirements Chapter. If you do not wish to set this variable then you will need to replace %ANT_HOME% with the full path to your Ant directory.

Provided there were no problems running the script you will see Build Successful when the script finishes.

Step 3: Deploy the war file in Wildfly

You will need to manually copy the war file from the dist folder to /opt/wildfly-VERSION-Final/standalone/deployments/

  • No labels