Introduction

Proxy is the part of the Gazelle testbed which is used to capture the messages exchanged between two systems under test. This tool is also bind to the EVSClient in order to validate the messages stored in the Proxy in a very simple way.

As for the other tools, the proxy is an open source project and its sources are available at https://gitlab.inria.fr/gazelle/applications/test-execution/gazelle-proxy.git.
You can download the latest gazelle-proxy.ear in nexus http://gazelle.ihe.net/nexus/index.html#nexus-search;quick~gazelle-proxy.ear

Compilation and installation

Gazelle testbed tools are built using Maven 3, when you have download the sources, go to the gazelle-proxy folder and execute

mvn -P public clean package

You will get an EAR in the gazelle-proxy-ear/target folder.

Then, follow the instructions below:

1. Create database

In your database (postgresql 9.1 or higher) create a database named “gazelle-proxy”, using UTF-8 encoding and owned by the user gazelle

createdb -U gazelle -E UTF8 gazelle-proxy

2. On your file system, create a directory /opt/proxy/DICOM and an empty file /opt/proxy/proxyPersistentChannels.csv

sudo mkdir -p /opt/proxy/DICOM
sudo touch /opt/proxy/proxyPersistentChannels.csv
sudo chown -R jboss:jboss-admin /opt/proxy
sudo chmod -R 775 /opt/proxy

3. Put the ear in the deploy folder of your Jboss AS

cp gazelle-proxy-ear/target/gazelle-proxy.ear /usr/local/jboss7/standalone/deployments/gazelle-proxy.ear

4. Manage datasource

[WARNING] : From version 4.7.0, datasources have been extracted from the ear. The template file can be found in /src/main/application/datasource in the source or in the file gazelle-proxy-X.X.X-datasource.zip from the nexus. For more information about how to manage that externalization, please refer to general considerations for JBoss7.

• Datasource name : gazelle-proxyDS

• Database name : gazelle-proxy

5. Configure SSO registration

Since version 5.1.0, Proxy can register itself as a client of a SSO server. This is done by giving some environment variables to the application.

[WARNING] There are additional required variables for registration of the proxy to the SSO server. Please refer to the README.md in sso-client-v7.

6. Start Jboss AS 7

sudo /etc/init.d/jboss7 start

7. Execute the sql script available in your workspace at gazelle-proxy-ear/src/main/sql/schema-X.X.X.sql

psql -U gazelle gazelle-proxy < schema-X.X.X.sql

8. Execute the sql script available in your workspace at gazelle-proxy-ear/src/main/sql/init-5.0.0.sql

psql -U gazelle gazelle-proxy < init-X.X.X.sql

9. Browse the application

Open a browser and go to http://yourServer:8080/proxy

10. The proxy is now up and running, see the next section for information on the configuration.

This new instance of the proxy is running without the CAS feature, that means that anyone accessing the tool has the administrator privileges.

If you rather want to use a single-sign one authentication, configure the application in this way. Edit the preference application_works_without_cas to set it to false.

Called tools

Check that dcmtk is installed on the machine. Actually, the proxy uses dcmdump to render the dicom files.

sudo apt get install dcmtk

Configuration

There is a set of properties that you can configure on the Configuration page, the table below describes the various properties defined and their default values.