Mentions légales du service

Skip to content
Snippets Groups Projects
Commit add10f47 authored by romuald dubourg's avatar romuald dubourg
Browse files

[Update] gazelle token doc

parent 919ba50b
No related branches found
No related tags found
No related merge requests found
......@@ -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.
![EVSClient architecture](./media/installation/UML_Global_GazelleTokenApi.png)
![GazelleTokenApi architecture](./media/installation/UML_Global_GazelleTokenApi.png)
## 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
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment