LANSA Composer supports the functionality offered by the mapping tool for mapping between XML, EDI, Excel (OOXML), text (including using FlexText), web service functions, and database formats including the use of constants, filters, If-Else conditions, supplied functions, and input functions, provided that:
- For maps prepared for execution as Java executable files (.JAR), the functionality is supported by Altova for Java code generation.
- For maps prepared for execution as MapForce Server execution files (.MFX), the functionality is supported by Altova for the MapForce "built-in" engine and for execution via Altova MapForce Server.
- Databases and database drivers used, and the operating systems on which they are running are amongst those that are supported by LANSA for use with LANSA software.
MapForce version 2015, release 3 (2015R3) introduced support for "simple output" components. These are supported in LANSA Composer, though your maps may, nevertheless, have only one output or target component, including the "simple output" component.
For maps prepared for execution as Java executable files (.JAR), certain properties of a Transformation Map definition are set explicitly by LANSA Composer before generating the Java code for a map. This means that any changes that you make to these properties in your map definition will not affect the generated Java implementation of the map. These include:
- The default output directory for generated code
- The application name
- The base package name for Java generation.
- The output language (LANSA Composer always generates Java code)