Introduction

This guide details the process for configuring the Structured Data Capture Conformance Tool (SDCCT).

 

Installing the sdcct-web-gateway Debian Package

If you followed the Source Build Guide to build SDCCT, a Debian package will be created in ~/sdcct/sdcct-web-gateway/target/sdcct-web-gateway_<version#>~<timestamp>_all.deb. To install sdcct-web-gateway, run:
dpkg --install sdcct-web-gateway_<version#>~<timestamp>_all.deb

To start the sdcct-web-gateway service, run:

service sdcct-web-gateway start

Overriding Properties

By default, the sdcct-web-gateway service binds to port 10080. This port can be changed by overriding the sdcct.tomcat.server.port.http property in the sdcct-web.properties file. This can be done by creating an sdcct-web-override.properties file in /etc/sdcct-web-gateway/META-INF/sdcct and including the specified property with a new port.

The /META-INF/sdcct directory needs to be created in /etc/sdcct-web-gateway. Other properties can be overriden in a similar fashion in sdcct-web-override.properties, including optional proxy configuration and setting the context path for the Tomcat server. Other Spring properties and beans in XML files from the source code can also be overridden following a similar approach.

Configuration with an HTTP Proxy Server

If configuring sdcct-web-gateway to work behind an HTTP proxy server like Apache HTTPD, the proxy server configuration should include setting the "Access-Control-Allow-Origin" header to allow any origin to access returned resources and support tunneling of web socket connections to the Tomcat server.

  • No labels