ProductsMapForceXML Mapping

Altova MapForce® 2012 provides powerful, visual XML mapping functionality for instantly transforming XML data from one XML format to any another XML format based on XML Schema or namespace aware DTDs, and can even generate an XML mapping component from an XML instance file.

Developing XML Mappings

MapForce provides an intuitive graphical interface for defining and executing XML mappings based on XML Schema or DTD content models. To develop an XML mapping, simply load two or more schemas into MapForce and drag connecting lines between the nodes of the source(s) and target(s), as shown below. Mixed content support even enables you to map text data that is interspersed with XML. To make your mapping easier, MapForce automatically connects matching child elements as you create your XML mapping by default (this setting can be changed at any time in the Connection menu).

 Click here to download a fully functional, free 30-day trial of Altova MapForce® 2012!

	View Flash demoClick to enlarge

If your do not have an associated schema for your XML instance, MapForce is able to generate a sample XML Schema behind-the-scenes to use as the content model for your XML mapping.

Advanced Data Processing for XML Mappings

XML mapping projects are often not simply one-to-one mappings of a source to a target component with the same structure. Most XML mappings involve the use of data processing functions to manipulate data between the content models. You may need to perform logical comparisons, mathematical computations, or string operations, and/or make other modifications to the data to complete your mapping. Data processing functions appear as boxes between the lines joining the source and target XML mapping components.

Data processing functions enable you perform advanced data transformations on-the-fly for a multitude of real-world transformation requirements. You can, for example, map multiple XML source elements to one target XML element to map European and US addresses to one generic “address” field, or easily convert incongruous date/time formats.

MapForce also supports advanced XML transformations involving multiple input and output schemas, multiple source and/or target files, or advanced multi-pass data transformations (from schema, to schema, to schema, etc.), for which you simply insert additional XML Schemas or DTDs into MapForce and draw additional XML mappings.

Learn more in the Data Processing Functions section.

XSLT 1.0/2.0 Function Libraries

To extend the function libraries included within MapForce, you can add any existing XSLT 1.0/2.0 file as a library, and all named templates in that file will automatically become available as data transformation functions that you can use in your XML mapping project in an intuitive visual manner. This allows you to leverage work you've already completed, as well as take advantage of existing XSLT libraries, such as the XSLT Standard Library. The XSLT Standard Library is a standard feature in MapForce that becomes available when you select XSLT 1.0 or 2.0 as your output format. You can also download the XSLT Standard Library for free from the MapForce Libraries page.

In addition to full support for XSLT 1.0 for executing XML mapping transformations, MapForce includes a complete implementation of XSLT 2.0 for use in your data processing functions. XSLT 2.0 provides a significant number of improvements and enhancements to their earlier versions, including a vast array of powerful new functions and operators that you can use in MapForce to process data in your XML mappings. These important new capabilities are explained in detail on the XSLT 2.0 page in the Solutions Center.

MapForce also allows you to create and save new functions quickly and easily. The visual function builder allows you visually group multiple functions in an XML mapping design into one user-defined function, which you can then save and add to the function library to reuse as necessary.

Viewing XML Mapping Output

As you design an XML mapping project, the built-in MapForce Engine allows you to view and save the autogenerated XSLT 1.0/2.0 or XQuery code with one click. You can also click the Output tab to view the actual output generated by your XML mapping.

Learn more in the Output View section.

XSLT & XQuery

Once you have finished defining your XML mapping and data processing rules, you can load an XML instance document as a source file, and the MapForce Built-In Execution Engine will instantly convert the data into the new format. MapForce also autogenerates XSLT 1.0 or 2.0 stylesheets for use in transforming data in multiple XML documents based on the source schema to conform to the target XML Schema. (Additionally, MapForce Enterprise and Professional Editions generate program code for any XML mapping, as described below.)

The ability to generate XQuery code allows you work with XQuery natively, with MapForce acting as a visual XQuery builder. The XQuery code that MapForce produces based on your XML mapping can be executed in an XML-capable database, or you can view the results of an XQuery by simply clicking the Output tab.

XML Digital Signatures

XML Digital Signatures are a W3C specification to digitally sign an XML document with an encrypted code that can be used to verify that the XML document has not been altered. XML Digital Signatures can be especially useful for XBRL, patent, tax, and other official filing documents. (More information is available at the XMLSpy XML Digital Signatures page.)

MapForce supports creating XML Digital Signatures for XML and XBRL output files using the MapForce Built-In execution engine. A signature is created for the generated result file when the Output button is pressed and the result file is saved.

XML Digital Signature settings are specified in the XML Signature Settings dialog when the Create digital signature option is chosen in the output Component Settings. XML Digital Signatures may be embedded as the last element of the output document or stored in a separate signature file.

If the Enveloped option for Signature Placement is selected, then the signature is the last child element below the root element of the XML file. If the Detached option is selected, then the signature file is generated as a separate document. Either, way, the XML Digital Signature can be viewed in the Output window. In the screenshot below, a detached XML Digital Signature is displayed in preview window 2.

Automating XML Mappings

In addition to XSLT 1.0 and 2.0 stylesheets and XQuery code, MapForce generates Java, C++, and C# program code for marshalling data from the source to the target content model as defined in your XML mapping. It also supports data mapping automation through API, ActiveX control, or the command line.

Learn more in the Automate Data Integration section.

Advanced Functionality

In addition to XML mapping, MapForce supports mapping any combination of XML, database, flat file, EDI, Excel 2007+, XBRL, and Web services data to build data integration or Web services applications.

Discover the power of MapForce for XML mapping in data integration and Web services applications. Download a free 30-day trial of MapForce.