• B2B ADAPTERS - PROCESSORS
• Transaction Attributes
• Key Encryption
• B2B Authentication
• Charset Conversion
• EBCDIC to ASCII
• Base64 Encoder
• Chained Transactions
• Data Attribute Swapper
• Zip / Unzip
• XLS to XML
• MD5 Hashing
• Java XML Binding
• MIME Decoder
• MIME Encoder
• MTOM
• TIFF to XML
• Remove Namespaces
• Regex Evaluation
• Add SOAP Header
• Symmetric Encryption
• XML Logging
• XML Validation Rules
• WS-Security
• XML to PDF
• XPath Evaluation

XML Validation Rules

The XCS eiConsole's Validation Processor Allows Validating the Inbound Data Stream Against External Sources – Files, Databases and Contextual Information

The Validation Processor supports a robust validation model. This validation model will allow you to accomplish three levels of validation. At the core this validation is field level, which can be accomplished through XML schema. At the next level you can implement validation rules that cross boundaries between fields to check items like the conditional requirements of one field based on the content of another. These rules can be implemented through XSLT, schematron or custom validation modules. The third level is external context validation. This will allow you to validate the inbound data stream against external sources (files, databases, contextual information).

The details of how these modules are set up are available in reference materials. These are all configured using the Validation processor. As with all the components of the eiConsole the user is presented with a graphical interface with easy to configure panels. The steps are:

Choose the Validation Processor from the Add Processor menu.

Name the Processor: InboundValidation and hit Add.

The Validation Processor configuration includes Model Files. Model files are XML files that specify the validation rules that need to be run. The specific format of these files will be covered later. Models can be aggregated in a particular Processor such that these rules can be layered on top of one another. For instance, you might have one Model File that does basic schema validation for all messages that fall under a particular standard. Each transaction may have a separate Model File that is used for specific rules in an implementation guide. On top of that, vendor or system specific rules can be implemented. These Model Files may be added to the list using the Add button.

Navigate to any Model Files that you would like to implement.

The aggregation of these Model Files can be saved as a name Validation Model under the Validation Processor Configuration. When data passes through the Validation Processor, these Model Files will be executed by the Validation Engine. Each Validation rule that executes successfully will be noted. An unsuccessful validation can be used to generate either an HTML based validation report or to throw an exception, which will trigger an alternate system processing