The Value Set Service (VSS) is responsible for Managing sensitive categories, code systems, value sets and coded concepts. The VSS also provides a RESTful service to map coded concepts to respective sensitive categories and provide the list of all sensitive categories available in the system.
- Oracle Java JDK 8 with Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy
- Docker Engine (for building a Docker image from the project)
This is a Maven project and requires Apache Maven 3.3.3 or greater to build it. It is recommended to use the Maven Wrapper scripts provided with this project. Maven Wrapper requires an internet connection to download Maven and project dependencies for the very first build.
To build the project, navigate to the folder that contains the parent pom.xml file using the terminal/command line.
- To build a JAR:
- For Windows, run
mvnw.cmd clean install - For *nix systems, run
mvnw clean install
- For Windows, run
- To build a Docker Image (this will create an image with
bhitsdev/vss:latesttag):- For Windows, run
mvnw.cmd clean install & cd web & ..\mvnw.cmd clean package docker:build & cd.. - For *nix systems, run
mvnw clean install; cd ./web; ../mvnw clean package docker:build; cd ..
- For Windows, run
This project uses MySQL for persistence and Flyway for database migration. It requires having a database user account with Object and DDL Rights to a schema with the default name vss. Please see Configure section for details of configuring the data source.
A SQL file is provided with this project to populate the database with sample value set data.
This is a Spring Boot project and serves the project via an embedded Tomcat instance. Therefore, there is no need for a separate application server to run this service.
- Run as a JAR file:
java -jar vss-x.x.x-SNAPSHOT.jar <additional program arguments> - Run as a Docker Container:
docker run -d bhitsdev/vss:latest <additional program arguments>
NOTE: In order for this Service to fully function as a microservice in the Consent2Share application, it is required to setup the dependency microservices and the support level infrastructure. Please refer to the Consent2Share Deployment Guide in the corresponding Consent2Share release (see Consent2Share Releases Page) for instructions to setup the Consent2Share infrastructure.
This project utilizes Configuration Server which is based on Spring Cloud Config to manage externalized configuration, which is stored in a Configuration Data Git Repository. We provide a Default Configuration Data Git Repository.
This project can run with the default configuration, which is targeted for a local development environment. Default configuration data is from three places: bootstrap.yml, application.yml, and the data which Configuration Server reads from Configuration Data Git Repository. Both bootstrap.yml and application.yml files are located in the resources folder of this source code.
We recommend overriding the configuration as needed in the Configuration Data Git Repository, which is used by the Configuration Server.
Also, please refer to Spring Cloud Config Documentation to see how the config server works, Spring Boot Externalized Configuration documentation to see how Spring Boot applies the order to load the properties, and Spring Boot Common Properties documentation to see the common properties used by Spring Boot.
java -jar vss-x.x.x-SNAPSHOT.jar --server.port=80 --spring.datasource.password=strongpassword
-
docker run -d bhitsdev/vss:latest --server.port=80 --spring.datasource.password=strongpassword -
In a
docker-compose.yml, this can be provided as shown below:
version: '2'
services:
...
vss.c2s.com:
image: "bhitsdev/vss:latest"
command: ["--server.port=80","--spring.datasource.password=strongpassword"]
...NOTE: Please note that these additional arguments will be appended to the default ENTRYPOINT specified in the Dockerfile unless the ENTRYPOINT is overridden.
For simplicity in development and testing environments, SSL is NOT enabled by default configuration. SSL can easily be enabled following the examples below:
java -jar vss-x.x.x-SNAPSHOT.jar --spring.profiles.active=ssl --server.ssl.key-store=/path/to/ssl_keystore.keystore --server.ssl.key-store-password=strongkeystorepassword
docker run -d -v "/path/on/dockerhost/ssl_keystore.keystore:/path/to/ssl_keystore.keystore" bhitsdev/vss:latest --spring.profiles.active=ssl --server.ssl.key-store=/path/to/ssl_keystore.keystore --server.ssl.key-store-password=strongkeystorepassword- In a
docker-compose.yml, this can be provided as follows:
version: '2'
services:
...
vss.c2s.com:
image: "bhitsdev/vss:latest"
command: ["--spring.profiles.active=ssl","--server.ssl.key-store=/path/to/ssl_keystore.keystore", "--server.ssl.key-store-password=strongkeystorepassword"]
volumes:
- /path/on/dockerhost/ssl_keystore.keystore:/path/to/ssl_keystore.keystore
...NOTE: As seen in the examples above, /path/to/ssl_keystore.keystore is made available to the container via a volume mounted from the Docker host running this container.
Java has a default CA Certificates Store that allows it to trust well-known certificate authorities. For development and testing purposes, one might want to trust additional self-signed certificates. In order to override the default Java CA Certificates Store in a Docker container, one can mount a custom cacerts file over the default one in the Docker image as follows: docker run -d -v "/path/on/dockerhost/to/custom/cacerts:/etc/ssl/certs/java/cacerts" bhitsdev/vss:latest
NOTE: The cacerts references given in the volume mapping above are files, not directories.
If you have any questions, comments, or concerns please see Consent2Share project site.
Please use GitHub Issues page to report issues.