Saving a mapping

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

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

The normal way of saving a mapping to the Mapper Database is to save it to the server. Then, the mapping will be sent to the Mapper Server, which in turn saves the mapping to the Mapper Database. In advanced mode the mapping can be saved directly to a Mapper Database, as for earlier versions of the mapper. This way of saving a mapping is deprecated and should normally not be used. All mapping functionality may not be supported when saving mappings directly to a 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. If you must change and save a schema file, see the Schema topics in this guide.

See Schema requirements

See Managing custom schema

See Editing schemas

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