Schematron-based Validator is a maven project. Sources are available on the INRIA Source Forge at the following URL:
If you’d like to checkout the sources on your system you might want to use the following svn command, provided subversion is installed on your system.
svn checkout svn://scm.gforge.inria.fr/svn/gazelle/Maven/SchematronValidator/trunk
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.
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.
Your database must have a user gazelle.
psql -U gazelle
CREATE DATABASE schematron-validator-prod OWNER gazelle ENCODING UTF8 ;
psql -U gazelle schematron-validator-prod < SchematronValidator-sql/init.sql
To deploy Schematron Validator:
Schematron Validator will need directories to store XSD and schematrons. By default, the application is configured to use
sudo mkdir /opt/SchematronValidator_prod sudo mkdir /opt/SchematronValidator_prod/bin sudo mkdir /opt/SchematronValidator_prod/xsd
/bin shall contain
ART-DECOR_precompilation_tools repositories and the jar file
XSDValidator-1.0-jar-with-dependencies.jar. It is available via Subversion at https://gforge.inria.fr/scm/viewvc.php/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
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.
Unzip the SQL archive
Execute SQL statements. Check that the database is correctly updated.
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.
|Preference name||Description||Default value|
|application_admin_email||An email address. Administrator of the tool might received messages when errors occur in the application such as compilation failure of schematron||-|
|application_admin_name||Application admin name||-|
|application_admin_title||Application admin title||Application Administrator|
|application_build_time||Application build time||July 12, 2010 - 11:59 AM|
|application_name||The name of the application||Schematron Validator|
|application_profile||The profile of the deployed application||prod|
|application_url||The public URL of the tool||http://yourDomain/SchematronValidator|
|application_works_without_cas||If true, any user might be granted with admin role. If false, the tool is bound to a CAS service for user authentication||false|
|bin_path||Relative path to the folder in which are stored the schematrons||bin|
|cas_enabled||If true, the CAS service for user authentication is used||true|
|cas_url||URL of the central authentication service||http://yourDomain/cas|
|cda_xsd_path||absolute path to the XSD file used for validating CDA||/opt/SchematronValidator_prod/xsd/cda/CDA.xsd|
|documentation_url||Link to the user guide||https://gazelle.ihe.net/gazelle-documentation/Schematron-Validator/user.html|
|epsos_cda_xsd_path||absolute path to the XSD file used for validating epSOS CDA|
|gazelle_home_path||absolute path to the directory in which are stored the files used by the tool||/opt/SchematronValidator|
|ip_login||If application_works_without_cas = true, authentication is based on user’s IP||false|
|ip_login_admin||Regex to be matched by the IP addresses of the users who can be granted as admin||.*|
|mif_root_directory||Relative path to the folder where are stored the MIF files||/mif|
|monitor_email||The email of the second person who will receive failure notification from the tool||-|