Version 7.0
When you prepare your Transformation Maps, LANSA Composer silently and invisibly invokes MapForce to generate the executable form of the map, and then LANSA Composer deploys it to the LANSA Composer server, ready for use.
When running on an IBM i server, maps are always prepared to execute as:
When running on a Windows server, you have the choice of preparing maps to execute as either:
Java executable file (.JAR)
Preparing maps to execute as a Java executable file is the standard LANSA Composer implementation. At run-time, a LANSA Integrator service executes the generated Java code.
In this mode of execution, neither Altova MapForce, nor any other Altova software need be installed on the server computer at run-time, and no additional software licences are required.
You may only use MapForce features in your map that are supported by MapForce for Java code generation. For more information, please refer to Supported Functionality of the Mapping Tool.
MapForce Server execution file (.MFX)
Preparing maps to execute through MapForce Server is an optional feature of LANSA Composer.
In this mode of execution, the prepared execution (.MFX) file is executed through MapForce Server, which must be installed and licenced on the same Windows server as LANSA Composer.
You may use MapForce features in your map that are supported by MapForce for the "built-in" engine. For more information, please refer to Supported Functionality of the Mapping Tool.
NOTE: This mode of map execution is only available for LANSA Composer on Windows servers.
NOTE: This mode of map execution requires an optional additional LANSA Composer licence (in addition to a correctly installed and licensed MapForce Server instance). Refer to About LANSA Composer Server Licenses.
Version 7.0