From d3181ed349795cf7875a6b80fa1098b7a55eaf8d Mon Sep 17 00:00:00 2001
From: Youn <yct@kereval.com>
Date: Tue, 27 Oct 2020 15:27:58 +0100
Subject: [PATCH] [GT-138] Update documentation, I added datasource part
---
Assertion-Manager/installation.md | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/Assertion-Manager/installation.md b/Assertion-Manager/installation.md
index 4cd4e94..5b80a71 100755
--- a/Assertion-Manager/installation.md
+++ b/Assertion-Manager/installation.md
@@ -40,6 +40,18 @@ It will:Â
* Get the latest released version of Assertion Manager and deploy it in your JBoss server.
* Create the database if it doesn't exist.
+## Deployment
+To deploy Assertion Manager:
+1. Paste the archive **AssertionManagerGui.ear** in the JBoss deployment directory `${JBOSS7\_HOME}/standalone/deployments/`
+2. Display JBoss server logs, start JBoss and wait for **ear** deployment.
+3. The application can be browsed at http://localhost:8080/AssertionManagerGui. *Port could also be different whether you have modified the JBoss configuration*.
+4. **WARNING** : From version 4.2.0, datasources have been extracted from the **ear**. The template file can be found in /src/main/application/datasource in the source or in the file AssertionManager-X.X.X-datasource.zip from the nexus.
+For more informations about how to manage that externalization, please refer to [general considerations for JBoss7](https://gazelle.ihe.net/gazelle-documentation/General/jboss7.html).
+
+Datasource name : AssertionManagerBaseDS
+
+Database name : assertion-manager
+
## Insert configuration values
Configuration can be done through the Administration interface or with an sql script.
--
GitLab