Altova MapForce 2023 Enterprise Edition

The general syntax of a MapForce command at the command line is:

Legend

The following notation is used to indicate command line syntax:

<filename>

The mapping design (.mfd) or mapping project (.mfp) file from which code is to be generated. To generate code for the whole project, set the target /GENERATE (see description below) and enter the project path as <filename>, for example, MapForceExamples.mfp.

/{target}

Specifies the target language or environment for which code is to be generated. The following code generation targets are supported.

<outputdir>

Optional parameter which specifies the output directory. If an output path is not supplied, the current working directory will be used. Note that any relative file paths are relative to the current working directory.

When target is /GENERATE and the <outputdir> parameter is not set, the code generation language, as well as the output path of each mapping, are supplied by the settings defined for each folder inside the project, see Managing Project Folders.

When target is /GENERATE and the <outputdir> parameter is set, the <outputdir> value supplied at the command line takes precedence over the output directory defined at the root project level. It does not take precedence, however, over the code generation settings defined at each folder inside the project.

/options

The /options are not mutually exclusive. One or more of the following options can be set.

Remarks

•Relative paths are relative to the working directory, which is the current directory of the application calling MapForce. This applies to the path of the .mfd filename, .mfp filename, output directory, log filename, and global resource filename.

•Do not use the end backslash and closing quote at the command line (for example, "C:\My directory\"). These two characters are interpreted by the command line parser as a literal double quotation mark. Use the double backslash \\ if spaces occur in the command line and you need the quotes ("c:\My Directory\\"), or try to avoid using spaces and therefore quotes at all.

Examples

1) To start MapForce and open the mapping <filename>.mfd, use:

2) To generate XSLT 2.0 code and also create a log file with the name <logfilename>, use:

3) To generate XSLT 2.0 code taking into account the global resource configuration <grconfigname> from the global resource file <grfilename>, use:

4) To generate a C# application for Visual Studio 2015 and output a log file, use:

5) To generate a C++ application using the code generation settings defined in Tools | Options, and output a log file, use:

6) To generate a C++ application for Visual Studio 2015, MSXML, with static libraries, MFC support, and no log file, use:

7) To generate a C++ application for Visual Studio 2015, Xerces, with dynamic libraries, no MFC support, and a log file, use:

8) To generate a Java application and also output a log file, use:

9) To generate code for all mappings in the project, using the language and output directory defined in the folder settings (of each folder inside the project), use:

10) To generate Java code for all mappings in the project file, use:

Note that the code generation language defined in the folder settings are ignored, and Java is used for all mappings.

11) To supply input and output files at the command line for a previously compiled Java mapping, use:

The /InputFileName and /OutputFileName parameters are the names of special input components in the MapForce mapping that allow you to use parameters in command line execution (see Supplying Parameters to the Mapping).

12) To compile a mapping to a MapForce Server execution file, for MapForce Server version 2023, and suppress XML signatures: