Building OpenEMPI from Source
This page describes how to build OpenEMPI starting from the source code that is stored in the Subversion repository. These instructions were developed on an Ubuntu machine so they follow the Unix conventions but since all the built tools used for OpenEMPI are platform independent, the same instructions should work equally well for other platforms. Where there are differences between building on Windows versus Unix, we try to point out those differences. As always, if you come up across something that is not clear or does not well as advertised on your platform, don't hesitate to let us know by raising an issue, posting a message on the forum, or better yet, providing a fix for it.
Get the Source from Subversion
The assumption that we make here is that you have a Subversion client on your platform. In our Ubuntu box getting the latest version of svn is as simply as running the following command:
sudo apt-get install subversion
If you need more helping in getting an svn client on your machine or installation instruction for different platforms, we won't duplicate the effort of others. You can get more information from the
You should then change directories to the location on your machine where you want to extract a copy of the source code. The URL for the svn repository is:
https://svn.kenai.com/svn/openempi~source-repository
To check-out the trunk from the repository into the subdirectory openempi simply use the svn co command:
svn co https://svn.kenai.com/svn/openempi~source-repository/trunk openempi
If you want to work on a specific branch or tag you just need to change the URL. For example, to work on the 2.0.5 development branch and name the directory appropriately so you can differentiate it from another branch or the trunk, the check-out command is:
svn co https://svn.kenai.com/svn/openempi~source-repository/branches/2.0.5-development openempi-2.0.5-development
Either way, you should start seeing the source files being downloaded to your machine:
A openempi-2.0.5-development/documents A openempi-2.0.5-development/documents/OS-CDE_Data_Model
At this point you should have a complete copy of the latest source code.
Build the source code using Maven
OpenEMPI uses maven as the build tool. If you are not familiar with maven you can get more information about it from . The precise definition of Maven from its Apache site is:
Apache Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information.
We currently use version 2.0.9 of maven but we have also tested other more recent versions of it with no problems. You can download the latest version or the appropriate release for your platform from: . Installation instructions more maven are available from its home site.
Building the source code should be as easy as going to the root of the source code and running maven. Assuming that you checked out the entire source tree in the openempi directory, change to openempi/openempi and run the install goal. For the rest of these instructions we will assume that you downloaded the source code into the openempi directory.
mvn install
or if you want to skip running the tests you can ignore them by doing the following:
mvn -Dmaven.test.skip=true install
As of release 2.0.4, the PIX/PDQ adapter requires two artifacts that are not available through a public repository yet. This will generate an error message while building the source code that will look as follows:
Missing: ---------- 1) org.openhealthexchange.openpixpdq:openpixpdq:jar:1.1 2) com.misys.hieportal.sysmon:eventmonitoring:jar:1.0
At this point the easiest option is to add our temporary maven repository to your root pom file. To do that, open the file pom.xml in the openempi/openempi directory and in the section that lists the various repositories, add the following entry as the last entry in the list (you will find an entry with id openxds so this new entry should follow that one):
<repository>
<id>sysnetint</id>
<url>http://sysnetintrepo.com/repository</url>
</repository>
You will also need to add this repository to the plugin repositories section:
<pluginRepositories>
<repository>
<id>sysnetint</id>
<url>http://sysnetintrepo.com/repository</url>
</repository>
</pluginRepositories>
The build should be successful at this point and you should have all the targets ready for deployment.
To deploy the war file that includes the core OpenEMPI solution as well as the web-based administration client, you can go to the openempi/openempi/webapp-web directory and use maven to deploy the war file to the JBoss server. Assuming that your JBoss instance is up and running and listening on the default ports, you just need to execute the jboss:deploy maven target.
