This project is a complete starter project you can use to deploy a FHIR server using HAPI FHIR JPA.
Note that this project is specifically intended for end users of the HAPI FHIR JPA server module (in other words, it helps you implement HAPI FHIR, it is not the source of the library itself). If you are looking for the main HAPI FHIR project, see here: https://github.com/jamesagnew/hapi-fhir
In order to use this sample, you should have:
The easiest way to run this server is to run it directly in Maven using a built-in Jetty server. To do this, change src/main/resources/hapi.properties server_address and server.base with the values commented out as For Jetty, use this and then execute the following command:
mvn jetty:runThen, browse to the following link to use the server:
http://localhost:8080/hapi-fhir-jpaserver/
If you need to run this server on a different port (using Maven), you can change the port in the run command as follows:
mvn -Djetty.port=8888 jetty:runAnd replacing 8888 with the port of your choice.
Much of this HAPI starter project can be configured using the properties file in src/main/resources/hapi.properties. By default, this starter project is configured to use Derby as the database.
To configure the starter app to use MySQL, instead of the default Derby, update the hapi.properties file to have the following:
To configure the starter app to use PostgreSQL, instead of the default Derby, update the hapi.properties file to have the following:
Because the integration tests within the project rely on the default Derby database configuration, it is important to either explicity skip the integration tests during the build process, i.e., mvn install -DskipTests, or delete the tests altogether. Failure to skip or delete the tests once you've configured PostgreSQL for the datasource.driver, datasource.url, and hibernate.dialect as outlined above will result in build errors and compilation failure.
It is important to use PostgreSQL95Dialect when using PostgreSQL version 10+.
You can override the properties that are loaded into the compiled web app (.war file) making a copy of the hapi.properties file on the file system, making changes to it, and then setting the JAVA_OPTS environment variable on the tomcat server to tell hapi-jpaserver-starter where the overriding properties file is. For example:
-Dhapi.properties=/some/custom/directory/hapi.properties
Note: This property name and the path is case-sensitive. "-DHAPI.PROPERTIES=XXX" will not work.
The UI that comes with this server is an exact clone of the server available at http://hapi.fhir.org. You may skin this UI if you'd like. For example, you might change the introductory text or replace the logo with your own.
The UI is customized using Thymeleaf template files. You might want to learn more about Thymeleaf, but you don't necessarily need to: they are quite easy to figure out.
Several template files that can be customized are found in the following directory: https://github.com/hapifhir/hapi-fhir-jpaserver-starter/tree/master/src/main/webapp/WEB-INF/templates
Using the Maven-Embedded Jetty method above is convenient, but it is not a good solution if you want to leave the server running in the background.
Most people who are using HAPI FHIR JPA as a server that is accessible to other people (whether internally on your network or publically hosted) will do so using an Application Server, such as Apache Tomcat or Jetty. Note that any Servlet 3.0+ compatible Web Container will work (e.g Wildfly, Websphere, etc.).
Tomcat is very popular, so it is a good choice simply because you will be able to find many tutorials online. Jetty is a great alternative due to its fast startup time and good overall performance.
To deploy to a container, you should first build the project:
mvn clean installThis will create a file called hapi-fhir-jpaserver.war in your target directory. This should be installed in your Web Container according to the instructions for your particular container. For example, if you are using Tomcat, you will want to copy this file to the webapps/ directory.
Again, browse to the following link to use the server (note that the port 8080 may not be correct depending on how your server is configured).
http://localhost:8080/hapi-fhir-jpaserver/
Docker compose is a simple option to build and deploy container. To deploy with docker compose, you should build the project
with mvn clean install and then bring up the containers with docker-compose up -d --build. The server can be
reached at http://localhost:8080/hapi-fhir-jpaserver/.
In order to use another port, change the ports parameter
inside docker-compose.yml to 8888:8080, where 8888 is a port of your choice.
The docker compose set also includes my MySQL database, if you choose to use MySQL instead of derby, change the following properties in hapi.properties:
Install Tomcat.
Make sure you have Tomcat set up in IntelliJ.
Add a Run Configuration for running hapi-fhir-jpaserver-example under Tomcat
Run the configuration.
Point your browser (or fiddler, or what have you) to http://localhost:8080/hapi/baseDstu3/Patient
It is important to use MySQL5Dialect when using MySQL version 5+.
The server may be configured with subscription support by enabling properties in the hapi.properties file:
subscription.resthook.enabled - Enables REST Hook subscriptions, where the server will make an outgoing connection to a remote REST server
subscription.email.enabled - Enables email subscriptions. Note that you must also provide the connection details for a usable SMTP server.
subscription.websocket.enabled - Enables websocket subscriptions. With this enabled, your server will accept incoming websocket connections on the following URL (this example uses the default context path and port, you may need to tweak depending on your deployment environment): ws://localhost:8080/hapi-fhir-jpaserver/websocket
By default, the server will use embedded lucene indexes for terminology and fulltext indexing purposes. You can switch this to using lucene by editing the properties in hapi.properties
For example:
elasticsearch.enabled=true
elasticsearch.rest_url=http://localhost:9200
elasticsearch.username=SomeUsername
elasticsearch.password=SomePassword
elasticsearch.required_index_status=YELLOW
elasticsearch.schema_management_strategy=CREATE