 |
Page History
...
The URI Resolver Service comes with a set of default configurations that can allow for easy setup, customization . 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:
...
| Info |
|---|
This application can be built and run in Java 1.6 by changing the java Java source and target values from 1.7 to 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:at Installing the URI Resolver
| Multiexcerpt include | ||||||
|---|---|---|---|---|---|---|
|
Custom Installation Options
...
Custom data base configurations are handled in the preceding link.
Properties File Path
Build Time Property File Path Instructions
...
Users can replace all instances of the variable
| Code Block |
|---|
#{ systemProperties['user.home']} |
value with any custom file path desired, then build the Resolver as detailed aboveat Installing the URI Resolver.
Deployment Time Property File Path Instructions
Otherwise, users can add a property to the tomcat 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 adding this value to the setenv.sh script in the tomcat Tomcat root/bin directory. If no such file exists, then one can be created.
| Wiki Markup |
|---|
{scrollabr:icons=false} |
