Selecting a Transformation Language Print this Topic Previous Page Up One Level Next page

Home >  Common Tasks > Working with Mappings >

Selecting a Transformation Language


To meet your data mapping needs, MapForce provides the ability to choose between various transformation languages.


By default, MapForce provides a robust, built-in engine capable of performing the same transformations supported in other languages. When you deploy MapForce mappings to MapForce Server, the built-in engine executes them without the need for any external processors. Furthermore, if you require minimal or no manual intervention in your data transformation process, you can use FlowForce Server to automate mapping processes by means of scheduled jobs.


Consider choosing the transformation language after testing several approaches and determining what works best for your data. The available transformation languages are as follows:


BUILT-IN (This is the default native transformation engine used by MapForce.)
XSLT 1.0
XSLT 2.0


To select a transformation language, do one of the following:


On the Output menu, click the name of the language you wish to use for transformation.
Click the name of the language in the Language Selection toolbar.


Note:Some mapping inputs and outputs are not supported by certain languages. For example, if you use a database as mapping input or output, you cannot generate XSLT code. Therefore, if you attempt to generate the code or preview the output of a mapping that has sources or targets not supported by the selected language, MapForce displays a relevant notification message.


The BUILT-IN transformation language

When you select BUILT-IN ( ic-builtin ) as transformation language for your mapping, MapForce uses its internal transformation engine to execute the data mapping. MapForce also uses this option implicitly, whenever you want to preview the output of a mapping where the selected transformation language is Java, C#, or C++.


It is recommended to set the transformation language to BUILT-IN in the following cases:


As default option, when you do not necessarily need to use a specific language to transform data. The BUILT-IN transformation language supports most MapForce features. As stated subsequently in this documentation, certain MapForce features are not supported when the transformation language is Java, C#, or C++.
If you intend to deploy and execute the mapping on a different Linux, Mac, or Windows machine with MapForce Server, see Automating Mappings and MapForce.
If you are processing large files and memory usage is a concern.

© 2019 Altova GmbH