jValidator is a data quality firewall, i.e. middleware for the real time validation, management, and monitoring of data streams. If you need to implement or improve the validation process of your schemas, to populate a database through data streams of various formats and originating from many sources, to validate complex rules, and to monitoring the quality of your data, jValidator is the solution.
|Tags||information flows management data stream management XML validation EXI validation Delimited Flat File validation Fixed Position Flat File validation data quality firewall data stream monitoring JSON validation EXCEL validation EDI Triggers ETL|
|Operating Systems||all Java capable systems|
|Implementation||Java 1.6+ extjs hibernate Spring Framework maven2|
|Translations||English Italian Russian German|
Release Notes: Stability and performance were priorities of this release, and many important features have also been implemented (including forecasting, triggers, and extracheck), but the most important news is that it's now possible to generate a data stream (like an ETL) from your db and is possible to validate the standard EDI streams.
Release Notes: Stability was improved with new management of the connection pool. It is now possible to import XSD files and personalize message errors, and dynamically validate the data from other databases with macros and personal validation rules. A very important interface with Mashape, a new annual chart, and an improved graphical interface were added. There were also many bugfixes and other minor new features.
Release Notes: Valid data streams are now stored dynamically in the database. Access is profiled. It is now possible to store macros, and the user can be alerted by email. New kinds of validation were provided (including key constraints), JSON and Excel input streams were implemented, Russian and German language support was added, and schema diagram export was added.
Release Notes: Porting from extjs 3 to 4. New kinds of validations. Charts, scheduling, export XSD, upload documentation, schema duplication, multiple streams in a file, active/deactive schemas and applications, and general refactoring.