diff --git a/Assertion-Manager/installation.md b/Assertion-Manager/installation.md
index 6e862a2a5f737a7a94379ddcb61fbce7465fcf78..e0cff396f46984ec2d73b5b593becee7a66cda92 100755
--- a/Assertion-Manager/installation.md
+++ b/Assertion-Manager/installation.md
@@ -6,13 +6,13 @@ function: Engineer
date: 17/01/2023
toolversion: 4.2.x
version: 1.02
-status: Approved document
+status: draft
reference: KER1-MAN-IHE-ASSERTION\_MANAGER\_INSTALLATION-1\_02
customer: IHE-EUROPE
---
# Purpose
-Here is a guide to help you installing Assertion Manager.
+Here is a guide to help you to install Assertion Manager.
# Minimal Requirements
@@ -24,21 +24,28 @@ Here is a guide to help you installing Assertion Manager.
To install those requirements you can refer to the documentation of installation of JBoss : [*General Requirements JBOSS 7*](https://gazelle.ihe.net/gazelle-documentation/General/jboss7.html)
-# Quick start
+## Sources & binaries
-Assertion manager has to be installed as a gazelle user on your server:
+Assertions Manager is an open-source project under Apache License Version 2.0 ([https://gazelle.ihe.net/content/license](https://gazelle.ihe.net/content/license)). Sources are available via Gitlab at [https://gitlab.inria.fr/gazelle/applications/test-design/AssertionManager](https://gitlab.inria.fr/gazelle/applications/test-design/AssertionManager).
+
+The latest public packaged release can be downloaded from our Nexus repository [https://gazelle.ihe.net/nexus/#nexus-search;quick~%20AssertionManagerGui.ear](https://gazelle.ihe.net/nexus/#nexus-search;quick~%20AssertionManagerGui.ear).
+
+
+### Database creation
+
+Your database must have a user **gazelle** :
+
+1. Connect to your database
```bash
-wget https://gitlab.inria.fr/gazelle/applications/test-design/AssertionManager/blob/master/install_assertion_manager_gui.sh
-chmod +x install_assertion_manager_gui.sh
-sudo install_assertion_manager_gui.sh
+psql -U gazelle
```
-It will:Â
+1. Execute the SQL statement to create the database.
-* Backup the previous EAR
-* Get the latest released version of Assertion Manager and deploy it in your JBoss server.
-* Create the database if it doesn't exist.
+```sql
+CREATE DATABASE "assertion-manager-gui" OWNER gazelle ENCODING 'UTF8' ;
+```
## Deployment
To deploy Assertion Manager:
@@ -50,9 +57,24 @@ For more informations about how to manage that externalization, please refer to
Datasource name : AssertionManagerBaseDS
-Database name : assertion-manager
+Database name : assertion-manager-gui
+
+### Application configuration
+
+1. Download the SQL scripts archive from our Nexus repository [https://gazelle.ihe.net/nexus/#nexus-search;quick~%20AssertionManagerGui.ear](https://gazelle.ihe.net/nexus/#nexus-search;quick~%20AssertionManagerGui.ear) (search for **AssertionManagerGui-ear-X.X.X-sql.zip**)
+
+1. Unzip the archive
+
+1. Edit the application_url value in init.sql. You might also want to edit application_works_without_cas.
-## Insert configuration values
+1. From the bash, update the application configuration by running :
+
+```bash
+psql -U gazelle assertion-manager-gui < schema-X.X.X.sql
+
+psql -U gazelle assertion-manager-gui < init-X.X.X.sql
+```
+Or
Configuration can be done through the Administration interface or with an sql script.
@@ -67,100 +89,32 @@ To restart the application, there are 2 options:
Here is the list of configuration variables that must be defined:Â
-| Variable| Default value| Description|
-|---------|--------------|------------|
-| application_url |http://server_domain:8080/AssertionManager| URL to reach the tool|
-| application_works_without_cas | true | Indicates authentication mechanism to use|
-| ip_login | true | Indicates authentication mechanism to use|
-| ip_login_admin | .\* | Pattern to grant users as admin based on their IP address|
-| cas_url | Not defined| URL of the CAS service|
-| upload_max_size | 100000000| Used to limit uploaded files size|
-| assertion_manager_rest_path_to_assertion | /testAssertion/assertion| do not change|
-| assertion_manager_rest_url | https://server_domain:8080/AssertionManagerGui/rest|  update server_domain:8080 to fit your needs.|
-| security-policies | true | Â Enable security features|
-| X-Frame-Options | SAMEORIGIN| Â https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options|
-| Cache-Control | private, no-cache, no-store, must-revalidate, max-age=0| Â https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#Cache-control|
-| Strict-Transport-Security | max-age=31536000 ; includeSubDomains| Â https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#Cache-control|
-| X-Content-Security-Policy | | https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#Cache-control|
-| X-WebKit-CSP | Use X-Content-Security-Policy values | |
-| X-WebKit-CSP-Report-Only | Use X-Content-Security-Policy-Report-Only values | |
+| Variable| Default value | Description|
+|---------|----------------------------------------------------------------------------------------------------------------|------------|
+| application_url | http://server_domain:8080/AssertionManagerGui | URL to reach the tool|
+| application_works_without_cas | true | Indicates authentication mechanism to use|
+| ip_login | true | Indicates authentication mechanism to use|
+| ip_login_admin | .\* | Pattern to grant users as admin based on their IP address|
+| cas_url | Not defined | URL of the CAS service|
+| upload_max_size | 100000000 | Used to limit uploaded files size|
+| assertion_manager_rest_path_to_assertion | /testAssertion/assertion | do not change|
+| assertion_manager_rest_url | https://server_domain:8080/AssertionManagerGui/rest |  update server_domain:8080 to fit your needs.|
+| security-policies | true | Â Enable security features|
+| X-Frame-Options | SAMEORIGIN | Â https://developer.mozilla.org/en-US/docs/Web/HTTP/X-Frame-Options|
+| Cache-Control | private, no-cache, no-store, must-revalidate, max-age=0 | Â https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#Cache-control|
+| Strict-Transport-Security | max-age=31536000 ; includeSubDomains | Â https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#Cache-control|
+| X-Content-Security-Policy | | https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#Cache-control|
+| X-WebKit-CSP | Use X-Content-Security-Policy values | |
+| X-WebKit-CSP-Report-Only | Use X-Content-Security-Policy-Report-Only values | |
| X-Content-Security-Policy-Report-Only | default-src self \*.ihe-europe.net; script-src self unsafe-eval unsafe-inline ; style-src self unsafe-inline ; | Â https://developer.mozilla.org/en-US/docs/Web/Security/CSP/Using_Content_Security_Policy |
-| sql_injection_filter_switch | true | Â Enable sql injection filtering|
-| gazelle_test-management-url | https://server_domain:8080/gazelle/rest/ | points to gazelle test management rest interface|
-| application_documentation | https://gazelle.ihe.net/content/assertion-manager| |
-| documentation_url | https://gazelle.ihe.net/content/assertion-manager| |
-| application_release_notes_url | https://gazelle.ihe.net/jira/browse/AS#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel | |
-| application_issue_tracker_url | https://gazelle.ihe.net/browse/EVSCLT| URL of the project in the issue tracking system |
-
-To insert values with an sql script, connect to the database :
-```bash
-su postgres
-psql assertion-manager-gui
-```
+| sql_injection_filter_switch | true | Â Enable sql injection filtering|
+| gazelle_test-management-url | https://server_domain:8080/gazelle/rest/ | points to gazelle test management rest interface|
+| application_documentation | https://gazelle.ihe.net/content/assertion-manager | |
+| documentation_url | https://gazelle.ihe.net/content/assertion-manager | |
+| application_release_notes_url | https://gazelle.ihe.net/jira/browse/AS#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel | |
+| application_issue_tracker_url | https://gazelle.ihe.net/browse/EVSCLT | URL of the project in the issue tracking system |
+
-Then copy paste the following script:
-```sql
-SET statement\_timeout = 0;
-SET lock\_timeout = 0;
-SET client\_encoding = 'UTF8';
-SET standard\_conforming\_strings = on;
-SET check\_function\_bodies = false;
-SET client\_min\_messages = warning;
-SET search\_path = public, pg\_catalog;
-SET default\_tablespace = '';
-SET default\_with\_oids = false;
---
--- Name: app\_configuration; Type: TABLE; Schema: public; Owner: gazelle; Tablespace:
---
-Â
-CREATE TABLE app\_configuration (
-Â Â id integer NOT NULL,
-Â Â value character varying(255),
-Â Â variable character varying(255)
-);
-
-ALTER TABLE public.app\_configuration OWNER TO gazelle;
-
---
--- Name: app\_configuration\_pkey; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace:
---
-
-ALTER TABLE ONLY app\_configuration
-ADD CONSTRAINT app\_configuration\_pkey PRIMARY KEY (id);
-
---
--- Name: variable\_unique; Type: CONSTRAINT; Schema: public; Owner: gazelle; Tablespace:
---
-
-ALTER TABLE ONLY app\_configuration
-ADD CONSTRAINT variable\_unique UNIQUE (variable);
-
---
--- Data for Name: app\_configuration; Type: TABLE DATA; Schema: public; Owner: gazelle
---
-
-INSERT INTO app\_configuration VALUES (1, 'false', 'ip\_login');
-INSERT INTO app\_configuration VALUES (2, '.\*', 'ip\_login\_admin');
-INSERT INTO app\_configuration VALUES (3, '100000000', 'upload\_max\_size');
-INSERT INTO app\_configuration VALUES (4, '/testAssertion/assertion', 'assertion\_manager\_rest\_path\_to\_assertion');
-INSERT INTO app\_configuration VALUES (5, 'https://server_domain:8080/AssertionManagerGui/rest', 'assertion\_manager\_rest\_url'); --update with your server domain example: https://gazelle.ihe.net/AssertionManagerGui/rest
-INSERT INTO app\_configuration VALUES (6, 'true', 'security-policies');
-INSERT INTO app\_configuration VALUES (7, 'SAMEORIGIN', 'X-Frame-Options');
-INSERT INTO app\_configuration VALUES (8, 'private, no-cache, no-store, must-revalidate, max-age=0', 'Cache-Control');
-INSERT INTO app\_configuration VALUES (9, 'max-age=31536000 ; includeSubDomains', 'Strict-Transport-Security');
-INSERT INTO app\_configuration VALUES (10, '', 'X-Content-Security-Policy');
-INSERT INTO app\_configuration VALUES (11, 'Use X-Content-Security-Policy values', 'X-WebKit-CSP');
-INSERT INTO app\_configuration VALUES (12, 'Use X-Content-Security-Policy-Report-Only values', 'X-WebKit-CSP-Report-Only');
-INSERT INTO app\_configuration VALUES (13, 'default-src self \*.ihe-europe.net; script-src self unsafe-eval unsafe-inline ; style-src self unsafe-inline ;', 'X-Content-Security-Policy-Report-Only');
-INSERT INTO app\_configuration VALUES (14, 'true', 'sql\_injection\_filter\_switch');
-INSERT INTO app\_configuration VALUES (15, 'https://server_domain:8080/AssertionManagerGui', 'application\_url'); --update with your server domain
-INSERT INTO app\_configuration VALUES (16, 'false', 'application\_works\_without\_cas');
-INSERT INTO app\_configuration VALUES (17, 'https://server_domain:8080/cas', 'cas\_url'); --update with your server domain
-INSERT INTO app\_configuration VALUES (18, 'https://server_domain:8080/gazelle/rest/', 'gazelle\_test-managment-url'); --update with your server domain
-INSERT INTO app\_configuration VALUES (19, 'https://gazelle.ihe.net/content/assertion-manager', 'application\_documentation');
-INSERT INTO app\_configuration VALUES (20, 'https://gazelle.ihe.net/content/assertion-manager', 'documentation\_url');
-INSERT INTO app\_configuration VALUES (21, 'https://gazelle.ihe.net/jira/browse/AS\#selectedTab=com.atlassian.jira.plugin.system.project%3Achangelog-panel', 'application\_release\_notes\_url');
-```
# Compile from sources
@@ -172,10 +126,7 @@ Assertion Manager is an open source project under Apache2 licence. The sources a
```bash
sudo apt-get install maven2 git
git clone https://gitlab.inria.fr/gazelle/applications/test-design/AssertionManager.git assertion-manager-gui
-git clone https://gitlab.inria.fr/gazelle/applications/test-design/AssertionManager.git assertion-manager
-cd assertion-manager
-mvn clean install
-cd ../assertion-manager-gui
+cd assertion-manager-gui
mvn clean package -U -Pproduction
```
@@ -189,7 +140,6 @@ su postgres
psql
postgres=\# CREATE USER gazelle;
postgres=\# ALTER USER gazelle WITH ENCRYPTED PASSWORD 'password';
-postgres=\# CREATE DATABASE "assertion-manager" OWNER gazelle ENCODING UTF-8;
postgres=\# CREATE DATABASE "assertion-manager-gui" OWNER gazelle ENCODING UTF-8;
postgres=\# \\q
exit
@@ -200,14 +150,10 @@ exit
Before compiling, go into gazelle-tm's directory and edit the file pom.xml. Open this file and adapt the properties of prod profile to your needs :
* jdbc.connection.url :Â jdbc:postgresql:assertion-manager-gui
-* jdbc.connection.url2 : jdbc:postgresql:assertion-manager
* jdbc.connection.user /Â jdbc.connection.password : credentials for database access
Then, create the EAR archive with the command line:
```bash
-cd assertion-manager
-mvn install
-cd ..
cd assertion-manager-gui
mvn clean package -Pproduction
```
diff --git a/Assertion-Manager/release-note.md b/Assertion-Manager/release-note.md
index 33032f04612a3c8e4d623df342a444acb96510d3..6f0bca5abaaef76eb456cc872bbc65912e62eeaa 100755
--- a/Assertion-Manager/release-note.md
+++ b/Assertion-Manager/release-note.md
@@ -1,13 +1,19 @@
---
title: Release note
subtitle: Assertion Manager
-toolversion: 4.2.4
-releasedate: 2023-04-18
+toolversion: 4.2.5
+releasedate: 2023-10-19
author: Anne-Gaëlle BERGE
function: Software Engineer
customer: IHE Europe
reference: KER1-RNO-IHE-ASSERTION_MANAGER
---
+# 4.2.5
+_Release date: 2023-10-19_
+
+__Bug__
+* \[[AM-293](https://gazelle.ihe.net/jira/browse/AM-293)\] Editing Assertions lead to an error page when saving
+
# 4.2.4
_Release date: 2023-04-18_
diff --git a/CH-IUA-Validator/installation.md b/CH-IUA-Validator/installation.md
index f816206491ee3710e745ce6e9b0b776bca88c9e4..98ee2609963a1d0e11cb6d0d74ac7a94b40b8341 100755
--- a/CH-IUA-Validator/installation.md
+++ b/CH-IUA-Validator/installation.md
@@ -27,7 +27,7 @@ To install those requirements you can refer to the documentation of installation
## Instructions
-Copy the chiua-validator-service.war into the "/usr/local/wildfly18/standalone/deployments" directory of your Wildfly server. Finally, start your server.
+Get the chiua-validator-service.war from https://gazelle.ihe.net/nexus/#nexus-search;quick~app.validator and copy it into the "/usr/local/wildfly18/standalone/deployments" directory of your Wildfly server. Finally, start your server.
Once the application is deployed, open a browser and go to http://yourserver/chiua-validator-service/ModelBasedValidationWSImpl?wsdl in order to check of the service is available.
diff --git a/CTS/installation.md b/CTS/installation.md
deleted file mode 100755
index b5fdb4cc9c06d5d01b478f52263b03acf67d81c3..0000000000000000000000000000000000000000
--- a/CTS/installation.md
+++ /dev/null
@@ -1,451 +0,0 @@
----
-title: Installation Manual
-subtitle: Certification Testing System
-author: Anne-Gaëlle Bergé
-function: Quality Engineer
-date: 2020-05-25
-toolversion: 1.3
-version: 1.00
-status: Approved
-reference: KER2-MAN-IHE-CTS_1_3
-customer: Federal Office For Public Health
----
-
-# Introduction
-
-FOPH is responsible for providing this guide to the SIA laboratories along with the CTS image to be deployed in the lab.
-
-## Purpose
-
-The purpose of this document is to explain how to install, configure and check the installation of the virtual machine provided by FOPH for
-running SIA test sessions.
-
-## Scope
-
-This document and associated Certification Testing System are relevant to the Swiss Interoperability Assessment Scheme (SIAS) 1.3.
-It is intended to authorized laboratories that will run a SIA test session.
-
-## Virtual Machine characteristics
-
-| __Linux kernel__ | 4.9.0-9-amd64 |
-|-------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
-| __Operating System__ | Debian GNU/Linux 9.12 (Stretch) |
-| __Allocated Base memory__ | 36 GB, 8 CPUs |
-| __Allocated disk space__ | 120 GB
-| __Virtual machine host name__ | The one provided when requesting a copy of CTS |
-| __Networking__ | How the virtual machine accesses the network must be configured according to your needs and requirements. However, we recommend using a bridge adapter. |
-| __Main user__ | gazelle (password : gazelle) is administrator/sudoer |
-| __Installed applications__ | Oracle Java 7 (/usr/lib/jvm/java-7-oracle), Java 8 (/usr/local/jdk1.8.0_121), java-1.7.0-openjdk-amd64 |
-| | Jboss server AS 7.2.0  (3 instances - locations : /usr/local/jboss7, /usr/local/jboss7-proxy, and /usr/local/jboss7-2) |
-| | Wildfly 10 AS |
-| | postgreSQL 9.6 (user : gazelle) |
-| | Apache 2 |
-| | exim 4 (SMTP server) |
-| | Tomcat8, Tomcat 7 |
-
-# Virtual Machine installation process
-
-## Installation
-
-You have been providing with a link to a qcow2 compressed file to be download and deployed in a QEMU virtualizer.
-
-## Check installation of the Virtual machine
-
-Once the machine is up and running, you should be able to access it in SSHÂ (access with public key only):
-
-```bash
-\#ssh gazelle@box\_ip
-```
-
-You must also be able to access the index from your favorite browser at __https://box\_ip__.
-
-Note that the following artifacts are being launch at start-up as docker containers:
-
-* Postgresql server;
-* Jboss and Wildfly servers (it may take a while);
-* Tomcat servers;
-* The SoapUI mocks.
-
-Accessing the home page and checking that the version number of the tools are displayed will tell you that the Jboss based applications are up and running.
-
-# Configuration
-
-## Applications' URLs and OIDs
-
-The testing environment provided to you has been set up for the URL you provided to FOPH when you requested a copy of the system. An OID was
-assigned to this instance of the CAS testing environment. If, for any reason, you need to update these values, a script is available and will
-update the URLs and/or OIDs defined in the database to meet the new URL and/or OID root. To do so, follow the steps below:
-
-1. SSH on the virtual machine
-2. Check you are in the following directory: /home/gazelle
-3. Edit file vm-packaging/update\_for\_distribution.sh (vim is installed)
-4. Update the value of BOX\_NEW\_URL, it shall match the URL your users will use to access the testing environment
-5. Update the value of BOX\_OLD\_URL, it shall match the URL of the previous installation
-5. Update the value of BOX\_NEW\_IP, it shall match the IP address of the Virtual Machine
-5. If desired, update the value of BOX\_NEW\_OID
-6. Save your changes
-
-7. Got to vm-packaging and run ./update\_for\_distribution.sh
-
-The script will restart the docker containers so that the tools will take the changes into account.
-
-## Port forwarding
-
-We recommend that you use a bridge to connect the virtual machine to your LAN. However, if you rather need to perform a network address translation (NAT), below is the list of ports which MUST be forwarded:
-
-* For Gazelle Security Suite: 20007, 20009, 20011, 20070, 3001, 3102, 3202
-* Apache server: 80 / 443 / 10443 if you use HTTPS
-
-Note that those ports are displayed to the user to facilitate the configuration of his/her system; then, it is a good practice to map the ports with the same number.
-
-## Installation of the machine certificate
-
-If the DNS entry was available when the CTS has been configured with your FQDN, a certificate has been requested to Letsencrypt and it has been installed.
-Otherwise, it is your responsibility to install a certificate for HTTPS accesses.
-
-The truststore of the jboss and tomcat servers need to access the truststore containing the certificate chain to the certificate used.
-The application servers installed on the machine are already configured to access the truststore.jks file located in the directory /opt/gazelle/cert.
-So updating that file with the correct chain of certificate is enough. The password of the truststore is set to « password ».
-If you change this password, you shall update the configuration of the Jboss7 and Tomcat application servers accordingly.
-
-### Generate certificates in GSS
-
-Log into Gazelle Security Suite and access PKI > Request a certificate.
-Fill out the form with the following parameters and hit “Requestâ€.
-* Certificate type: Client and Server
-* Key size: 4096
-* Common Name (CN) shall match the full qualifier domain name of the CTS environment.
-* Other mandatory parameters shall fill out to match your organization and country.
-* If the system under test supports SNI, you need to generate another certificate for the second
-hostname that can be used to reach your CTS environment.
-
-### Load the certificate on CTS
-
-In Gazelle Security Suite, go to PKI > Certificate certificates and access the details related to the certificates you have requested.
-From the top right corner of the page, download the certificate (PEM Format), the private key, and the keystore (JKS format) (Password : password, Alias :jboss).
-Copy those certificates in /opt/gazelle/cert on CTS.
-
-#### Configure simulators
-
-Replace /opt/gazelle/cert/jboss.jks by the previously downloaded keystore.
-
-#### ATNA SNI tests
-
-ATNA with SNI extension requires modifications to be performed on the initial library in order to adapt with the testing platform. By default, the library and its certificates are pointing on ehealthsuisse.ihe-europe.net platform.
-Pre-requisite: section "Generate certificates in GSS" has been completed and you have two new certificates.
-* Copy the certificates and private keys into the library’s folder (in /opt/simulators/atna-tls-testing-with-sni/certificates)
-* Edit the server SNI script (server-tls-1.0-sni.sh)
-* Replace the ehealthsuisse-simu .pem and .keycertificates by the certificates pointing on your testing platform (make sure to keep the “certificates/†mentions in front of the certificate names)
-* Replace the test-ihe-europe .pem and .key certificates by the certificates pointing on your second hostname
-* Save the script
-
-#### Apache configuration (port 10443)
-
-ehealthsuisse-simu.key and ehealthsuisse-simu.pem in /opt/gazelle/cert/simu-apache must be replaced by the certificate and the private key previously downloaded.
-
-#### IDP
-
-Enter the commands (enter 'password' when asked):
-```
-$> sudo su
-$> cd /etc/letsencrypt/live/<domainname>
- $> openssl pkcs12 -export -inkey privkey.pem -in cert.pem -certfile chain.pem -out cert.p12
-```
-
-Then replace idp-backchannel.p12 and idp-browser.p12 in /opt/shibboleth-idp/credentials by cert.p12
-Finally,restart docker :
-```
-$> sudo docker restart shibboleth-idp
-```
-
-Open docker log :
-
-```
-$> sudo docker logs shibboleth-idp
-```
-
-If there are errors you will need to restart apacheds then restart the IDP :
-
-```
-$> sudo service apacheds-2.0.0-M24-default stop
-$> sudo service apacheds-2.0.0-M24-default start
-$> sudo docker restart shibboleth-idp
-```
-
-#### Configure TLS simulators in GSS
-
-```
-psql -U gazelle gss -c "UPDATE tls_simulator SET certificate_id = <id_of_the_new_certificate> WHERE certificate_id = 23"
-```
-
-Where <id_of_the_new_certificate> is the id of the certificate created in the "Generate certificates in GSS" section of this document. This id is displayed in the GUI.
-
-#### Restart all docker
-
-```
-docker restart authentication-simulator ch-iua-validator epr-access-token-provider epr-adr-simulator epr-assertion-provider-simulator epr-atc-simulator epr-ppq-repository epr-restricted-metadata-update-update-document-set epr-restricted-metadata-update-responding-gateway epr-restricted-metadata-update-registry-stored-query epr-xca-responding-gateway epr-xds-registry gazelle-assertion-manager gazelle-autoheal gazelle-cda-generator gazelle-dds gazelle-documentation gazelle-evsclient gazelle-fhir-validator gazelle-front gazelle-hl7v2-validator gazelle-hpd-simulator gazelle-patient-manager gazelle-patient-registry gazelle-pixm-connector gazelle-reverse-proxy-apache2 gazelle-schematron-validator gazelle-security-suite gazelle-sso gazelle-sts gazelle-svs-simulator gazelle-tm gazelle-webservice-tester hapi-fhir-jpavalidator idp-adapter shibboleth-idp xdstar-client
-```
-
-# Check access to the tools
-
-From https://your\_box\_url, you should access the following page (Apache front-end) which lists the available applications, their links, and the links to their user manual.
-
-
-
-Check you have access to all the tools. When you access the tool for the first time, the loading of the page could appear to be quite long because
-the tool is being initialized.
-
-## Login
-
-A Central Authentication Service has been set installed and configured. You will be able to create new accounts. To access the tools for the first time,
-use the default account:
-
-__Username__: admin
-
-__Password__: 123456
-
-__Role__: admin\_role
-
-Once you have created your own account (with admin_role role at least) and make sure you disable the admin account or change its password.
-
-## Jboss management
-
-_jboss7_ can be replaced by jboss7-2, jboss7-proxy or wildfly 10 depending on the Jboss application server you need to start/stop/restart.
-
-| __Command__ | __Description__ |
-|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
-| sudo service jboss7 start | Starts the Jboss7 default server (requires gazelle's password) |
-| sudo service jboss7 stop | Stops the Jboss7 process (requires gazelle's password) |
-| sudo service jboss7 restart | Stops the Jboss7 server and after a while starts it again (requires gazelle's password) |
-
-# Gazelle tools
-
-## User guides
-
-Documentation for the tools that are installed on the virtual machine can be found at YOUR_SERVER_URL/gazelle-documentation. On the home page, a direct
-link to each page of the manual is available (PDF icon).
-
-## Included tools
-
-The following tools are installed on the virtual machine:
-
-* __Gazelle Test Management (configured to work as Test Management and Gazelle Master Model)__ is the tool used during the connectathons. It is used to manage
-the users, the systems under test and the test sessions. SIA conformance tests are also stored in this tool.
-It embeds the SIA test cases and the IHE concepts.
-* __Patient Manager__ is a simulator which integrates the IHE profiles which deals with patient and encounter management (CH:PIXV3, CH:XCPD, and CH:PDQV3 are configured)
-* __SVS Simulator__ is a simulator for the SVS profile. It is used by the other applications of the Gazelle test bed as a value set repository.
-* __Gazelle HL7 Validator__ is a validation tool for HL7v3-based messages
-* __Assertion manager Gui__ gathers the assertions extracted from the IHE Technical Framework and EPR specifications
-* __XDSTools__ is aimed to test the systems implementing the XDS.b, XCA, XDS-I.b and XCA-I integration profiles
-* __Gazelle Security Suite__ gathers features to test the CH:ATNA integration profile
-* __Demographic Data Server__ is used to generate fake demographics for testing purposes
-* __EVS Client__ is the graphical interface to Gazelle validation services.
-* __Gazelle Webservice Tester__ has been designed with the purpose of executing SoapUI projects against the systems under test. It also stores the
-message exchanged between the systems under test and the SoapUI mocks
-* __Schematron Validator__ is a schematron-based conformance checker
-* __HPD Simulator__ emulates the CH:HPD actors and offers a validation service for the messages produced in the context of this profile
-* __XD\* Client__ offers validators for verifying the conformance of the XD* messages
-* __CDA Generator__ owns the validator for the CDA SDCO documents
-* __Gazelle FHIR Validator__ provides validators for the messages exchanged in the context of the CH:ATC profile
-* __Authentication Simulator__
-* __CAS__ service for singe-sign-on login
-* __Nagios__ is a service monitoring configured to check the availability of the tools installed in the virtual machine
-* A number of SoapUI mocks are also available, they emulates EPR actors playing the role of responder:
- * Assertion Provider
- * ADR Provider
- * PPQ Repository
- * Metadata Update Responder
- * ATC Patient Audit Record Repository
- * XDS Document Registry
- * XCA Responding Gateway
-* A library for TLS tests with SNI extension used to test authentication with this extension.
-
-The following binaries are deployed in the Jboss7-2: /usr/local/jboss7-2/standalone/deployments directory.
-
-| __Application__ | __Binary name__ | __version__ | __Database__ |
-|-------------------------|---------------------------|-------------|-------------------------|
-| Demographic Data Server | DemographicDataServer.ear | 4.2.2 | demographic-data-server |
-| EVS Client | EVSClient.ear | 5.12.1 | evs-client-prod
-| Gazelle Webservice Tester | gazelle-websesrvice-tester.ear | 1.7.1 | gazelle-webservice-tester |
-| Schematron Validator | SchematronValidator.ear | 2.5.0 | schematron-validator-prod |
-| Authentication Simulator | authentication-simulator.ear | 0.1.2 | authentication-simulator |
-
-
-The following binaries are deployed in Jboss 7-proxy server: /usr/local/jboss7-proxy/standalone/deployment/.
-
-| __Application__ | __Binary name__ | __version__ | __Database__ |
-|------------------------|---------------------------|-------------|-----------------------|
-| Assertion manager Gui | AssertionManagerGui.ear | 4.1.0 | assertion-manager |
-| Test Management | gazelle-tm.ear | 5.12.1 | gazelle |
-| Patient Manager | PAMSimulator.ear | 9.11.7 | pam-simulator |
-| SVS Simulator | SVSSimulator.ear | 2.3.0 | svs-simulator |
-| Gazelle HL7 Validator | GazelleHL7v2Validator.ear | 3.5.1 | gazelle-hl7-validator |
-| Gazelle Security Suite | gazelle-gss.ear | 6.2.4 | gss |
-
-The following binaries are deployed in Jboss 7 server: /usr/local/jboss7/standalone/deployment/.
-
-| __Application__ | __Binary name__ | __version__ | __Database__ |
-|------------------------|---------------------------|-------------|-----------------------|
-| CDA Generator | CDAGenerator.ear | 2.2.1 | cda-generator |
-| HPDSimulator | HPDSimulator.ear | 2.2.1 | hpd-simulator |
-| XDStarClient | XDStarClient.ear | 2.5.4 | xdstar-client |
-| IDP Adaptor | idp-adapter.ear | 0.1.1 | NO DB |
-
-
-The following binaries are deployed in tomcat 8 server: /var/lib/tomcat8/webapps/
-
-| __Application__ | __Binary name__ | __version__ | __Database__ |
-|-----------------|----------------------|-------------|--------------|
-| XDSTools7 | xdstools7.war | 7.2.8 | NO DB |
-| Apereo CAS | sso.war | | Connect to gazelle |
-
-The following binary is deployed in Wildfly 10 server: /usr/local/wildfly10/standalone/deployments
-
-| __Application__ | __Binary name__ | __version__ | __Database__ |
-|-----------------|----------------------|-------------|--------------|
-| Gazelle FHIR Validator | FhirValidator.ear | 3.0.3 | gazelle-fhir-validator |
-
-All the web services required by the applications are on the virtual machine. No access will be done to Gazelle’s servers.
-
-## Monitoring of services
-
-The test environment is delivered with Nagios3 tool configured to check the availability of the services available in the testbed. You will access it from the __Nagios Monitoring__ link of the home page.
-Default username and password have been set to nagiosadmin/gazelle.
-
-## Calibration
-
-For some applications, calibration scripts have been set up. To check the proper configuration of your environment or to check the environment is
-calibrated, you can access the administration page at YOUR_SERVER_URL/admin.php. Details on how it works are given at
-YOUR_SERVER_URL/gazelle-documentation/Gazelle-Calibration/user.html.
-
-# Backups
-
-The backup of the databases (and ONLY the databases) is performed automatically. In the home directory of gazelle (/home/gazelle) there is a folder
-called backup. In that folder there is a script called backup.sh which is executed once a day thanks to a cron
-
-```
-@daily /home/gazelle/backup/backup.sh
-```
-
-We use then logrotate in order to keep:
-
-* a back up for the last 7 days
-* a back up for the last 4 weeks
-* a back up for the last 12 months
-
-For each database we create
-
-* a dump,
-* a SQL dump of the definition,
-* a SQL dump of the data
-
-# Running a SIA testing session
-
-A number of pre-requisites are given below which will help the testing session manager to conduct correctly a SIA testing session.
-
-## Testing session definition
-
-The CTS is provided with a testing session entitled "Default CA Testing Session"; this includes all you need to run a session.
-If you need to create a new testing session, make sure that, when you define this new testing session, you include the list of integration profile
-to be tested. You shall also select “conformity assessment†as testing session type; this will allow the participants to see the tests defined for
-in SIAS.
-
-## Testing tools
-
-Conformity assessment testing is run against tools, some of them have to be declared as such in Gazelle Test Management.
-
-The "Defaut CA Testing Session" session includes those tools. To import them into a newly created testing session, you need to
-
-1. Go to Administration > Manage > Systems > System Management
-2. Click on “Import systems from a previous testing sessionâ€
-3. Select company with keyword = IHE
-4. Select the tools to import
-5. Click on Import
-
-
-## System acceptance
-
-To allow the SUT operator to see the tests to be performed for his/her system, you need to accept it in the testing session. To do so, go to
-Administration > Manage > Systems > System acceptance and hit the checkbox for the systems to be included in this testing session.
-
-## Testing against central services
-
-Testing of the UPI and CH:CPI profiles requires that the systems under test establish a connection respectively to ZAS and BIT central services. It is
-then the responsibility of the testing laboratory to contact those services to get the log of the exchanged messages in order to verify that the messages
-sent by the systems under test complies with EPR specifications.
-
-Please note that there is not legal agreement that bounds the SIA Laboratory with ZAS and BIT.
-
-The following sections give you guidance regarding the prerequisite to test against those services.
-
-### Testing UPI against ZAS
-
-The conformity assessment tests for the UPI profile are run against ZAS UPI service. Only members from the federal organizations are allowed to access the GUI of the UPI system where
-the logs of the testing reside. In other words, as a laboratory, you will not have a direct access to the messages exchanged between the system under test and the UPI service.
-One week in advance of the testing session, you are expected to notify ZAS that you are going to conduct a SIA test session and that you requested their help to fetch the test logs.
-
-During the execution of the conformity assessment tests for UPI, the SUT operators is requested to provide the demographics of the patients they used in the test steps. To help ZAS
-to gather the messages of relevance for you, please populate the spreadsheet "UPI\_Logs\_request\_to\_ZAS.xlsx" (available under the test data section of CTS).
-
-Once ZAS has gathered the message to you, they will send you the XML file along with the original spreadsheet updated with the file name. Upload the messages in the relevant test
-steps and ask the SUT operators to validate them using EVS Client.
-
-### Testing CH:CPI against BIT
-
-The conformity assessment tests for the CH:CPI profile are run against the BIT CPI Provider. Only members from the federal organizations are allowed to access the GUI of the CPI
-system where the audit logs of the testing reside. Also BIT CPI Provider requires an operational action to enable logging full traces (complete payload of messages). In other words,
-as a laboratory, you will not have a direct access to the messages exchanged between the system under test and the CPI Provider.
-
-One week in advance of the testing session, you are expected to notify BIT that you are going to conduct a SIA test session and that you requested their help to fetch the test logs.
-The day of the execution of CH:CPI, you must notify them the precise CH:CPI testing hours for enabling/disabling the traces. Once the testing over, you should receive from BIT the
-complete traces logged during the given hours. It is the lab's responsability to find the messages sent by the SUT and upload them in the relevant test step (SUT operators are
-requested to provide timestamp, IP/host and query information for helping this process).
-
-In case of technical issues (request from the SUT operator failing), BIT can be contacted to have a look at their monitoring interface. This interface provides summary information of
-request attempts and complete audit logs that can help troubleshooting faster. FOPH also have an access to this interface.
-
-### Testing TLS with SNI extension
-
-ATNA profile specification authorizes the use of SNI extension in TLS tests (multiple hostnames with one IP address). However, the current TLS simulator in GSS does not support this extension.
-This may cause a failure in TLS tests with systems requiring SNI. A temporary workaround with a tool dedicated to test that case has been set up.
-This tool is named "atna-tls-testing-with-sni" and its directory is located in "/opt/simulators".
-A README file has been created at root directory level to guide monitors through the testing process.
-
-Prior to perform this test, monitors must ask participants to provide them with an additional DNS entry specifically for SNI extension testing.
-As mentioned in SIA test cases in Gazelle Test Management, monitors are asked to provide the logs retrieved from the tool as evidence in test steps.
-
-# Annex : Cloning process
-
-The CTS is obtained from the Reference Environment 1.2.
-
-Clone the virtual machine of the reference environment. Start it
-
-Download the packaging scripts on the VM from the SVN repository : https://svn.ihe-europe.net/gazelle/scripts/vm-packaging/branches/CTS
-
-`svn checkout https://svn.ihe-europe.net/gazelle/scripts/vm-packaging/branches/CTS packaging-scripts/`
-
-There is two main scripts :
-- cleanup_data_for_distribution.sh : Delete all data not needed for the CTS
-- update_for_distribution.sh : Update all the URLs, IP address and OIDs
-
-Both need to be executed with root access (sudo).
-
-First, execute the clean up scripts :
-
-`sudo ./cleanup_data_for_distribution.sh`
-
-Before executing the second script, some parameters need to be updated. Open the update_for_distribution.sh and update the following properties :
-* BOX_NEW_URL= the url for the CTS VM
-* BOX_NEW_OID= the oid for the CTS VM
-* BOX_NEW_IP= the ip for the CTS VM
-* ADMIN_NAME= The admin name in Gazelle Test Management
-* ADMIN_TITLE= The admin title in Gazelle Test Management
-* ADMIN_EMAIL= The admin email in Gazelle Test Management
-
-The following properties should not be changed as they are the url of the reference environment (it always be https://ehealthsuisse.ihe-europe.net) and the old hostname :
-* BOX_OLD_URL
-* DEFAULT_BOX_HOSTNAME
-
-Save the file, then execute update_for_distribution.sh with sudo :
-
-`sudo ./update_for_distribution.sh`
diff --git a/CTS/media/home_page.png b/CTS/media/home_page.png
deleted file mode 100755
index 7bf6897d91702ebc0fa2aac99768db964efca45b..0000000000000000000000000000000000000000
Binary files a/CTS/media/home_page.png and /dev/null differ
diff --git a/DCC-validator/installation.md b/DCC-validator/installation.md
index 31c6c242cfc8f4000fb749716ae227992cee561b..43dc3ce01d158b94e8f932bb3a4e85c4b6a88056 100755
--- a/DCC-validator/installation.md
+++ b/DCC-validator/installation.md
@@ -2,8 +2,8 @@
title: Installation Manual
subtitle: DCC Validator
author: Malo Toudic
-releasedate: 05/04/2025
-toolversion: 1.0.x
+releasedate: 03/11/2023
+toolversion: 1.2.x
function: Developer
version: 0.01
status: Draft document
@@ -51,11 +51,12 @@ Define a resource in your server with name *java:/app/gazelle/dcc-validator/oper
This resource should refer to a deployment.properties file. This file shall contain the following properties :
-| Property Name | Description | Example value |
-| --- | --- | --- |
-| svssimulator.url | URL of Simulator | <http://localhost/SVSSimulator> |
-| truststore.path | Path of the truststore containing the trusted certificates that issues Digital covid certificates | /opt/dcc-validator/truststore.jks |
-| truststore.password | Password of the truststore containing the trusted certificates that issues Digital covid certificates | password |
+| Property Name | Description | Example value |
+| --- |-------------------------------------------------------------------------------------------------------|-----------------------------------|
+| svssimulator.url | URL of Simulator | <http://localhost/SVSSimulator> |
+| truststore.path | Path of the truststore containing the trusted certificates that issues Digital covid certificates | /opt/dcc-validator/truststore.jks |
+| truststore.password | Password of the truststore containing the trusted certificates that issues Digital covid certificates | password |
+| ddvcverifier_url | URL of the WHO DDVC verifier | http://localhost/verify |
#### Configure WildFly 18 for DCC Validator
diff --git a/DCC-validator/release-note.md b/DCC-validator/release-note.md
index 8fad9df4e8360498d057c035b55c3688373576e8..4f325a17287bad35726dfb219f7ee380e2d6d260 100755
--- a/DCC-validator/release-note.md
+++ b/DCC-validator/release-note.md
@@ -1,14 +1,23 @@
---
title: Release note
subtitle: Digital Covid Certificate validator
-toolversion: 1.0.0
-releasedate: 2022-04-05
+toolversion: 1.2.2
+releasedate: 2023-11-03
author: Malo Toudic
function: Software developer
customer: IHE Europe
reference: KER1-RNO-IHE-DCC_VALIDATOR
---
+# 1.2.2
+_Release date: 2023-11-03_
+
+__Story__
+* \[[DCC-20](https://gazelle.ihe.net/jira/browse/DCC-20)\] Make the DDVC verify url configurable
+
+__Problem__
+* \[[DCC-21](https://gazelle.ihe.net/jira/browse/DCC-21)\] Some DDVC QR CODE cannot be decoded
+
# 1.2.1
_Release date: 2022-11-29_
diff --git a/Datamatrix/Makefile b/Datamatrix/Makefile
new file mode 100755
index 0000000000000000000000000000000000000000..cbbc56c706e2a9d7c1b43999f7199c4c956757ea
--- /dev/null
+++ b/Datamatrix/Makefile
@@ -0,0 +1,3 @@
+SHELL := /bin/bash
+
+include ../Makefile.generic
diff --git a/Datamatrix/installation.md b/Datamatrix/installation.md
new file mode 100755
index 0000000000000000000000000000000000000000..d4eef60d78a48eca6ef3eb2e09258e7a4feb7f9b
--- /dev/null
+++ b/Datamatrix/installation.md
@@ -0,0 +1,12 @@
+---
+title: Installation Manual
+subtitle: Datamatrix
+author: Nicolas BAILLIET
+function: Developer
+date: 2023-10-24
+toolversion: 1.X.X
+version: 1.0
+status: Approved
+reference: KER1-MAN-ANS-DATAMATRIX_INSTALLATION
+customer: ANS
+---
diff --git a/Datamatrix/release-note.md b/Datamatrix/release-note.md
new file mode 100755
index 0000000000000000000000000000000000000000..d6a3b1ef8a20eb3d19a9c3cbb90ab092d09bff9b
--- /dev/null
+++ b/Datamatrix/release-note.md
@@ -0,0 +1,16 @@
+---
+title: Release note
+subtitle: Datamatrix
+toolversion: 1.0.1
+releasedate: 2023-10-24
+author: Nicolas BAILLIET
+function: Developer
+customer: ANS
+reference: KER1-RNO-ANS-DATAMATRIX
+---
+# 1.0.1
+_Release date: 2023-10-24_
+
+__Task__
+* \[[DATAMATRIX-1](https://gazelle.ihe.net/jira/browse/DATAMATRIX-1)\] IHM improvement - Size text area, Version number, user manual
+* \[[DATAMATRIX-2](https://gazelle.ihe.net/jira/browse/DATAMATRIX-2)\] C40 encoding and broken link
\ No newline at end of file
diff --git a/Datamatrix/user.md b/Datamatrix/user.md
new file mode 100755
index 0000000000000000000000000000000000000000..8327aa356667e6860b7cd56659e4744b612b7988
--- /dev/null
+++ b/Datamatrix/user.md
@@ -0,0 +1,12 @@
+---
+title: User Manual
+subtitle: Datamatrix
+author: Nicolas BAILLIET
+function: Developer
+releasedate: 2023-10-24
+toolversion: 1.X.X
+version: 1.02
+status: Draft
+reference: KER1-MAN-ANS-DATAMATRIX_USER
+customer: ANS
+---
\ No newline at end of file
diff --git a/EPR-ADR-Simulator/release-note.md b/EPR-ADR-Simulator/release-note.md
index 589cb28fb9716d3d36084f5fa388406da908b18a..ba4d1acf0e5de3dd6403b73cb7fe1587cc63fb7d 100755
--- a/EPR-ADR-Simulator/release-note.md
+++ b/EPR-ADR-Simulator/release-note.md
@@ -1,15 +1,22 @@
---
title: Release note
subtitle: ADR Simulator
-author: Youn Cadoret
+author: Youn Cadoret / Alexandre POCINHO
function: Developer
-releasedate: 2020-03-11
-toolversion: 1.3.6
+releasedate: 2023-06-13
+toolversion: 1.3.7
reference: KER1-RNO-IHE-ADR_SIMULATOR
customer: IHE-EUROPE
---
+# 1.3.7
+_Release date: 2023-06-13_
+
+__Task__
+* \[[ADRPROV-17](https://gazelle.ihe.net/jira/browse/ADRPROV-17)\] Update specification for CH:ADR Response
+
+
# 1.3.6
_Release date: 2020-03-11_
diff --git a/EPR-ATC-Simulator/release-note.md b/EPR-ATC-Simulator/release-note.md
index fbbef13f16b6a2ede8213b7f533ff00e7f49ad0f..f99dc7567f37f481eefbc9202aea4e764cbdabf0 100755
--- a/EPR-ATC-Simulator/release-note.md
+++ b/EPR-ATC-Simulator/release-note.md
@@ -1,13 +1,19 @@
---
title: Release note
subtitle: ATC Simulator
-toolversion: 2.0.0
-releasedate: 2023-06-08
+toolversion: 2.0.1
+releasedate: 2023-12-07
author: Youn Cadoret
function: Software Engineer
customer: IHE Europe
reference: KER1-RNO-IHE-ATC_SIMULATOR
---
+
+# 2.0.1
+_Release date: 2023-12-07_
+__Bug__
+* \[[ATCREPO-23](https://gazelle.ihe.net/jira/browse/ATCREPO-23)\] ATC Repository data need to be updated to be conform to the specification
+
# 2.0.0
_Release date: 2023-06-08_
__Task__
diff --git a/EVS-Client/installation.md b/EVS-Client/installation.md
index 7a148a182a69d3b8c3e7cd705c594f11cd83b2fd..9c7a5f975464c62c8e6f5a1a2df01b650d0c5015 100755
--- a/EVS-Client/installation.md
+++ b/EVS-Client/installation.md
@@ -3,8 +3,8 @@ title: Installation Manual (including rest api)
subtitle: EVS Client
author: Cédric Eoche-Duval
function: Software Engineer at IHE Gazelle Team
-date: 2023/04/18
-toolversion: 6.2.x
+date: 2023/12/08
+toolversion: 6.4.x
version: 2.01
status: Approved document
reference: KER1-MAN-IHE-EVS_CLIENT_INSTALLATION-2_01
@@ -84,7 +84,7 @@ If any of these variables is set, the corresponding preference in `preferences.p
Since version **6.3.0**, EVSClient can register itself as a client of a SSO server. This is done by giving some environment variables to the application.
| **Variable name** | **Description** | **Example of value** |
-|----------------------|---------------------------------------------------------------------|-------------------------------------|
+|-----------------https://svn.ihe-europe.net/gazelle/validators/xds/xds-model-----|---------------------------------------------------------------------|-------------------------------------|
| GZL_EVSCLIENT_K8S_ID | Describes the instance ID and the replica ID of the application. | gazelle-evsclient-6dfeeb5595-tl29k |
[WARNING] There are additional required variables for registration of the proxy to the SSO server. Please refer to the
diff --git a/EVS-Client/release-note.md b/EVS-Client/release-note.md
index acdf5038dda7ca450bbe2c5784c572e2543c9cdf..850fc7dce4ca1a40c9bf11e32941000dee88a1ce 100755
--- a/EVS-Client/release-note.md
+++ b/EVS-Client/release-note.md
@@ -1,34 +1,48 @@
---
title: Release note
subtitle: EVS Client
-toolversion: 6.4.0
-releasedate: 2023-09-13
+toolversion: 6.4.1
+releasedate: 2023-12-08
author: Cédric Eoche-Duval
function: Software Engineer
customer: IHE Europe
reference: KER1-RNO-IHE-EVS_CLIENT
---
+# 6.4.1
+
+_Release date: 2023-12-08_
+
+__Bug__
+* \[[EVSCLT-1188](https://gazelle.ihe.net/jira/browse/EVSCLT-1188)\] Rename Pixelmed SR Dose validator
+* \[[EVSCLT-1191](https://gazelle.ihe.net/jira/browse/EVSCLT-1191)\] Missing MCA Button for remote validation
# 6.4.0
+_Release date: 2023-09-13_
__Story__
* \[[EVSCLT-1164](https://gazelle.ihe.net/jira/browse/EVSCLT-1164)\] Validation Service Client for EVS6
-
__Bug__
* \[[EVSCLT-1147](https://gazelle.ihe.net/jira/browse/EVSCLT-1147)\] Cannot download the validation report
* \[[EVSCLT-1182](https://gazelle.ihe.net/jira/browse/EVSCLT-1182)\] Title of the validation page is not relevant
* \[[EVSCLT-1183](https://gazelle.ihe.net/jira/browse/EVSCLT-1183)\] Does not display the eye icon if the user cannot be pointed to the location of the issue
+# 6.3.0
+_Release date: 2023-07-11_
+
+Step 1 of Gazelle User Management renovation.
+
+__Task__
+* \[[EVSCLT-1174](https://gazelle.ihe.net/jira/browse/EVSCLT-1174)\] [GUM] Integrate new sso-client-v7 to evs
# 6.2.4 (SUPPORT)
-_Release date: 2023-09-05_
+_Release date: 2023-09-05_
__Bug__
* \[[EVSCLT-1185](https://gazelle.ihe.net/jira/browse/EVSCLT-1185)\] Bugs correction in MCA
* \[[EVSCLT-1186](https://gazelle.ihe.net/jira/browse/EVSCLT-1186)\] Bugs correction in X-val
-* \[[EVSCLT-1187](https://gazelle.ihe.net/jira/browse/EVSCLT-1187)\] Error on validation report
+* \[[EVSCLT-1187](https://gazelle.ihe.net/jira/browse/EVSCLT-1187)\] Error on validation report
Remarks : This version is a support version from 6.2.3. It DOES NOT support Gazelle User Management Feature and corrects some bugs presents in Message Content Analyzer (upgraded to 3.0.5 SUPPORT), Gazelle X Validation (upgraded to 2.0.5), Gazelle Assets (upgraded to 3.0.1).
@@ -40,16 +54,6 @@ Step 1 of Gazelle User Management renovation.
Integration of new version (2.0.0) of sso-client-v7.
-# 6.3.0
-
-_Release date: 2023-07-11_
-
-Step 1 of Gazelle User Management renovation.
-
-__Task__
-* \[[EVSCLT-1174](https://gazelle.ihe.net/jira/browse/EVSCLT-1174)\] [GUM] Integrate new sso-client-v7 to evs
-
-
# 6.2.3
_Release date: 2023-06-06_
@@ -60,7 +64,6 @@ __Bug__
__Story__
* \[[EVSCLT-1176](https://gazelle.ihe.net/jira/browse/EVSCLT-1176)\] validation CDA EV6
-
# 6.2.2
_Release date: 2023-04-20_
diff --git a/EVS-Client/user.md b/EVS-Client/user.md
index 5e32c0cd62d973a98f132823c24e4a2c3f99a066..b969c1f0e26d08290a482b7fdb97c8cd3fcb4c46 100755
--- a/EVS-Client/user.md
+++ b/EVS-Client/user.md
@@ -1,10 +1,10 @@
---
title: User Manual
subtitle: EVS Client
-author: Philippe Daigremont
+author: Cédric Eoche-Duval
function: IHE Europe Technical Project Manager
-date: 18/04/2023
-toolversion: 6.2.x
+date: 08/12/2023
+toolversion: 6.4.x
version: 1.04
status: Approved document
reference: KER1-MAN-IHE-EVS_CLIENT_USER-1_04
diff --git a/Gazelle-HL7V2-Simulators/media/HL7V2Manager_UI.png b/Gazelle-HL7V2-Simulators/media/HL7V2Manager_UI.png
index cbabcf80c1357ffca53470f4143fe0dc00beb775..d772d3f1f6cbd65ed1490957bde53e0c62ee7eb9 100644
Binary files a/Gazelle-HL7V2-Simulators/media/HL7V2Manager_UI.png and b/Gazelle-HL7V2-Simulators/media/HL7V2Manager_UI.png differ
diff --git a/Gazelle-HL7V2-Simulators/release-notes.md b/Gazelle-HL7V2-Simulators/release-notes.md
new file mode 100644
index 0000000000000000000000000000000000000000..3846c7bc5cf475685796e83e8c06f00780e06921
--- /dev/null
+++ b/Gazelle-HL7V2-Simulators/release-notes.md
@@ -0,0 +1,15 @@
+---
+title: Release note
+subtitle: HL7V2 Simulators
+author: Romuald DUBOURG, Claude Lusseau
+date: 7/11/2023
+toolversion: 1.0.0
+function: Software Engineer
+customer: ANS
+---
+# HL7Simulators 1.0.0
+_Release date: 2023-7-11_
+
+__Story__
+* \[[HLVSIM-1](https://gazelle.ihe.net/jira/browse/HLVSIM-1)\] Create Hl7V2 Simulators
+
diff --git a/Gazelle-HL7V2-Simulators/user.md b/Gazelle-HL7V2-Simulators/user.md
index 008357325dd7d4b01dbd49f18fa12e0213786a7c..0e9535b7f72fa4337d02334d5863fc3fa810a2f3 100755
--- a/Gazelle-HL7V2-Simulators/user.md
+++ b/Gazelle-HL7V2-Simulators/user.md
@@ -1,5 +1,5 @@
---
-title: Installation Manual
+title: User Manual
subtitle: Gazelle-Hl7-simulator
author: CLaude LUSSEAU, Romuald DUBOURG
function: Software Engineer
@@ -15,15 +15,15 @@ customer: IHE-EUROPE
HL7V2Simulators is the part of the Gazelle platform dedicated to the simulation of Hl7v2 messages transmission.
-The first simulator mimics the transmission of a Clinical Document Architecture (CDA) to a receiving application. The creator of the simulator expects to receive as many acknowledgments as requested by the message.
+One simulator mimics the transmission of a Clinical Document Architecture (CDA) to a receiving application. The creator of the simulator expects to receive as many acknowledgments as requested by the message.
-The second simulator acts as a server, receiving any CDA message sent to it. It then sends back as many acknowledgments as requested in the message to its sender.
+Three simulator acts as a server with different charset handled. For every CDA messages received, they send back as many acknowledgments as requested in the message to their sender.
Concerning HL7v2 simulators: the application also gathers the HL7 templates.
# User interface
-As shown on picture below, the [User Interface] provides two simulators tools: **Creator** and **Manager**:
+As shown on picture below, the [User Interface] provides two simulators tools: **Creator** and **Managers**:
@@ -31,7 +31,7 @@ As shown on picture below, the [User Interface] provides two simulators tools: *
-And **Manager** allows user to receive Hl7 messages from a creator:
+And **Managers** allows user to receive Hl7 messages from a creator:
@@ -40,12 +40,17 @@ Both tools use templates included in the application or imported by user.
## Browse Configuration SUT
-There are 5 fields that define a Configuration SUT:
+There are 10 fields that define a Configuration SUT:
- Name : Define the name of your configuration
- Host/ip: define the destination device of the message
- Port: Define on which port send the message on the destination device
- Application: Define the name of the application which you send the message it will help fulfill the message
- Facility: Define the name of the facility which you send the message it will help fulfill the message
+ - Owner: Show the creator of the configuration
+ - CompanyOwner: Show the company owner of the configuration, only user can see his company's not share configuration.
+ - isShare: Define if the configuration is share to others users. Only admin or people of the company can edit it.
+ - Charset: Define on a server it tells with which charset message should be sent and replied.
+ - isServerSide: Define if the configuration is for a server or a client
Once connected with CAS(Central Authentication Service) Select option  of **HL7v2 simulators tool** menu.
@@ -54,7 +59,7 @@ It will display the list of Configuration SUT :
-All the Configuration SUT available are gathered in the tool. You can either create, edit or delete one.
+Only admin cans see all configuration but a lambda user can see his company configuration also either create, edit or delete one.
## Browse Template
@@ -62,7 +67,7 @@ There are 4 fields that define a template :
-Title : Define the title of the template
-isEnabled : Define if the template can be used in a message
-Filename : Define the name of the stocked file corresponding at the mustache template
- -Description: Explain what is the purpose of the template or it's particularity
+ -Description: Explain what is the purpose of the template ,or it's particularity
Once connected with CAS(Central Authentication Service) Select option  of **HL7v2 simulators tool** menu.
@@ -77,7 +82,7 @@ All Template available are gathered in the tool. You can either create, edit or
## Browse Preference
There are 4 fields that define a preference:
- -PreferenceName : define the name a of a preference
+ - PreferenceName : define the name a of a preference
- ClassName: define the type of value contain by the preference
- PreferenceValue: define the value of a preference
- Description: describe how is use the preference
@@ -90,14 +95,21 @@ It will display the list of Preference :
All Preference available are gathered in the tool. You can either create, edit or delete one.
+Preferences enable to custom the working of the application there are 5 things that can be custom.
+ Endpoint_Validator: The validation Endpoint to define which HL7 validator should be used.
+ UTF8_Manager_Name, UTF8_Manager_Host, UTF8_Manager_Application, UTF8_Manager_Facility, UTF8_Manager_Port :The configuration of the UTF-8 manager
+ I88591_Manager_Name, I88591_Manager_Host, I88591_Manager_Application, I88591_Manager_Facility, I88591_Manager_Port :The configuration of the 8859-1 manager
+ I885915_Manager_Name, I885915_Manager_Host, I885915_Manager_Application, I885915_Manager_Facility, I885915_Manager_Port :The configuration of the 8859-15 manager
+ Creator_Name, Creator_Host ,Creator_Application , Creator_Port:The configuration of the creator
+
+
# Creator
The Creator Simulator simulate the transmission of a Clinical Document Architecture (CDA) to a receiving application.
There are two things that must be configured before sending a message.
-First a message should have a destination, so the creator need a Configuration SUT to be selected this will represent the destination where you want the message to be send.
-It is possible to use default local configuration to test simulators between them but to send to an external application, its configuration SUT must be added on the Configuration SUT browser.
-Once the configuration SUT needed is set it can be selected with this dropdown on the Creator UI.
+First a message should have a destination, so the creator need a Configuration SUT to be selected this will represent the destination where you want the message to be sent.
+It is possible to use default configuration ,but it can be custom on the preferences' menu.
@@ -107,26 +119,25 @@ Once the needed template is set it can be selected with dropdown on the creator
-Before using the creator be sure that the SUT Configuration name local_creator_configuration is correctly define.
For sending the receiving application Configuration must have been insert in the configuration list.
On the Creator GUI before sending, a Configuration Receiver and a Template must have been selected.
-Once the message is sent the message history print messages who have been send and receive including ACK/NACK AND ZAM. 1
+Once the message is sent the message history print messages who have been sent and receive including ACK/NACK AND ZAM.
-## Manager
+## Managers
-The manager is easier to use because it's just a server that can be started/stopped.
-Before using the manager be sure that the SUT Configuration name local_manager_configuration is correctly define.
-For replying ZAM the manager must have all required ZAM templates. See TEMPLATE section for details.
-For replying ZAM the manger should also have the configuration SUT defined of the sender. Else the manager cannot know where to send ZAM ( because ACK with HAPI is automatic).
-For starting the server manager just go to the Manger GUI and press the start button.
-Once the server is started it will try parsing every incoming messages and reply ACK/NACK AND corresponding ZAM.
+There is a manager for each charsets UTF-8, 8859-1 et 8859-15.
+Managers are easier to use because it's just a server that can be started/stopped.
+For replying ZAM managers must have all required ZAM templates. See TEMPLATE section for details.
+For replying ZAM managers should also have the configuration SUT defined of the sender. Else managers cannot know where to send ZAM ( because ACK with HAPI is automatic).
+For starting servers managers just go to the Manager GUI and press the start button.
+Once servers are started they will try to parse every incoming messages and reply ACK/NACK AND corresponding ZAM.
## Default Import
-DEFAULT_ANS_TEMPLATES
This variable can be set to true to have a group of messages example with a description that explain what they are use for.
-DEFAULT_ANS_SERVERS
+-DEFAULT_ANS_SERVERS
This variable can be set to true to initialize default server of the application instead of created them manually
\ No newline at end of file
diff --git a/Gazelle-Security-Suite/release-note.md b/Gazelle-Security-Suite/release-note.md
index a0d614f7de2c310a048e4e472319a0cce89d800d..904a9ac133b6ef9ceac5c9375d22bb342b273054 100755
--- a/Gazelle-Security-Suite/release-note.md
+++ b/Gazelle-Security-Suite/release-note.md
@@ -1,14 +1,14 @@
---
title: Release note
subtitle: Gazelle Security Suite
-toolversion: 6.3.2
+toolversion: 6.3.3
releasedate: 2023-06-08
author: Anne-Gaëlle BERGE
function: Software Engineer
customer: IHE Europe
reference: KER1-RNO-IHE-GSS
---
-#6.3.3
+# 6.3.3
_Release date : 2023-06-08_
__Task__
diff --git a/Gazelle-Token-Service/installation.md b/Gazelle-Token-Service/installation.md
index cdadc2f14f992b1e3b5515790475c576b6d70db5..f191a7a2eb822458d1101fab507fc607f7357e30 100644
--- a/Gazelle-Token-Service/installation.md
+++ b/Gazelle-Token-Service/installation.md
@@ -15,7 +15,7 @@ customer: IHE-EUROPE
Gazelle Token Service is an open-source Java EE project used to calling various validation-services of e-Health standards.
-
+
## Get Gazelle-Token-Service
@@ -54,10 +54,10 @@ Each version of EVSClient is published in
### Pre-requisites
-Gazelle Token Service requires **JDK 11**, **JBoss AS 7.2.0-Final** **WildFly 18.0.1.Final**+ and **PostgreSQL**
+Gazelle Token Service requires **JDK 11**, **WildFly 26.1.2.Final**+ and **PostgreSQL**
to be run. Please refere to
-[General considerations for WildFly 18](https://gazelle.ihe.net/gazelle-documentation/General/wildfly18.html)
-to install WildFly 18 and setup a compliant environment.
+[General considerations for WildFly 26](https://gazelle.ihe.net/gazelle-documentation/General/wildfly26.html)
+to install WildFly 26 and setup a compliant environment.
### Create and initialize the database
@@ -74,33 +74,26 @@ If any of these variables is set, the corresponding preference in `preferences.p
Data sources _(configuration file that indicates how to connect to the
database)_ must be defined in the WildFly application server. More information about how to configure
data sources can be found here:
-[WildFly datasources](https://gazelle.ihe.net/gazelle-documentation/General/wildfly18.html#setup-datasources-for-gazelle-applications).
+[WildFly datasources](https://gazelle.ihe.net/gazelle-documentation/General/wildfly26.html).
-EVSClient will expect the JNDI datasource to be named: `java:jboss/datasources/GazelleTokenDS`.
+Gazelle Token will expect the JNDI datasource to be named: `java:jboss/datasources/GazelleTokenDS`.
A data source example and specific to Gazelle Token Service can be found in `gazelle-token-service-ear/src/main/datasource`
in the sources or in the archive `gazelle-token-service-ear-X.X.X-datasource.zip` that can be downloaded from
-[https://gazelle.ihe.net/nexus](https://gazelle.ihe.net/nexus/index.html#nexus-search;gav%7E%7EEVSClient-ear%7E%7E%7E).
+(https://gazelle.ihe.net/nexus/service/local/repositories/releases/content/net/ihe/gazelle/token/gazelle-token-service-ear/1.0.0/gazelle-token-service-ear-1.0.0-datasource.zip).
### File system
-
-A ZIP file is available at
-[https://gazelle.ihe.net/nexus/#nexus-search;quick~gazelle-token-service](https://gazelle.ihe.net/nexus/#nexus-search;quick~gazelle-token-service)
-(search for the last released **gazelle-token-service-ear-X.X.X-dist.zip**) that you can unzip in order to easily
-create all the required directories, starting at /opt.
-
-```bash
-wget -nv -O /tmp/gazelle-token-service-dist.zip "[*https://gazelle.ihe.net/nexus/service/local/repositories/releases/content/net/ihe/gazelle/gazelle-token-service-ear/X.X.X/gazelle-token-service-ear-X.X.X-dist.zip*](https://gazelle.ihe.net/nexus/service/local/repositories/releases/content/net/ihe/gazelle/EVSClient-ear/6.X.X/EVSClient-ear-6.X.X-dist.zip)"
-unzip /tmp/gazelle-token-service-dist.zip -d /
+Files system are located in /opt/gazelle-token.
+You should create the folder before launching the app.
+```
+sudo mkdir /opt/gazelle-token
```
### Single Sign On Installation
SSO installation is optional.
-Since version **5.13.0**, EVSClient needs a file to be integrated with the Gazelle SSO application.
-
-An instance of [Gazelle SSO](../Gazelle-SSO) must be deployed, the file `evs.properties`
+An instance of [Gazelle SSO](../Gazelle-SSO) must be deployed, the file `gazelle-token-service.properties`
shall be in `/opt/gazelle/cas` and must contain the following statements :
```properties
@@ -110,17 +103,17 @@ casLogoutUrl=https://<yourfqdn>/sso/logout
service=https://<yourfqdn>/gazelle-token-service
```
-_The truststore path must be the path referenced in `/etc/init.d/wildfly18`, in the option `OPT_SSL` and `-Djavax.net.ssl.trustStore`._
+_The truststore path must be the path referenced in `/etc/init.d/wildfly26`, in the option `OPT_SSL` and `-Djavax.net.ssl.trustStore`._
## Deployment
-Once you have retrieved the archive (see [Get EVSClient](#get-evsclient)), copy it to your JBoss7
-server in the `${JBOSS_DIR}/standalone/deployments` directory. The EAR copied in this folder MUST be
-named `evs.ear`.
+Once you have retrieved the archive, copy it to your wildfly26
+server in the `/usr/local/wildfly26/standalone/deployments` directory. The EAR copied in this folder MUST be
+named `gazelle-token-service.ear`.
```bash
-cp EVSClient-ear-X.X.X.ear /usr/local/wildfly-18.0.1.Final/standalone/deployments/gazelle-token-service-ear.ear
-sudo service wildfly18 start
+cp gazelle-token-service-ear-X.X.X.ear /usr/local/wildfly26/standalone/deployments/gazelle-token-service-ear.ear
+sudo service wildfly26 start
```
If you did not change any default configuration, Gazelle Token Service should be accessible at
diff --git a/Gazelle-Transformation-Service/installation.md b/Gazelle-Transformation-Service/installation.md
index fde20e3dd1df289be5eb386817fbf1cf1d34d5da..44e7f9c16e02af079d5437cf44b04b14b8921c51 100755
--- a/Gazelle-Transformation-Service/installation.md
+++ b/Gazelle-Transformation-Service/installation.md
@@ -15,7 +15,7 @@ customer: IHE-EUROPE
# Sources & binaries
-Gazelle Transformation Service is an open-source project under Apache License Version 2.0 ([https://gazelle.ihe.net/content/license](https://gazelle.ihe.net/content/license)). Sources are available via Subversion at [https://svn.ihe-europe.net/gazelle/Maven/gazelle-transformation/](https://svn.ihe-europe.net/gazelle/Maven/gazelle-transformation/).
+Gazelle Transformation Service is an open-source project under Apache License Version 2.0 ([https://gazelle.ihe.net/content/license](https://gazelle.ihe.net/content/license)). Sources are available via git at [https://gitlab.inria.fr/gazelle/public/processing/transformation](https://gitlab.inria.fr/gazelle/public/processing/transformation).
# Gazelle Transformation Service installation and configuration
diff --git a/Gazelle-User-Management/links.md b/Gazelle-User-Management/links.md
index 78945bc2efcd75cc90ccbf21fc5fe9a11c80eb29..c33d87033173ccce666c65bb547ccf30d776bb4f 100644
--- a/Gazelle-User-Management/links.md
+++ b/Gazelle-User-Management/links.md
@@ -1,8 +1,8 @@
---
title: Documentation
subtitle: Gazelle User Management
-toolversion: 1.0.0
-releasedate: 2023-07-17
+toolversion: 1.0.1
+releasedate: 2023-09-14
author:
---
diff --git a/Gazelle-Webservice-Tester/installation.md b/Gazelle-Webservice-Tester/installation.md
index 09d1c054b7950aa7ef1a0182a59d9f9879d5b2df..b4c84e439e3f7b55e66688d8b6e48577dc654bcf 100755
--- a/Gazelle-Webservice-Tester/installation.md
+++ b/Gazelle-Webservice-Tester/installation.md
@@ -4,7 +4,7 @@ subtitle: Gazelle Webservice Tester
author: Malo TOUDIC
function: Software developer
date: 05/03/2019
-toolversion: 1.7.x
+toolversion: 1.8.x
version: 1.02
status: Approved document
reference: KER1-MAN-IHE-GAZELLE_WEBSERVICE_TESTER_USER
diff --git a/Gazelle-Webservice-Tester/release-note.md b/Gazelle-Webservice-Tester/release-note.md
index 7f8dbd0b4fc4dd2a7ac53d422b2c295b1ad3270c..e476629e17949d139a8fa7c33c087e659b26ecbc 100755
--- a/Gazelle-Webservice-Tester/release-note.md
+++ b/Gazelle-Webservice-Tester/release-note.md
@@ -1,13 +1,20 @@
---
title: Release note
subtitle: Gazelle Webservice Tester
-toolversion: 1.7.4
+toolversion: 1.8.0
releasedate: 2021-07-19
author: Malo TOUDIC
function: Software developer
customer: IHE-Europe
reference: KER1-RNO-IHE-GAZELLE_WEBSERVICE_TESTER
---
+# 1.8.0
+_Release date: 2023-09-21_
+
+__Improvement__
+* \[[GWT-146](https://gazelle.ihe.net/jira/browse/GWT-146)\] Display dump of dicom document when displaying WADO-RS response
+* \[[GWT-147](https://gazelle.ihe.net/jira/browse/GWT-147)\] Display response HTTP header
+
# 1.7.4
_Release date: 2021-07-19_
diff --git a/Gazelle-Webservice-Tester/user.md b/Gazelle-Webservice-Tester/user.md
index 96dc13e6d5be6ea944770e084f0f5d12a86a9eaa..e64a064cc74250b8ab24a3c022d69692e9ce5c11 100755
--- a/Gazelle-Webservice-Tester/user.md
+++ b/Gazelle-Webservice-Tester/user.md
@@ -4,7 +4,7 @@ subtitle: Gazelle Webservice Tester
author: Malo TOUDIC
function: Software developer
date: 05/03/2019
-toolversion: 1.7.x
+toolversion: 1.8.x
version: 1.02
status: Approved document
reference: KER1-MAN-IHE-GAZELLE_WEBSERVICE_TESTER_USER
diff --git a/HPD-Simulator/release-note.md b/HPD-Simulator/release-note.md
index c56d071da1733a38fdc0e133f9231821370e7e15..46878fb8bdd25611ed54e9a1d5042b30043218f6 100755
--- a/HPD-Simulator/release-note.md
+++ b/HPD-Simulator/release-note.md
@@ -1,13 +1,25 @@
---
title: Release note
subtitle: HPDSimulator
-toolversion: 2.4.3
-releasedate: 2023-06-12
+toolversion: 2.4.5
+releasedate: 2023-12-08
author: Malo TOUDIC
function: Software Developer
customer: IHE Europe
reference: KER1-RNO-IHE-HPD_SIMULATOR
---
+# 2.4.5
+_Release date: 2023-12-08_
+
+__Bug__
+* \[[HPD-221](https://gazelle.ihe.net/jira/browse/HPD-221)\] [CH] Wrong value set IDs in HPD validation constraint
+
+# 2.4.4
+_Release date: 2023-12-07_
+
+__Bug__
+* \[[HPD-220](https://gazelle.ihe.net/jira/browse/HPD-220)\] [CH:HPD] UID Format: . and _ need to be added to the list of special characters that don't need to be escaped
+
# 2.4.3
_Release date: 2023-06-12_
diff --git a/HTTP-Validator/release-note.md b/HTTP-Validator/release-note.md
index e077d98ecb56c0db5af5db636c27aa28179a56d5..1338895453c55c45c6e6732b0508406c1f8d3678 100644
--- a/HTTP-Validator/release-note.md
+++ b/HTTP-Validator/release-note.md
@@ -2,7 +2,7 @@
title: Release note
subtitle: HTTP Validator
toolversion: 0.3.0
-releasedate: 2023-08-28
+releasedate: 2023-09-19
author: Clément LAGORCE
function: Software Engineer
customer: IHE Europe
@@ -10,7 +10,7 @@ reference: KER1-RNO-IHE-HTTP_VALIDATOR
---
# 0.3.0
-_Release date: 2023-08-28_
+_Release date: 2023-09-19_
__Story__
* \[[HTTP-16](https://gazelle.ihe.net/jira/browse/HTTP-16)\] Release/Doc
diff --git a/Makefile b/Makefile
index 837346660a41834330cc1d690bddd12a52b4e6fc..6265050ebdf8dfe258ff14c2fbfa34f1cc4840e6 100755
--- a/Makefile
+++ b/Makefile
@@ -7,6 +7,18 @@ TEMPLATE_JEKYLL = _templates/jekyll-gazelle-documentation
DOCS := $(filter-out _templates/,$(DOCS))
DOCS := $(filter-out target/,$(DOCS))
+# Répertoire source où se trouvent les fichiers Markdown
+SOURCE_DIR := $(CURDIR)
+
+# Récupère tous les fichiers Markdown récursivement dans SOURCE_DIR
+MARKDOWN_FILES := $(shell find $(SOURCE_DIR) -type f -name "*.md")
+
+# Génère la liste des répertoires uniques où se trouvent les fichiers Markdown
+DIRS := $(sort $(dir $(MARKDOWN_FILES)))
+
+# Remplace l'extension .md par .pdf pour les fichiers cibles
+PDF_FILES := $(patsubst $(SOURCE_DIR)/%.md,$(OUTPUT_FOLDER)/%.pdf,$(MARKDOWN_FILES))
+
all: clean jekyll $(DOCS)
$(DOCS): force | $(OUTPUT_FOLDER)
@@ -62,6 +74,7 @@ copy_source_to_jekyll:
@echo "Done!"
.PHONY: clean
+
clean:
-rm -rf $(OUTPUT_FOLDER)
@for a in $(DOCS); do \
@@ -71,3 +84,13 @@ clean:
fi; \
done;
@echo "All clear!"
+
+# Règle par défaut pour générer tous les PDF. Attention avec les tableaux il peut y avoir des problèmes de rendu voir README
+pdf-gen: $(PDF_FILES)
+
+# Règle pour convertir un fichier Markdown en PDF
+$(OUTPUT_FOLDER)/%.pdf: $(SOURCE_DIR)/%.md
+ @mkdir -p $(@D) # Crée le répertoire cible s'il n'existe pas
+ cd $(dir $<) && pandoc $< -N -s --toc --pdf-engine=xelatex -o $(SOURCE_DIR)/$@
+
+
diff --git a/Patient-Manager/user.md b/Patient-Manager/user.md
index 41cb8bbee9f46d633bf2e9fd1ca1da4185042852..7875ec1156ac5c1c6ab76d2f8b53aced57c785f9 100755
--- a/Patient-Manager/user.md
+++ b/Patient-Manager/user.md
@@ -643,30 +643,30 @@ The Patient Manager is able to act as a Patient Demographics Supplier for the Pa
The table below gathers the parameters the simulator is able to map to its database to perform the query and send back the batch of corresponding patients. Note that when several parameters are provided, the AND operator is used to build the database query; the "\*" wildcard is supported to substitute zero or more characters. The returned patients are those owned by the Patient Demographic Supplier actor. To consult the list of available patients, see [*https://gazelle.ihe.net/PatientManager/patient/allPatients.seam?actor=PDS*](https://gazelle.ihe.net/PatientManager/patient/allPatients.seam?actor=PDS)Â . Note that only the subset of active patients is queried.
-| **HL7 FIELDÂ ** | **Â ELEMENT NAME** | Â **JAVA OBJECT / ATTRIBUTE (indicative)**Â | **Â SQL CLAUSEÂ ** | **Â EXTRA INFO** |
-|----------------|----------------------------------------------------------------------|--------------------------------------------|-------------------------------------------------------|--------------------------------|
-| **PID.3** | Patient Identifier List | patient.patientIdentifiers | like (ignores case) | also filter according to QPD-8 |
-| **PID.3.1** | Patient Identifier List (ID Number) | patientIdentifer.fullPatientId | like (ignores case), MatchMode = START | |
-| **PID.3.4.1** | Patient Identifier List (Assigning Authority - namespace ID) Â | Â patientIdentifier.domain.namespaceIDÂ | domain namespaceID like (ignores case)Â | |
-| **PID.3.4.2** | Patient Identifier List (Assigning Authority - universal ID) | patientIdentifier.domain.universalID | Â domain universal ID like (ignores case)Â | |
-| **PID.3.4.3** | Patient Identifier List (Assigning Authority - universal ID Type) |  patietnIdentifier.domain.universalIDType |  domain universal ID type  like (ignores case) | |
-| **PID.3.5** | Patient Identifier List (Identifier Type Code) | patientIdentifier.identifierTypeCode | like (ignores case) | |
-| **PID.5.1.1 ** | Patient Name (family name/surname) | patient.lastName | like (ignores case) | |
-| **PID.5.2** | Patient Name (given name) | patient.firstName | like (ignores case) | |
-| **PID.7.1** | Date/Time of Birth | patient.dateOfBirth | between 'date 0:00 am' to 'date 11:59 pm' | date format : yyyyMMddHHmmss |
-| **PID.8** | Administrative Sex | patient.genderCode | equals | Gender code (F, M ...) |
-| **PID.11.1** | Patient Address (Street) | patient.street | like (ignores case) | |
-| **PID.11.3** | Patient Address (City) | patient.city | like (ignores case) | |
-| **PID.11.4** | Patient Address (State) | patient.state | like (ignores case) | |
-| **PID.11.5** | Patient Address (Zip Code) | patient.zipCode | like (ignores case) | |
-| **PID.11.6** | Patient Address (Country Code) | patient.countryCode | like (ignores case) | iso3 |
-| **PID.18** | Patient Account Number | patient.accountNumber | like (ignores case) | |
-| **PID.18.1** | Patient Account Number  (ID Number) | patient.accountNumber | like (ignores case), MatchMode = START | |
-| **PID.18.4.1** | Patient Account Number  (Assigning Authority - namespace ID) | patient.accountNumber |  like (ignores case) %^^^value, MatchMode = START | |
-| **PID.18.4.2** | Patient Account Number  (Assigning Authority - universal ID) | patient.accountNumber | like (ignores case) %^^^%&value, MatchMode = START | |
-| **PID.18.4.3** | Patient Account Number  (Assigning Authority - universal ID Type)   | patient.accountNumber |  like (ignores case) %^^^%&%&value, MatchMode = START | |
-| **PID.6.1.1** | Mother's maiden name (last name) | patient.mothersMaidenName | like (ignores case) | |
-| **PID.13.9** | Phone Number - Home (any text) | patient.phoneNumber | like (ignores case) | |
+| **HL7 FIELDÂ ** | **Â ELEMENT NAME** | Â **JAVA OBJECT / ATTRIBUTE (indicative)**Â | **Â SQL CLAUSEÂ ** | **Â EXTRA INFO** |
+|--------------------|----------------------------------------------------------------------|--------------------------------------------|-------------------------------------------------------|--------------------------------|
+| **PID.3** | Patient Identifier List | patient.patientIdentifiers | like (ignores case) | also filter according to QPD-8 |
+| **PID.3.1** | Patient Identifier List (ID Number) | patientIdentifer.fullPatientId | like (ignores case), MatchMode = START | |
+| **PID.3.4.1** | Patient Identifier List (Assigning Authority - namespace ID) Â | Â patientIdentifier.domain.namespaceIDÂ | domain namespaceID like (ignores case)Â | |
+| **PID.3.4.2** | Patient Identifier List (Assigning Authority - universal ID) | patientIdentifier.domain.universalID | Â domain universal ID like (ignores case)Â | |
+| **PID.3.4.3** | Patient Identifier List (Assigning Authority - universal ID Type) |  patietnIdentifier.domain.universalIDType |  domain universal ID type  like (ignores case) | |
+| **PID.3.5** | Patient Identifier List (Identifier Type Code) | patientIdentifier.identifierTypeCode | like (ignores case) | |
+| **PID.5.1.1 ** | Patient Name (family name/surname) | patient.lastName | like (ignores case) | |
+| **PID.5.2** | Patient Name (given name) | patient.firstName | like (ignores case) | |
+| **PID.7.1** | Date/Time of Birth | patient.dateOfBirth | between 'date 0:00 am' to 'date 11:59 pm' | date format : yyyyMMddHHmmss |
+| **PID.8** | Administrative Sex | patient.genderCode | equals | Gender code (F, M ...) |
+| **PID.11.1** | Patient Address (Street) | patient.street | like (ignores case) | |
+| **PID.11.3** | Patient Address (City) | patient.city | like (ignores case) | |
+| **PID.11.4** | Patient Address (State) | patient.state | like (ignores case) | |
+| **PID.11.5** | Patient Address (Zip Code) | patient.zipCode | like (ignores case) | |
+| **PID.11.6** | Patient Address (Country Code) | patient.countryCode | like (ignores case) | iso3 |
+| **PID.18** | Patient Account Number | patient.accountNumber | like (ignores case) | |
+| **PID.18.1** | Patient Account Number  (ID Number) | patient.accountNumber | like (ignores case), MatchMode = START | |
+| **PID.18.4.1** | Patient Account Number  (Assigning Authority - namespace ID) | patient.accountNumber |  like (ignores case) %^^^value, MatchMode = START | |
+| **PID.18.4.2** | Patient Account Number  (Assigning Authority - universal ID) | patient.accountNumber | like (ignores case) %^^^%&value, MatchMode = START | |
+| **PID.18.4.3** | Patient Account Number  (Assigning Authority - universal ID Type)   | patient.accountNumber |  like (ignores case) %^^^%&%&value, MatchMode = START | |
+| **PID.6.1.1** | Mother's maiden name (last name) | patient.mothersMaidenName | like (ignores case) | |
+| **PID.13.9** | Phone Number - Home (any text) | patient.phoneNumber | like (ignores case) | |
Table 1 PDQ - PDS - ITI-21 query parameters
diff --git a/Patient-Manager/user.md~ b/Patient-Manager/user.md~
new file mode 100755
index 0000000000000000000000000000000000000000..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391
diff --git a/Patient-Registry/installation.md b/Patient-Registry/installation.md
index 253e5c3fa9546b0ab5fb176d4d8699ba5a6b6ca6..973edb1a5c50f9bed0c093e414125e9bf76d091b 100755
--- a/Patient-Registry/installation.md
+++ b/Patient-Registry/installation.md
@@ -105,6 +105,7 @@ Define a resource in your server with name *java:/app/gazelle/pdqm-connector/ope
This resource should refer to a deployment.properties file. This file shall contain the following properties :
| Property Name | Description | Example value |
+|--------------|-----------|------------|
| patientregistry.url | URL of the Patient Registry Processing Service used to manage patients. | http://localhost:8580/patient-registry/patient-registry/PatientProcessingService/patient-processing-service?wsdl|
### Application server
@@ -307,4 +308,4 @@ cp pixm-connector-X.X.X.war /usr/local/wildfly18/standalone/deployments/pixm-con
Start wildfly. The API can be accessed at (depending on your configured host and port)
* ITI-83 : [GET http://localhost:8580/pixm-connector/fhir_ihe/Patient/$ihe-pix?sourceIdentifier={sourceIdentifier}(&targetSystem={targetsystem,...})(&_format=json)](http://localhost:8580/pixm-connector/fhir_ihe/Patient/$ihe-pix?sourceIdentifier={sourceIdentifier}(&targetSystem={targetsystem,...})(&_format=json))
-* ITI-93 : shall be reachable to perform a feed. Create and Delete method have been implemented.
\ No newline at end of file
+* ITI-93 : shall be reachable to perform a feed. Create and Delete method have been implemented.
diff --git a/Proxy/release-note.md b/Proxy/release-note.md
index c94f9f880bc9ba306c2cf1273d340a24914f5149..cd0df33a0f0b97c870e652ede33154a3313b0285 100755
--- a/Proxy/release-note.md
+++ b/Proxy/release-note.md
@@ -1,8 +1,8 @@
---
title: Release note
subtitle: Proxy
-toolversion: 5.1.0
-releasedate: 2023-07-11
+toolversion: 6.0.0
+releasedate: 2024-01-18
author: Anne-Gaëlle BERGE
function: Software Engineer
customer: IHE Europe
@@ -62,6 +62,15 @@ __Task__
* \[[PROXY-298](https://gazelle.ihe.net/jira/browse/PROXY-298)\] Custom pipeline fork
* \[[PROXY-311](https://gazelle.ihe.net/jira/browse/PROXY-311)\] System Tests Proxy V17
+# 5.1.1
+_Release date: 2023-12-13_
+
+__Bug__
+* \[[PROXY-302](https://gazelle.ihe.net/jira/browse/PROXY-302)\] Cannot log with ipLogin
+
+__Story__
+* \[[PROXY-303](https://gazelle.ihe.net/jira/browse/PROXY-303)\] Dump Dicom to xml in WADO-RS responses
+
# 5.1.0
_Release date: 2023-07-11_
diff --git a/Proxy/user.md b/Proxy/user.md
index e43ae7e60723a75424fdc99db9c3804b907e5c68..0e997dc595276c4c797dd46b8e649737219cef49 100755
--- a/Proxy/user.md
+++ b/Proxy/user.md
@@ -2,8 +2,8 @@
title: User Manual
subtitle: Gazelle Proxy
author: Nicolas BAILLIET
-date: 12/07/2023
-toolversion: 5.1.0
+date: 13/12/2023
+toolversion: 5.1.1
function: Engineer
version: 2.01
status: Approved document
diff --git a/README.md b/README.md
index d6f727e9beb73078593021f85d427469864d043b..c502fce8de2c3cc0a6120617b295a366518b4836 100755
--- a/README.md
+++ b/README.md
@@ -23,10 +23,10 @@ Document is then available at <http://localhost:1080/gazelle-documentation/>
### setup
```bash
-sudo apt-get install make git git-svn texlive-xetex pandoc ruby-dev
+sudo apt-get install make git git-svn texlive-xetex pandoc ruby-dev build-essential dh-autoreconf
```
-Then, from `gazelle-dev-documentation` folder run to install some more libs and required gems
+Then, from `gazelle-dev-documentation` folder run to install some more libs and required gems
```bash
make setup
@@ -37,18 +37,22 @@ make setup
make
```
-### Generate all the documents and start Jekyll (do not use in production)
-```shell
-make view
-```
-### Generate the PDF version of the release note
-```shell
-make release-notes
+### Add a gem in the bundle
+```bash
+cd target/jekyll-gazelle-documentation
+sudo bundle add webrick
+sudo bundle install
+
+
```
-Check target/ folder for results
+### Generate all the documents and start Jekyll (do not use in production)
+```bash
+sudo bundle exec jekyll serve
+```
+Once it is done you server must have been started on localhost:4000/gazelle-documentation/
## Folder structure
gazelle-documentation
@@ -89,6 +93,28 @@ The YAML header is used by Jekyll and pandoc to generate menus and front pages,
The YAML header is used by Jekyll and pandoc to generate menus and front pages, make sure all the metadata are present and up-to-date. The *.md files must start with the YAML header.
+## Conversion Markdown to Pdf files
+
+To generate pdf files use the command (might take some times)
+
+```bash
+sudo make -i pdf-gen
+```
+
+you can use
+```bash
+sudo make clean
+```
+to remove all generated files
+
+!!WARNING!!
+Be careful with table in markdown they may break your pdf if table are too big.
+
+In any case if your pdf is break you might want to use the extension markdown pdf with visual studio code.
+
+With this extension you can generate pdf one by one with command available in the extension.
+
+Table with this extension are correct
## Links
@@ -96,4 +122,3 @@ http://pandoc.org/
[Pandoc installation package](https://github.com/jgm/pandoc/releases/tag/1.17.2)
-http://blog.cigrainger.com/2014/07/pandoc-markdown.html
diff --git a/Test-Management/admin.md b/Test-Management/admin.md
index 8e631d8e6f41e831bf7c7607a352ae0cb46a114b..d9188abbf1f25fe4caa44c945ffa7125184f5cd9 100755
--- a/Test-Management/admin.md
+++ b/Test-Management/admin.md
@@ -2,8 +2,8 @@
title: Administration guide
subtitle: Gazelle Test Management
author: Nicolas BAILLIET
-function: Software ngineer
-releasedate: 12/09/2023
+function: Software Engineer
+releasedate: 06/11/2023
toolversion: 7.X.X
version: 1.02
status: Approved document
@@ -654,10 +654,8 @@ From this page, you can see what are the active testing sessions, active/inactiv
From the Administration of testing sessions page, click on "Add an event"; a new form will be displayed. The following information are requested
-- Year : when the testing event takes place
-- Zone : where the testing event takes place
-- Type : what type of event are you registering
-- Description : will be used as title of the testing session
+- Name : will be used as title of the testing session, it's unique and mandatory
+- Description : optionally describe the testing session
- Start date : beginning of the testing event itself
- End date : end of the testing event
- Registration deadline : after this date, users will not be able to alter their system (addition/removal of actor/profile)
diff --git a/Test-Management/conformance_tool.md b/Test-Management/conformance_tool.md
index c55a574122d3fac798809b1235cf62aa6a7f4df0..a9302760a36a424c36e01027202121714dad8041 100755
--- a/Test-Management/conformance_tool.md
+++ b/Test-Management/conformance_tool.md
@@ -3,7 +3,7 @@ title: Launching Conformance Tool of XDS Tools from Gazelle Test Management
subtitle: Gazelle Test Management
author: Malo TOUDIC
function: Developer
-date: 13/06/2018
+date: 06/11/2023
version: 0.01
status: Draft
reference: KER1-MAN-IHE-TEST_MANAGEMENT_GWT_XDSTOOLS-0_01
diff --git a/Test-Management/installation.md b/Test-Management/installation.md
index a6fcfc1f44f6c72d3c1546b0f2eaba88bd9cd8fa..c2fa875f24c85e7d3d1448f095a0271b9b5ae83e 100755
--- a/Test-Management/installation.md
+++ b/Test-Management/installation.md
@@ -2,8 +2,8 @@
title: Installation manual
subtitle: Gazelle Test Management
author: Nicolas BAILLIET
-function: Engineer
-releasedate: 12/09/2023
+function: Software Engineer
+releasedate: 06/11/2023
toolversion: 7.X.X
version: 1.02
status: Approved document
@@ -196,12 +196,22 @@ therefore, an administrator should insert manually his HTML content in the table
By default, two sections (Documentation and Announcement) are displayed only in the home page, the other two sections
(Tool index and Credits) are visible through all the application pages.
-### Update section
+### Update section priors to 7.0.1
`update tm_section update content='<YOUR_HTML_CONTENT>' where id=<SECTION_ID>`
+
+### Update section since version 7.0.1
+
+The administrator of the current session have access to the Home Page Manager via Administration menu.
+By default, the announcement section is selected. It can be changed via the drop-down menu.
+The selected section can be edited via this page. The `Save and Continue` button will update the section.
+Restore button restore the previous version of the selected section.
+
+
+
## Version priors to 6.3.0
The home page is built of two blocks the administrators can customize when they are logged in.
diff --git a/Test-Management/media/home_page_manager.png b/Test-Management/media/home_page_manager.png
new file mode 100644
index 0000000000000000000000000000000000000000..c53ecd657624091d86dda2efb2d36b0225f1db5c
Binary files /dev/null and b/Test-Management/media/home_page_manager.png differ
diff --git a/Test-Management/release-note.md b/Test-Management/release-note.md
index 48e306fa9b0b991b5e382398753791a668517025..9d4ba3fc8c8b2f9e14829fe5eada647253e2ade0 100755
--- a/Test-Management/release-note.md
+++ b/Test-Management/release-note.md
@@ -1,18 +1,66 @@
---
title: Release note
subtitle: Test Management
-toolversion: 7.1.0
-releasedate: 2023-09-11
+toolversion: 7.1.6
+releasedate: 2024-01-04
author: Anne-Gaëlle BERGE
function: Software Engineer
customer: IHE Europe
reference: KER1-RNO-IHE-TEST_MANAGEMENT
---
+# 7.1.6
+_Release date: 2024-01-04_
+
+__Bug__
+* \[[GZL-5306](https://gazelle.ihe.net/jira/browse/GZL-5306)] Display test menu entry as not logged in" is not functionnal
+* \[[GZL-5307](https://gazelle.ihe.net/jira/browse/GZL-5307)] Anonymous users can download the IHE mode
+
+# 7.1.5
+_Release date: 2023-11-06_
+
+__Remarks__
+
+Update gazelle-model, release 5.0.2
+
+Update gazelle-tm-tools, release 4.1.7
+
+__Tâche__
+
+* \[[GZL-5247](https://gazelle.ihe.net/jira/browse/GZL-5247)\] Make testing session uniquely identified
+
+__Bug__
+* \[[GZL-5271](https://gazelle.ihe.net/jira/browse/GZL-5271)\] Impossible to create a new testing session in TM.
+* \[[GZL-5273](https://gazelle.ihe.net/jira/browse/GZL-5273)\] Some unit tests don't pass anymore
+* \[[GZL-5273](https://gazelle.ihe.net/jira/browse/GZL-5277)\] A modification of a testing session name is not well reported
+
+# 7.1.4
+_Release date: 2023-10-13_
+
+__Bug__
+* \[[GZL-5265](https://gazelle.ihe.net/jira/browse/GZL-5265)\] Test run are no more accessible if EVS link is wrong.
+
+# 7.1.3
+_Release date: 2023-10-09_
+
+__Tâche__
+* \[[GZL-5268](https://gazelle.ihe.net/jira/browse/GZL-5268)\] Invalid Dashboard value in Evaluation for capabilities
+* \[[GZL-5269](https://gazelle.ihe.net/jira/browse/GZL-5269)\] TM-Remove report button for vendors
+
+# 7.1.2
+_Release date: 2023-09-20_
+
+__Bug__
+* \[[GZL-5252](https://gazelle.ihe.net/jira/browse/GZL-5252)\] Metatests not properly displayed on Test Execution page
+
+# 7.1.1
+_Release date: 2023-09-14_
+
+__Bug__
+* \[[GZL-5260](https://gazelle.ihe.net/jira/browse/GZL-5260)\] Admin cannot access the list of registered SUT and manage them
# 7.1.0
_Release date: 2023-09-11_
-
__Bug__
* \[[GZL-5164](https://gazelle.ihe.net/jira/browse/GZL-5164)\] Test session creation - setting dates for time-boxed test sessions
* \[[GZL-5220](https://gazelle.ihe.net/jira/browse/GZL-5220)\] Fix GMM and PR home page
@@ -70,7 +118,7 @@ __Task__
* \[[GZL-5201](https://gazelle.ihe.net/jira/browse/GZL-5201)\] [GUM] Remove block account possibility in TM
* \[[GZL-5209](https://gazelle.ihe.net/jira/browse/GZL-5209)\] [GUM] Remove log as feature from TM
-See also [GUM release note](../Gazelle-User-Management/release-note.html).
+See also [GUM release note](https://doc-ihe.kereval.cloud/gazelle-applications/v/gazelle-user-management/release-note).
# 6.10.4
_Release date: 2023-06-23_
diff --git a/Test-Management/user.md b/Test-Management/user.md
index 46c7a7fcffcee592a5b6a1cb89f12bea075eeb9a..a2378725ee18a87e6896823006e7a7d8e86de9e8 100755
--- a/Test-Management/user.md
+++ b/Test-Management/user.md
@@ -3,7 +3,7 @@ title: User manual
subtitle: Gazelle Test Management
author: Anne-Gaëlle Bergé
function: Engineer
-releasedate: 12/09/2023
+releasedate: 06/11/2023
toolversion: 7.X.X
version: 2.01
status: Validated
diff --git a/Wado-Errors-Manager/user.md b/Wado-Errors-Manager/user.md
index 325afb29096e3dfc7e96074ee24812a6dfbc282b..2908a5b3730fd67eec8e5e97e42b6bf907749ec4 100755
--- a/Wado-Errors-Manager/user.md
+++ b/Wado-Errors-Manager/user.md
@@ -1,6 +1,6 @@
---
subtitle: Wado Errors Manager
-title: Installation Manual
+title: User Manual
author: Romuald DUBOURG
date: 08/09/2023
toolversion: 1.0.0
diff --git a/XDStar-Client/release-note.md b/XDStar-Client/release-note.md
index 404cdb1beb4a186c6de8adae8f53fc956cdfb120..2311c208671b9a4dd0dd29ca48e418f578fef6ce 100755
--- a/XDStar-Client/release-note.md
+++ b/XDStar-Client/release-note.md
@@ -1,7 +1,7 @@
---
title: Release note
subtitle: XDStarClient
-toolversion: 2.5.13
+toolversion: 2.5.14
releasedate: 2023-07-04
author: Anne-Gaëlle BERGE
function: Software Engineer
@@ -52,6 +52,10 @@ __Story__
# 2.5.8
_Release date: 2021-09-19_
+__Bug__
+* \[[XDSTAR-775](https://gazelle.ihe.net/jira/browse/XDSTAR-775)\] [eHS][XDS.b] ITI-18 validator - $MetadataLevel shall equal to 1
+* \[[XDSTAR-776](https://gazelle.ihe.net/jira/browse/XDSTAR-776)\] [eHS][XDS.b] ITI-41 validator - DocumentEntry.Title should be mandatory
+
__Story__
* \[[XDSTAR-763](https://gazelle.ihe.net/jira/browse/XDSTAR-763 )\] Swiss adaptations 3.1