There are certain functions of Altova MapForce that are explicitly NOT supported for use with LANSA Composer. These are:
- MapForce projects
- Web service projects (publishing web services)
- Maps that use multiple target components or "chained transformations" (such cases can generally be accomplished by making use of intermediate "variable" components or by using more than one map each with a single target component)
Transformation Map definitions that make use of these functions may not integrate correctly with LANSA Composer.
For maps prepared for execution as Java executable files (.JAR), LANSA Composer does not support any functionality that is not supported by Altova for Java code generation. Some notable items that fall into this category and that may not be used in maps prepared for execution as Java executable files (.JAR) are:
- JSON components (input or output)
- REST web service function calls
- Note the foregoing is not an exhaustive list – you should refer to Altova MapForce documentation for the definitive statement on whether certain features are supported for Java code generation.
For maps prepared for execution as MapForce Server execution files (.MFX), LANSA Composer does not support any functionality that is not supported by Altova for the MapForce "built-in" engine and for execution via Altova MapForce Server.
In addition, the following user-interface options for Altova MapForce are not used (or supported) with LANSA Composer:
- MapForce plug-in for MS Visual Studio .NET
- MapForce plug-in for Eclipse