In MapForce, a transformation language is used to generate transformation code that carries out mappings. You can select/modify a transformation language at any time. MapForce allows viewing the transformation code in the selected language. For more information, see Generating and Previewing XSLT Code. You can also generate this code via the menu command File | Generate Code in and use this code for transforming any data document that is valid according to the source component’s schema. Depending on the MapForce edition, you can choose the following languages for your data transformation:
MapForce Basic Edition
MapForce Professional and Enterprise editions
To select a transformation language, do one of the following:
•In 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 (shown below).
When you change the transformation language of the mapping, certain MapForce features may not be supported for that language. For more information, see Support Notes.
As you design or preview mappings, MapForce validates the integrity of your schemas or transformations. If any validation errors occur, MapForce displays them in the Messages window. This is helpful because you can immediately review and correct these errors.
Transformation languages in MapForce Professional and Enterprise editions
When you choose Java, C# or C++ as a transformation language, MapForce generates the required projects and solutions so that you can open them directly in Visual Studio or Eclipse. For advanced data integration scenarios, you can also extend the generated program with your own code, using Altova libraries and the MapForce API.
When you select BUILT-IN as a transformation language for your mapping, MapForce uses its native transformation engine to execute the data mapping. MapForce also uses this option implicitly whenever you preview the output of a mapping where the selected transformation language is Java, C#, or C++.
The BUILT-IN engine executes mappings without the need for any external processors, which may be a good choice if memory usage is an issue. If you do not need to generate program code in a specific language, use BUILT-IN as a default option, because it supports most MapForce features compared to other languages (see Support Notes). Furthermore, if you select BUILT-IN as a transformation language, you will be able to automate the mapping with MapForce Server. For more information, see Automating MapForce Tasks with Altova Products.