XML Validation Tool
Automated Validation and Certification of Trading Partners’ Messages to Standardize Initial and Ongoing Information Exchange
The Validation Server enables the automated validation and certification of trading partners’ messages to standardize initial and ongoing information exchange. A company that is receiving the same messages from multiple trading partners can “publish” their message formats and rules to allow the trading partners to test their message / transactions before going “live”.
Because Validations are configured using the XCS eiConsole, and deployed to the XCS eiPlatform in exactly the same way that interfaces are deployed, there is enormous flexibility relative to the Submission, Validation and Responses to test messages.
The Validation Server can accept incoming “test documents” through a variety of protocols, including but not limited to email, HTTP, HTML Form and FTP. A trading partner wishing to validate their messages may submit those messages in any of a variety of different ways. For instance, a developer wishing to test a new transaction may alternatively:
- Send an email with “Transaction Test” in the subject line
- Post the XML to test.yourcompany.com
- Select the transaction to be tested from a drop-down on a web page
- FTP a file to a directory on test.yourcompany.com
Inbound test documents can be subject to any required validation through a “pluggable” validation architecture. Validation rules can be expressed in XML Schema, Schematron or in a custom XML validation dialect.
Validation models can be “layered”, where a number of different models are applied to the same instance document. For example, the same document may be validated against:
- The Schema
- Certification Rules
- Your Company-Specific Implementation Rules
- Trading Partner-Specific Implementation Rules
This approach also has the benefit of exposing those areas where partners’ interpretations are at odds with yours, or with the standard itself.
Validation results can be produced as XML, or as a human-readable HTML report. This report enumerates the rules executed against a particular instance document, the success or failure of the aforementioned rules and any relevant details in the case of a failure. The report is returned to the submitter through the appropriate transport protocol (email, HTTP, web page, FTP, etc).