Paths in Various Execution Environments

www.altova.com Print this Topic Previous Page Up One Level Next page

Home >  Designing Mappings > Using Relative and Absolute Paths >

Paths in Various Execution Environments

If you generate code from mappings,  the generated files are no longer run by MapForce. Instead, the mappings are run by the target environment you have chosen (for example, RaptorXML Server). The implication is that, for the mapping to run successfully, any relative paths must be meaningful in the environment where the mapping runs.

 

Consequently, when the mapping uses relative paths to instance or schema files, consider the base path to be as follows for each target language:

 

Target language

Base path

XSLT/XSLT2

Path of the XSLT file.

XQuery*

Path of the XQuery file.

C++, C#, Java*

Working directory of the generated application.

BUILT-IN* (when previewing the mapping in MapForce)

Path of the mapping (.mfd) file.

BUILT-IN* (when running the mapping with MapForce Server)

The current working directory.

BUILT-IN* (when running the mapping with MapForce Server under FlowForce Server control)

The working directory of the job or the working directory of FlowForce Server.

* Languages available in MapForce Professional and Enterprise editions

If required, you can instruct MapForce to convert all paths from relative to absolute when generating code for a mapping. This option might be useful if you run the mapping code on the same operating system, or perhaps on another operating system where any absolute path references used by the mapping can still be resolved.

 

To convert all paths to absolute in the generated code, right-click the mapping, and select the Make paths absolute in generated code check box. See also Changing the Mapping Settings.

 

When you generate code and the check box is selected, MapForce resolves any relative paths based on the directory of the mapping file (.mfd), and makes them absolute in the generated code. This setting affects the path of the following files:

 

Input and output instance files for all file-based component kinds

 

When the check box is not selected, the file paths will be preserved as they are defined in the component settings.


© 2019 Altova GmbH