Company > Mission
Company > Team
Products > Repository 2.0
Products > Mediator 2.0
Products > XMLizer 2.0
Products > XFE
Solutions > Consulting
Contact Us

XMLizer 2.0

XMLizer carries out the transformation from XML documents to existing relational databases and vice-versa.The XMLizer permits XQuery based extraction of data from a relational database, the transformation of XML to XML formats and the insertion (or loading) of the XML data into relational database tables.

The XML/DBC Java API for XML Mediators, Repositories and ELT Tools

Click here for a brochure describing the XMLizer. (PDF 32 KB)

Click here for answers to Frequently Asked Questions (FAQ) on the XMLizer. (PDF 30 KB)

Click here for a 30 day evaluation version of the XMLizer.

Click here for a white paper describing our products. (Word 957 KB) (ZIP 219 KB)

All data translation is simplified into a single document. Thus, the unique properties of this tool are:

  • Drastically reduced development time. The programmer simply defines the mappings and all generation of identifiers, parsing of documents and generation of complex SQL statements are done automatically.
  • Increased ease of maintainence. Translations between XML and SQL are no longer cast in the "stone" of programs. The translations are clearly laid out in a single location providing a clear description of data movement in both directions.
  • Increased performance. XMLizer is highly optimized to perform these translations. Instead of "one-off" optimizations used in an ad-hoc translation, all optimization techniques are gathered in one place and can be applied to all uses of the product.

Exchanging data between EAI, EDI or B to B platforms and an existing relational database is difficult due to the differences in the structure and type of the data involved. The XMLizer brings a solution to this problem by providing a tool to easily:

This functionality is provided by the component with a maximum of flexibility and openness to incremental improvements.


For each type of XML document to be produced, the developer forms the XQuery requests that permit the extraction of data to be linked to the XML document. The extractor module itself is in charge of the connection to the relational database, the execution of the XQuery requests, and the reconstruction of the XML documents in the specified format. The Extractor provides a wide range of flexibility for:

  • Defining generic requests containing parameters that are instantiated at run-time,
  • Defining a nested set of requests to construct deeply structured XML documents from a flat relational schema,
  • Choosing the format of the XML document to be generated.

The following diagram shows the architecture of the Extractor:


For each type of XML document to be inserted, the developer forms a set of storage rules to be applied to the elements of the document. These rules are specified with the aide of the a simple mapping language. The Mapper utilizes these rules to decide where data elements are stored. Restrictions on data storage (such as foreign keys) are automatically handled during data storage.

The essential functionality provided is:

  • Control of the structure of the documents accepted,
  • Management of data integrity constraints,
  • Conditional insertion and updates on the database,
  • Integration of function calls and SQL requests during insertion,
  • Automatic generation of identifiers and keys,
  • User defined generation of identifiers and keys, and
  • Execution of related stored procedures.

The following diagram shows the architecture of the Mapper:

Home : Company : Products : Solutions : News : References : Information : Contact Us Cash advance online : Links
Winity Hosting
Site Design by e-PowerApps.com