Saving a mapping

Created mappings must be saved on your workspace even when the mappings are not yet completed. In the Mapping Editor or in the Java editor, an asterisk after the mapping name or function indicates that the editor content has not yet been saved. To save your created mappings, select File > Save or use the shortcut key Ctrl + S.

To generate or publish a mapping, you must save it to the Mapper Database because the Mapper Server reads mapping metadata from the Mapper Database. The mapping is automatically saved when you generate or publish the Mapper Database. You can also save the mapping to the Mapper Database without generating or publishing it.

The default way of saving a mapping to the Mapper Database is to save it to the server. Then, the mapping is sent to the Mapper Server and saved to the Mapper Database.

When you save a mapping, the progress and result is logged in the Mapping Console view.

Note: If you replace a mapping that already exists in the Mapper Database, only the mapping is saved and not the schema files. Follow the standards in changing and saving a schema file:

See Managing custom schemas.
See Editing schemas.

If you change the XML schemas for a mapping, we recommend that you give the mapping a new version number or rename the mapping. A new mapping is created in the Mapper Database.

When you save a standard mapping, it is automatically converted into a custom mapping. A custom mapping can have the same name as a standard mapping, but we recommend that you change the name for custom mappings, for example, by adding a suffix to the mapping name.