 |
Page History
The URI Resolver Service comes with a set of default configurations that can allow for easy setup, customization for various database configurations and file systems is possible however
| Table of Contents |
|---|
Prerequisites
MySQL 5.1.x
Maven 3.0.x
Tomcat 7.x
Git 1.7.7.5
Java 1.7
Build Instructions
Clone the URI Resolver project using:
| Code Block |
|---|
git clone https://github.com/NCIP/URI_Resolver.git |
Change to the URI_Resolver directory:
| Code Block |
|---|
cd URI_Resolver |
Change to the 6.1 branch:
| Code Block |
|---|
git checkout tags/qa_v0.0.1.rc8.05.2013 |
Build the application with Maven:
| Code Block |
|---|
mvn clean install |
| Info |
|---|
This application can be built and run in Java 1.6 by changing the java source and target values from 1.7 to 1.6 in the pom.xml file |
If the build is successful then the resulting war file will be in the target directory
Default Installation
Default installations of the war file can be handled as detailed here:
Custom Installation Options
Data Base
Custom data base configurations are handled in the preceding link
Properties File Path
Build Time Property File Path Instructions
Paths to property files are hard coded in the Beans.xml file located in the src/main/resource folder.
Users can replace all instances the variable
| Code Block |
|---|
#{ systemProperties['user.home']} |
value with any custom file path desired, then build the Resolver as detailed above.
Deployment Time Property File Path Instructions
Otherwise, users can add a property to the tomcat start up script such as
| Code Block |
|---|
-Duser.home=/my/custom/path |
and do so at deployment time.
This can be done by add this value to the setenv.sh script in the tomcat root/bin directory. If no such file exists, then one can be created.
