Mentions légales du service

Skip to content
Snippets Groups Projects
Commit 4e2bca0a authored by Youn Cadoret's avatar Youn Cadoret
Browse files

I added the installation manual and user manual for XDSMU and RMU

parent 25d73065
No related branches found
No related tags found
No related merge requests found
SHELL := /bin/bash
include ../Makefile.generic
---
title: Installation Manual
subtitle: ATC Simulator
author: Wylem BARS
function: Software Engineer
date: 19/04/2019
toolversion: 1.1.2
version: 0.01
status: Draft
reference: KER1-MAN-IHE-ATC_SIMULATOR_INSTALLATION-0_01
customer: IHE-EUROPE
---
# ATC Simulator - Installation & configuration
## Source code
Sources of the tool are available on Inria's Gforge in the Gazelle project:
[EPD (trunk)](https://scm.gforge.inria.fr/authscm/wbars/svn/gazelle/EPD/trunk).
## Patient Audit Consumer
This project can be loaded on a Gazelle WebService tester instance. This way you will be able to launch a suite of requests from the simulator emulating
the Patient Audit Consumer actor of the CH:ATC profile.
First you need to load the project in Gazelle WebService Tester. Then, check :
* The entire project
* The NormalCases test suite
* The ErrorCases test suite
This will allow the user to either launch a specific test suite or to launch both using the entire project.
Then click on the Project name in the tree and check the __endpoint__ and __enPointAssertions__ properties. This will be useful to specify where your
system is so the simulator can request it for Audit Events.
The click on each test case from the project and check all parameters. Then the user will be able to modify the request parameters send by the simulator to match
audit event from his Patient Audit Record Repository.
## Patient Audit Record Repository
First step to set up the Patient Audit Record Repository actor from the simulator is to checkout sources.
You can checkout the entire ATC simulator sources from the url [here](https://scm.gforge.inria.fr/authscm/wbars/svn/gazelle/EPD/trunk/ATC).
For the Patient Audit Record Repository actor you will need three things :
* The SoapUI project __ATC/soapui/ATC-MockService-soapui-project.xml__
* The folder __ATC/test_data/AuditEvent__ that contains all Audit Events known by the simulator.
* The script __ATC/init.d/atcRecordRepositoryMock__ that will allow you to start/stop the mock project as a service on your platform
Once you downloaded the ATC folder, you have all the data you need to run the Patient Audit Record Repository Mockup.
Simply modify __atcRecordRepositoryMock__ script properties :
| **Property** | **Description** | **Example Value** |
|----------------------------------------------|---------------------------------------------------------|----------------------------------------------------------------------------------------------|
| SOAPUI_PATH | Path to the SoapUI folder installed on your platform| /usr/local/SmartBear/SoapUI-5.3.0|
| SOAPUI_PROJECT_PATH | Path to the SoapUI project checked out from Inria's Gforge| /opt/simulators/ATC/soapui/ATC-MockService-soapui-project.xml|
| SOAPUI_MOCK_NAME | Name of the mock | PatientAuditRecordRepository|
| SOAPUI_MOCK_PORT | Port that will be used to access the Mock| 8096|
| SOAPUI_MOCK_ENDPOINT | Endpoint that will be used to reach the Mock| /atc-record-repository |
| SOAPUI_MOCK_LOG | Path to the log file for the Mock | /var/log/soapui/epr-atc-record-repository.log|
When the properties are modified to fit your platform, you can copy the script or create a symbolic link in __/etc/init.d__ folder to be able to use start
and stop the mock as a service.
You will then be able to use following commands to respectively start the Mock service, see its status and stop the service :
```bash
sudo service atcRecordRepositoryMock start
sudo service atcRecordRepositoryMock status
sudo service atcRecordRepositoryMock stop
```
\ No newline at end of file
---
title: Release note
subtitle: ATC Simulator
toolversion: 1.1.2
releasedate: 2019-04-10
author: Wylem BARS
function: Software Engineer
customer: IHE Europe
reference: KER1-RNO-IHE-ATC_SIMULATOR
---
# 1.1.2
_Release date: 2019-04-10 _
__Bug__
* \[[ATCREPO-7](https://gazelle.ihe.net/jira/browse/ATCREPO-7)\] ATC Client simulator send "IHE- SAML" instead of "IHE-SAML"
* \[[ATCREPO-8](https://gazelle.ihe.net/jira/browse/ATCREPO-8)\] Patient Audit Record Repository response contains not all request parameters
* \[[ATCREPO-9](https://gazelle.ihe.net/jira/browse/ATCREPO-9)\] ATC Consumer endpoint include /ARRService and shouldn't
* \[[ATCREPO-10](https://gazelle.ihe.net/jira/browse/ATCREPO-10)\] & should not be escaped inside date parameter
# 1.1.1
_Release date: 2019-04-03 _
__Bug__
* \[[ATCREPO-5](https://gazelle.ihe.net/jira/browse/ATCREPO-5)\] Handling of parameter "date=ge
* \[[ATCREPO-6](https://gazelle.ihe.net/jira/browse/ATCREPO-6)\] ATC - Simulator ignores _format parameter, only responding with XML
# 1.1.0
_Release date: 2019-03-27 _
__Story__
* \[[ATCREPO-1](https://gazelle.ihe.net/jira/browse/ATCREPO-1)\] Update the mock to comply with the EPR 1.8 specification
__Improvement__
* \[[ATCREPO-2](https://gazelle.ihe.net/jira/browse/ATCREPO-2)\] Update the AuditMessage and AuditEvent messages
# 1.0.2
_Release date: 2019-02-15 _
__Bug__
* \[[ATCREPO-3](https://gazelle.ihe.net/jira/browse/ATCREPO-3)\] Mock not correctly handle request parameters
__Improvement__
* \[[ATCREPO-4](https://gazelle.ihe.net/jira/browse/ATCREPO-4)\] Replace regex with XMLHolder in assertion reading
---
title: User Manual
subtitle: ATC Simulator
author: Wylem BARS
function: Software Engineer
date: 19/01/2019
toolversion: 1.1.0
version: 0.01
status: Draft
reference: KER1-MAN-IHE-ATC_SIMULATOR_USER
customer: IHE-EUROPE
---
# Introduction
This simulator is developed in conformance with Swiss Integration profiles and IHE Technical Framework.
This simulator emulates actor from CH:ATC (Audit Trail Consumption) profile. This profile defines the audit trail consumption requirements a community
has to provide for a patient's audit trail. The profile CH:ATC defines and precises the actors and transaction [ITI-81] of the IHE IT Infrastructure
Technical Framework Supplement Add RESTful Query to ATNA 1 and defines the content of the Audit Messages. The different types of the Audit Messages are
based on the requirements for Document and Policy Access management in order to achieve the Swiss regulation needs on the audit trail access by patients.
Therefore it can act as a Patient Audit Consumer or as a Patient Audit Record Repository.
As a Patient Audit Consumer, this simulator is aimed to send messages to a Patient Audit Record Repository. Consequently, if your system (named SUT or System Under Test) is reachable from the Internet, you will be able to receive messages from the simulator.
As a Patient Audit Record Repository, this simulator can be requested Audit Events by your system.
# Patient Audit Consumer
When acting as a Patient Audit Consumer, this simulator is able to send multiple requests to your SUT to test the handling of parameters :
* date
* entity-id
* entity-role
* source
* type
* subtype
* outcome
* entity-type
* user
* address
* _format
It can also send bad requests (missing requested parameters, parameters providing no matches, etc) to test the behavior of the SUT against erroneous requests.
## How to access the Simulator ?
The simulator is accessible via Gazelle Webservice Tester. If the simulator is available on the instance of the tool, it should appear in the project list with the name **ATC_Repository**.
This name may also be followed with the version of the specification in brackets.
![ATC Simulator for Patient Audit Consumer](./media/atc_repo_gwt.png)
## How to send messages to an SUT ?
If the simulator is available on the instance of Gazelle Webservice Tester you are using, it can then be launched as any other project from the tools.
Go to **Run**. Select the **ATC_Repository** project. You will have two Test suite available. The **NormalCases** test suite will send a request to test each parameter listed earlier.
The **ErrorCases** test suite will focus on error cases.
![Run the ATC Repository Project](./media/atc_repo_run.png)
You can then chose if you want to execute one specific test suite or the entire project.
You will then be able to chose the endpoint the simulator will use, as well as the parameter from the requests that will be sent to your SUT.
![Form defining parameters to use to execute NormalCases test suite](./media/atc_repo_normal_cases.png)
Once you defined all parameters for the Simulator to send requests, simply press **Run** and it will send messages to your SUT and keep track of exchanges in an **Execution**.
This Execution can be retrieved anytime in the **Execution List** menu.
# Patient Audit Record Repository
The ATC Simulator can also simulates a CH:ATC Patient Audit Record Repository.
A **Patient Audit Consumer** queries a **Patient Audit Record Repository** for Audit Events defined by this profile.
The Patient Audit Consumer used entity-id (Patient ID) and date before/after as parameters to asked the Audit Record Repository.
In all, there are only three mandatory parameters.
There are also optional parameters : entity-type, entity-role, source, type, user, subtype, outcome and address.
Each request sent must have a security token in the header, this part is used to check access rights. In this token, two elements will be checked :
* Is the assertion valid in time ? (Time not Before in the past and Time not After in the future)
* Does the mock know the patient ID passed as a **resource-id** attribute ? If not, the mock will say you do not have the right to acces the information. The list of available patient ID is displayed below.
## Data Set
###Token Security
Here are the ID to put in the SAML token in **resource-id** attribute.
If you query any other patient id, the mock will respond with an error message saying that you are not authorized to access information related to the given patient ID.
|**resource-id**|
|-------------|
|761337610430891416^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO|
|761337610423590456^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO|
|761337610435209810^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO|
|761337610436974489^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO|
### AuditEvent
Here are all couples of Dates/PatientID to effectively access audit events.
However, using optional parameters can lead you to no Audit event returned, even with those date and patient ID.
Indeed, if the events does not match even one of the optional parameters, the audit event will not be returned by the ATC Mock.
|**Patient ID**|**Dates**|
|--------------|----------|
|urn:oid:2.16.756.5.30.1.127.3.10.3|761337610430891416| ge2015-01-01 / le2020-01-01|
|urn:oid:2.16.756.5.30.1.127.3.10.3|761337610435209810|ge2015-01-01 / le2017-01-01|
|urn:oid:2.16.756.5.30.1.127.3.10.3|761337610436974489|ge2017-01-01 / le2019-01-01|
## End Point
Here are the endpoints to use to send your request to the Patient Audit Record Repository simulator :
* [http://ehealthsuisse.ihe-europe.net:8096/atc-record-repository?wadl](https://ehealthsuisse.ihe-europe.net/atc-record-repository.wadl)
* [https://ehealthsuisse.ihe-europe.net:10443/atc-record-repository?wadl](https://ehealthsuisse.ihe-europe.net/simu/atc-record-repository.wadl)
It requires TLS mutual authentication with testing certificate (from GSS PKI).
##ATC URI example
Here is an example URI for a requets on patient with ID **761337610430891416^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO** looking for audit events between
**2015-01-01** and **2020-01-01**
```
http://ehealthsuisse.ihe-europe.net:8096/atc-record-repository/ARRservice/AuditEvent?date=ge2015-01-00&date=le2020-01-00&entity-id=urn:oid:2.16.756.5.30.1.127.3.10.3|761337610430891416
```
SHELL := /bin/bash
include ../Makefile.generic
---
title: User Manual
subtitle: RMU & XDSMU Simulator
author: Youn Cadoret
function: Developer
date: 28/06/2019
toolversion: 1.1.0
version: 0.01
status: to be reviewed
reference: KER1-MAN-IHE-RMU_SIMULATOR_INSTALLATION_USER
customer: IHE-EUROPE
---
# EPR RMU MockUp
## Overview
The RMU MockUp is a SoapUI webservice (mock) that provides Cross-Gateway Update Document Set [ITI-X1] Response. This mock requires that the Update Metadata Registry MockUp is started.
* default_wsdl_url: http://ehealthsuisse.ihe-europe.net:8095/xcmu-responding-gateway?wsdl
* default_path: /xcmu-responding-gateway
* default_port: 8095
* default_mock_name: RespondingGateway_Binding_Soap12 MockService
* default_mock_path: /opt/simulators/epr-xcmu-responding-gateway-mockup
* default_soapui_path: /usr/local/SmartBear/SoapUI-5.3.0/
* default_soapui_mock_log: /var/log/soapui/epr-xcmu-responding-gateway.log
* default_init.d: /etc/init.d/xcmuRespondingGatewayMock
* default_keystore_path: /opt/gazelle/cert/jboss.jks
## Install SoapUI
[https://www.soapui.org/](https://www.soapui.org/)
## Install EPR RMU MockUp
### Get the git project
```bash
git clone https://gitlab.inria.fr/gazelle/specific-tools/epr/metadata-update-responders.git $EPR_XCMU_MOCK_DIR
```
## Mock as a service
### Prepare the init.d script
Edit the init.d scripts `$EPR_XCMU_MOCK_DIR/init.d/xcmuRespondingGatewayMock` and set the following environment variables
* SOAPUI_PATH => Path of SoapUI folder
* SOAPUI_PROJECT_PATH => Path of SoapUI project script
* SOAPUI_MOCK_NAME => Name of the SoapUI mock
* SOAPUI_MOCK_PORT => Port of the SoapUI mock
* SOAPUI_MOCK_ENDPOINT => Path of the SoapUI mock
* SOAPUI_MOCK_LOG => Path where to publish log file
### Declare the service
Type the following commands register the init.d script as service
```bash
sudo cp $EPR_XCMU_MOCK_DIR/init.d/xcmuRespondingGatewayMock /etc/init.d/xcmuRespondingGatewayMock
sudo chmod u+x /etc/init.d/xcmuRespondingGatewayMock
sudo chmod 775 /etc/init.d/xcmuRespondingGatewayMock
```
If you want the service to start at each machine start up
```bash
sudo update-rc.d xcmuRespondingGatewayMock defaults
```
Be careful to allow the service to write logs into your target directory. As example
```bash
sudo mkdir /var/log/soapui
sudo chmod 775 /var/log/soapui
```
### Start the mock
To run the mock
```bash
sudo /etc/init.d/xcmuRespondingGatewayMock start
```
To stop the mock
```bash
sudo /etc/init.d/xcmuRespondingGatewayMock stop
```
To get status of the mock
```bash
sudo /etc/init.d/xcmuRespondingGatewayMock status
```
## Troubleshouting
You might need to install those following packets
```bash
sudo apt-get install -y libxrender1 libxtst6 libxi6
```
You might need to resolve errors when starting the mock
```bash
sudo mv /root/.soapuios/ /root/.soapuios_old
```
# EPR ITI-18 Registry Stored Query MockUp
## Overview
The ITI-18 Registry Stored Query MockUp is a SoapUI webservice (mock) that provides Registry Stored Query [ITI-18] Response.
* default_wsdl_url: http://ehealthsuisse.ihe-europe.net:8093/registry-stored-query?wsdl
* default_path: /registry-stored-query
* default_port: 8093
* default_mock_name: DocumentRegistry_Binding_Soap11 MockService
* default_mock_path: /opt/simulators/epr-xcmu-responding-gateway-mockup
* default_soapui_path: /usr/local/SmartBear/SoapUI-5.3.0/
* default_soapui_mock_log: /var/log/soapui/epr-registry-stored-query.log
* default_init.d: /etc/init.d/RegistryStoredQueryMock
* default_keystore_path: /opt/gazelle/cert/jboss.jks
## Install SoapUI
[https://www.soapui.org/](https://www.soapui.org/)
## Install EPR Assertion Provider MockUp
### Get the git project
```bash
git clone https://gitlab.inria.fr/gazelle/specific-tools/epr/metadata-update-responders.git $EPR_XCMU_MOCK_DIR
```
## Mock as a service
### Prepare the init.d script
Edit the init.d scripts `$EPR_XCMU_MOCK_DIR/init.d/RegistryStoredQueryMock` and set the following environment variables
* SOAPUI_PATH => Path of SoapUI folder
* SOAPUI_PROJECT_PATH => Path of SoapUI project script
* SOAPUI_MOCK_NAME => Name of the SoapUI mock
* SOAPUI_MOCK_PORT => Port of the SoapUI mock
* SOAPUI_MOCK_ENDPOINT => Path of the SoapUI mock
* SOAPUI_MOCK_LOG => Path where to publish log file
### Declare the service
Type the following commands register the init.d script as service
```bash
sudo cp $EPR_XCMU_MOCK_DIR/init.d/RegistryStoredQueryMock /etc/init.d/RegistryStoredQueryMock
sudo chmod u+x /etc/init.d/RegistryStoredQueryMock
sudo chmod 775 /etc/init.d/RegistryStoredQueryMock
```
If you want the service to start at each machine start up
```bash
sudo update-rc.d RegistryStoredQueryMock defaults
```
Be careful to allow the service to write logs into your target directory. As example
```bash
sudo mkdir /var/log/soapui
sudo chmod 775 /var/log/soapui
```
### Start the mock
To run the mock
```bash
sudo /etc/init.d/RegistryStoredQueryMock start
```
To stop the mock
```bash
sudo /etc/init.d/RegistryStoredQueryMock stop
```
To get status of the mock
```bash
sudo /etc/init.d/RegistryStoredQueryMock status
```
## Troubleshouting
You might need to install those following packets
```bash
sudo apt-get install -y libxrender1 libxtst6 libxi6
```
You might need to resolve errors when starting the mock
```bash
sudo mv /root/.soapuios/ /root/.soapuios_old
```
# EPR ITI-57 Update Metadata Set MockUp
## Overview
The ITI-57 Update Metadata Set MockUp is a SoapUI webservice (mock) that provides Update Document Set [ITI-57] Response.
* default_wsdl_url: http://ehealthsuisse.ihe-europe.net:8094/update-document-set?wsdl
* default_path: /update-document-set
* default_port: 8094
* default_mock_name: DocumentRegistry_Binding_Soap12 MockService
* default_mock_path: /opt/simulators/epr-xcmu-responding-gateway-mockup
* default_soapui_path: /usr/local/SmartBear/SoapUI-5.3.0/
* default_soapui_mock_log: /var/log/soapui/epr-update-document-set.log
* default_init.d: /etc/init.d/UpdateMetadataSetMock
* default_keystore_path: /opt/gazelle/cert/jboss.jks
## Install SoapUI
[https://www.soapui.org/](https://www.soapui.org/)
## Install EPR Assertion Provider MockUp
### Get the Git project
```bash
git clone https://gitlab.inria.fr/gazelle/specific-tools/epr/metadata-update-responders.git $EPR_XCMU_MOCK_DIR
```
## Mock as a service
### Prepare the init.d script
Edit the init.d scripts `$EPR_XCMU_MOCK_DIR/init.d/xcmuRespondingGatewayMock` and set the following environment variables
* SOAPUI_PATH => Path of SoapUI folder
* SOAPUI_PROJECT_PATH => Path of SoapUI project script
* SOAPUI_MOCK_NAME => Name of the SoapUI mock
* SOAPUI_MOCK_PORT => Port of the SoapUI mock
* SOAPUI_MOCK_ENDPOINT => Path of the SoapUI mock
* SOAPUI_MOCK_LOG => Path where to publish log file
### Declare the service
Type the following commands register the init.d script as service
```bash
sudo cp $EPR_XCMU_MOCK_DIR/init.d/UpdateMetadataSetMock /etc/init.d/UpdateMetadataSetMock
sudo chmod u+x /etc/init.d/UpdateMetadataSetMock
sudo chmod 775 /etc/init.d/UpdateMetadataSetMock
```
If you want the service to start at each machine start up
```bash
sudo update-rc.d UpdateMetadataSetMock defaults
```
Be careful to allow the service to write logs into your target directory. As example
```bash
sudo mkdir /var/log/soapui
sudo chmod 775 /var/log/soapui
```
### Start the mock
To run the mock
```bash
sudo /etc/init.d/UpdateMetadataSetMock start
```
To stop the mock
```bash
sudo /etc/init.d/UpdateMetadataSetMock stop
```
To get status of the mock
```bash
sudo /etc/init.d/UpdateMetadataSetMock status
```
## Troubleshouting
You might need to install those following packets
```bash
sudo apt-get install -y libxrender1 libxtst6 libxi6
```
You might need to resolve errors when starting the mock
```bash
sudo mv /root/.soapuios/ /root/.soapuios_old
```
This diff is collapsed.
SHELL := /bin/bash
include ../Makefile.generic
---
title: User Manual
subtitle: RMU & XDSMU Simulator
author: Youn Cadoret
function: Developer
date: 28/06/2019
toolversion: 1.1.0
version: 0.01
status: to be reviewed
reference: KER1-MAN-IHE-XDSMU_SIMULATOR_INSTALLATION_USER
customer: IHE-EUROPE
---
# EPR RMU MockUp
## Overview
The RMU MockUp is a SoapUI webservice (mock) that provides Cross-Gateway Update Document Set [ITI-X1] Response. This mock requires that the Update Metadata Registry MockUp is started.
* default_wsdl_url: http://ehealthsuisse.ihe-europe.net:8095/xcmu-responding-gateway?wsdl
* default_path: /xcmu-responding-gateway
* default_port: 8095
* default_mock_name: RespondingGateway_Binding_Soap12 MockService
* default_mock_path: /opt/simulators/epr-xcmu-responding-gateway-mockup
* default_soapui_path: /usr/local/SmartBear/SoapUI-5.3.0/
* default_soapui_mock_log: /var/log/soapui/epr-xcmu-responding-gateway.log
* default_init.d: /etc/init.d/xcmuRespondingGatewayMock
* default_keystore_path: /opt/gazelle/cert/jboss.jks
## Install SoapUI
[https://www.soapui.org/](https://www.soapui.org/)
## Install EPR RMU MockUp
### Get the git project
```bash
git clone https://gitlab.inria.fr/gazelle/specific-tools/epr/metadata-update-responders.git $EPR_XCMU_MOCK_DIR
```
## Mock as a service
### Prepare the init.d script
Edit the init.d scripts `$EPR_XCMU_MOCK_DIR/init.d/xcmuRespondingGatewayMock` and set the following environment variables
* SOAPUI_PATH => Path of SoapUI folder
* SOAPUI_PROJECT_PATH => Path of SoapUI project script
* SOAPUI_MOCK_NAME => Name of the SoapUI mock
* SOAPUI_MOCK_PORT => Port of the SoapUI mock
* SOAPUI_MOCK_ENDPOINT => Path of the SoapUI mock
* SOAPUI_MOCK_LOG => Path where to publish log file
### Declare the service
Type the following commands register the init.d script as service
```bash
sudo cp $EPR_XCMU_MOCK_DIR/init.d/xcmuRespondingGatewayMock /etc/init.d/xcmuRespondingGatewayMock
sudo chmod u+x /etc/init.d/xcmuRespondingGatewayMock
sudo chmod 775 /etc/init.d/xcmuRespondingGatewayMock
```
If you want the service to start at each machine start up
```bash
sudo update-rc.d xcmuRespondingGatewayMock defaults
```
Be careful to allow the service to write logs into your target directory. As example
```bash
sudo mkdir /var/log/soapui
sudo chmod 775 /var/log/soapui
```
### Start the mock
To run the mock
```bash
sudo /etc/init.d/xcmuRespondingGatewayMock start
```
To stop the mock
```bash
sudo /etc/init.d/xcmuRespondingGatewayMock stop
```
To get status of the mock
```bash
sudo /etc/init.d/xcmuRespondingGatewayMock status
```
## Troubleshouting
You might need to install those following packets
```bash
sudo apt-get install -y libxrender1 libxtst6 libxi6
```
You might need to resolve errors when starting the mock
```bash
sudo mv /root/.soapuios/ /root/.soapuios_old
```
# EPR ITI-18 Registry Stored Query MockUp
## Overview
The ITI-18 Registry Stored Query MockUp is a SoapUI webservice (mock) that provides Registry Stored Query [ITI-18] Response.
* default_wsdl_url: http://ehealthsuisse.ihe-europe.net:8093/registry-stored-query?wsdl
* default_path: /registry-stored-query
* default_port: 8093
* default_mock_name: DocumentRegistry_Binding_Soap11 MockService
* default_mock_path: /opt/simulators/epr-xcmu-responding-gateway-mockup
* default_soapui_path: /usr/local/SmartBear/SoapUI-5.3.0/
* default_soapui_mock_log: /var/log/soapui/epr-registry-stored-query.log
* default_init.d: /etc/init.d/RegistryStoredQueryMock
* default_keystore_path: /opt/gazelle/cert/jboss.jks
## Install SoapUI
[https://www.soapui.org/](https://www.soapui.org/)
## Install EPR Assertion Provider MockUp
### Get the git project
```bash
git clone https://gitlab.inria.fr/gazelle/specific-tools/epr/metadata-update-responders.git $EPR_XCMU_MOCK_DIR
```
## Mock as a service
### Prepare the init.d script
Edit the init.d scripts `$EPR_XCMU_MOCK_DIR/init.d/RegistryStoredQueryMock` and set the following environment variables
* SOAPUI_PATH => Path of SoapUI folder
* SOAPUI_PROJECT_PATH => Path of SoapUI project script
* SOAPUI_MOCK_NAME => Name of the SoapUI mock
* SOAPUI_MOCK_PORT => Port of the SoapUI mock
* SOAPUI_MOCK_ENDPOINT => Path of the SoapUI mock
* SOAPUI_MOCK_LOG => Path where to publish log file
### Declare the service
Type the following commands register the init.d script as service
```bash
sudo cp $EPR_XCMU_MOCK_DIR/init.d/RegistryStoredQueryMock /etc/init.d/RegistryStoredQueryMock
sudo chmod u+x /etc/init.d/RegistryStoredQueryMock
sudo chmod 775 /etc/init.d/RegistryStoredQueryMock
```
If you want the service to start at each machine start up
```bash
sudo update-rc.d RegistryStoredQueryMock defaults
```
Be careful to allow the service to write logs into your target directory. As example
```bash
sudo mkdir /var/log/soapui
sudo chmod 775 /var/log/soapui
```
### Start the mock
To run the mock
```bash
sudo /etc/init.d/RegistryStoredQueryMock start
```
To stop the mock
```bash
sudo /etc/init.d/RegistryStoredQueryMock stop
```
To get status of the mock
```bash
sudo /etc/init.d/RegistryStoredQueryMock status
```
## Troubleshouting
You might need to install those following packets
```bash
sudo apt-get install -y libxrender1 libxtst6 libxi6
```
You might need to resolve errors when starting the mock
```bash
sudo mv /root/.soapuios/ /root/.soapuios_old
```
# EPR ITI-57 Update Metadata Set MockUp
## Overview
The ITI-57 Update Metadata Set MockUp is a SoapUI webservice (mock) that provides Update Document Set [ITI-57] Response.
* default_wsdl_url: http://ehealthsuisse.ihe-europe.net:8094/update-document-set?wsdl
* default_path: /update-document-set
* default_port: 8094
* default_mock_name: DocumentRegistry_Binding_Soap12 MockService
* default_mock_path: /opt/simulators/epr-xcmu-responding-gateway-mockup
* default_soapui_path: /usr/local/SmartBear/SoapUI-5.3.0/
* default_soapui_mock_log: /var/log/soapui/epr-update-document-set.log
* default_init.d: /etc/init.d/UpdateMetadataSetMock
* default_keystore_path: /opt/gazelle/cert/jboss.jks
## Install SoapUI
[https://www.soapui.org/](https://www.soapui.org/)
## Install EPR Assertion Provider MockUp
### Get the Git project
```bash
git clone https://gitlab.inria.fr/gazelle/specific-tools/epr/metadata-update-responders.git $EPR_XCMU_MOCK_DIR
```
## Mock as a service
### Prepare the init.d script
Edit the init.d scripts `$EPR_XCMU_MOCK_DIR/init.d/xcmuRespondingGatewayMock` and set the following environment variables
* SOAPUI_PATH => Path of SoapUI folder
* SOAPUI_PROJECT_PATH => Path of SoapUI project script
* SOAPUI_MOCK_NAME => Name of the SoapUI mock
* SOAPUI_MOCK_PORT => Port of the SoapUI mock
* SOAPUI_MOCK_ENDPOINT => Path of the SoapUI mock
* SOAPUI_MOCK_LOG => Path where to publish log file
### Declare the service
Type the following commands register the init.d script as service
```bash
sudo cp $EPR_XCMU_MOCK_DIR/init.d/UpdateMetadataSetMock /etc/init.d/UpdateMetadataSetMock
sudo chmod u+x /etc/init.d/UpdateMetadataSetMock
sudo chmod 775 /etc/init.d/UpdateMetadataSetMock
```
If you want the service to start at each machine start up
```bash
sudo update-rc.d UpdateMetadataSetMock defaults
```
Be careful to allow the service to write logs into your target directory. As example
```bash
sudo mkdir /var/log/soapui
sudo chmod 775 /var/log/soapui
```
### Start the mock
To run the mock
```bash
sudo /etc/init.d/UpdateMetadataSetMock start
```
To stop the mock
```bash
sudo /etc/init.d/UpdateMetadataSetMock stop
```
To get status of the mock
```bash
sudo /etc/init.d/UpdateMetadataSetMock status
```
## Troubleshouting
You might need to install those following packets
```bash
sudo apt-get install -y libxrender1 libxtst6 libxi6
```
You might need to resolve errors when starting the mock
```bash
sudo mv /root/.soapuios/ /root/.soapuios_old
```
This diff is collapsed.
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment