DML Mapping Projects

Project components

Project file

Project directory structure

DML version

Effects of the DML version on importing and exporting

A DML Mapping Project is a standard Eclipse project with a default directory structure. A Mapping Project combines all files required for creating, designing, and modifying one or more Mappings. The directory structure of the Mapping Project and the project file itself are automatically generated when creating a new Mapping Project. The Global Runtime Objects is also created automatically by default.

One Mapping Project can contain multiple Mappings. All Mappings that are located in the same Mapping Project can use the same resources, such as Tables and Custom Functions.

Resources that should be reused on the runtime server over multiple Mappings should be located in the Global Runtime Objects.

Note For conceptual information about Mapping Services, such as the project structure, the life-cycle of Mappings, the product architecture, the Mapping Services Workbench, and Mapping Services specific terminology, refer to the Axway Mapping Services Overview Guide.

Project components

Depending on the mapping language , the Mapping Project can contain:

  • Business Documents
  • Maps
  • Mapping Flows
  • Variables
  • Tables
  • Functions
  • Test data, containing test cases for simulation
  • Configurations for the simulation
  • Documentation

Project file

The main entry point for each Mapping Project is the project file project.ms.

Project directory structure

The project directory structure and the project file itself are created and then all of the necessary steps needed to execute the Mapping are defined and grouped in the correct order. Apart from Mappings and processor files, the project can contain – depending on the Mapping type –XML files, XSL Translets, stylesheets, documentation files, runtime configuration files, SQL scripts for the creation of database tables, and much more (see Project components).

Directory Contents
Business Documents Source and target message descriptions of the Mappings for details).
Documentation Mapping documentations
Extended Objects Additional files that will be used for the Mappings (Custom Functions, Tables, Variables)
Mapping Flows Mapping Flows, that describe how a Mapping is orchestrated
Maps Maps, that describes the transformation from the source into the target document
Testdata Test messages (e.g. example EDI or XML messages) and the simulation suite
project.ms Mapping description file as the main entry point for the Mapping Project

DML version

A DML Mapping Project can be designated as either DML 1.5 or 2.0. All new projects are defined as 2.0.(or higher), providing some new features (enabling justification and padding) that change mapping results. Older projects are generally defined as 1.5., keeping the previous project behaviors (justification and padding are disabled), unless you change the version to 2.0 to use the new features.

These are the main differences between DML 2.0 and DML 1.5:

  • Changes in padding behavior:
  • In DML 2.0, setting the Justification attribute will have the expected effect, in DML 1.5, some settings were ignored.
  • Variable Length Output Fields with a fixed Decimal Point Position:
  • If the field has variable length and the Justification attribute is set to right, and if the input has less fractional digits than the expected output definition, the value will be padded with zero until the value matches the definition of the output field.
  • Interactions between the attributes Pad reals with a leading and trailing zero in the Business Document General options and the environment variable DECIMAL_POINT_NOT_MANDATORY:
  • In DML 2.0, the attribute Pad reals with a leading and trailing zero work independently of the values of the environment variable DECIMAL_POINT_NOT_MANDATORY. In DML 1.5, the padding of trailing zero was not done if the value of the environment variable was set to 1.
  • As of DML 2.0, the minimum length for Integer class is checked for variable fields.

These are the main differences between DML 2.1 and DML 2.0:

  • In DML 2.1, the precision and scale are taken into account for XML. Prior to DML 2.1, the definition for XML leaves with real data type was not interpreted in a consistent way. That means, if some values did not match the definition, no error was displayed. As of DML 2.1, an error will be displayed if the values do not match the definition.
  • In DML 2.1, extra namespaces removed in the generation of XSD business documents.
  • In DML 2.1, short real numbers will issue a warning when the option facet check is enabled along with the option accept document with error.

Effects of the DML version on importing and exporting

DML versions also affect project and deployment package import and export:

  • Importing an older project sets the version to 1.5.
  • Exporting a deployment package maintains the existing project version at the time of export, either 1.5 or 2.0.
  • Importing a previously deployed deployment package sets the project version to 1.5, even if some of the objects in the project are set to 2.0. A warning does advise you about the mismatch. You can override the version to 2.0 to change the project and resulting behaviors.

Change the DML version

To change the DML version of the DML Mapping Project :

  1. Double-click the project file in the Project Explorer.
  2. In the Project Properties list , click Mapping Details.
  3. Select the version in the Version drop-down list. You can choose between 1.5 and 2.0.
  4. Save the changes.

The mapping language and version is shown as a label in the Project Explorer on the project.ms file, for example[DML-2.0]. To customize the decoration, use the Preferences dialog box (see also Set Mapping language and version decoration).

Related topics

Mapping Services Overview

Create DML Mapping Projects

Import a Map Designer project

Set Mapping language and version decoration

Related Links