Sources and package

Schematron-based Validator is a maven project. Sources are available on the INRIA Source Forge at the following URL:

https://gitlab.inria.fr/gazelle/public/validation/schematron-validator.git

If you’d like to checkout the sources on your system you might want to use the following git command, provided subversion is installed on your system.

git clone https://gitlab.inria.fr/gazelle/public/validation/schematron-validator.git

Note that the latest executable can be extracted from our nexus repository as well  at Nexus Repository Manager.

Important, if you download the ear from Nexus it will have a name such as SchematronValidator-ear-2.0.0.ear, then be sure to rename it to SchematronValidator.ear otherwise the deployment will fail.

Installation

This tool is to be installed in a Jboss 7.2 application server and runs with a PosgreSQL database.

If you do not have yet a Jboss installed in your environment, proceed as described in General consideration page.

Database creation

Your database must have a user gazelle.

1. Download the SQL scripts archive from Nexus Repository Manager (search for SchematronValidator-ear-X.X.X-sql.zip).
2. Unzip the archive into a folder SchematronValidator-sql
3. Connect to your database

   psql -U gazelle
   

4. Excute the SQL statement to create the database.

   CREATE DATABASE schematron-validator-prod OWNER gazelle ENCODING UTF8 ;
   

5. Initialize database by running :

   psql -U gazelle schematron-validator-prod < SchematronValidator-sql/init.sql
   

Deployment

To deploy Schematron Validator:

1. Paste the archive SchematronValidator.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/SchematronValidator. Port could also be different whether you have modified the JBoss configuration.
4. WARNING : From version 2.5.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 Schematronvalidator-X.X.X-datasource.zip from the nexus. For more informations about how to manage that externalization, please refer to general considerations for JBoss7.

Datasource name : SchematronValidatorDS

Database name : schematron-validator-prod

1. WARNING : Since version 2.5.1, you need to configure the mail session that is needed by the tool in the jboss configuration file standalone.xml. Read details in the “Externalize mail server configuration” section of JBoss 7 installation page for further information.

Data storage

Schematron Validator will need directories to store XSD and schematrons. By default, the application is configured to use /opt/SchematronValidator_prod.

sudo mkdir /opt/SchematronValidator_prod
sudo mkdir /opt/SchematronValidator_prod/bin
sudo mkdir /opt/SchematronValidator_prod/xsd

The repository /bin shall contain schematron, compilation and ART-DECOR_precompilation_tools repositories and the jar file XSDValidator-1.0-jar-with-dependencies.jar. It is available via Subversion at https://svn.ihe-europe.net/gazelle/Maven/ihe-xmltools-jar/trunk/src/test/resources/jar/

Be sure the directory can be read/written by JBoss.

sudo chmod -R 775 /opt/SchematronValidator_prod
sudo chown -R jboss:jboss-admin /opt/SchematronValidator_prod

Update from a previous version

1. Download the new ear and its associated update SQL script from our Nexus Repository Manager (search for SchematronValidator-X.X.X.ear and SchematronValidator-X.X.X-sql.zip). Not each version has an update sql to execute.

2. Unzip the SQL archive

3. Execute SQL statements. Check that the database is correctly updated.

4. Deploy the new ear

Due to the update mechanism of the database, it is important to not skip any version of the application in an overall update. You cannot go directly from 2.0.0 to 2.3.0, you will have to repeat the process from 2.0.0 to 2.0.1, 2.0.2, 2.0.3 and so on.

Configuration

SSO Configuration

There are additional preferences to configure the SSO authentication.

For more documentation about SSO configurations, follow the link here.