Deleting mappings

Use these procedures to delete a mapping from your workspace or remove a mapping from a database.

The normal way of removing a mapping from a Mapper Database is to remove it from the server. A command will be sent to the Mapping Server, which in turn removes the mapping from the Mapper Database. In advanced mode, the mapping can be removed from a Mapper Database directly from the mapper, as for earlier versions of the mapper. This way of removing a mapping is deprecated and should normally not be used.

Note: 

  • Input and output XML schemas are saved in the database. If two or more mappings use the same XML schema, the XML schema is only stored once in the database.

    To remove an XML schema from the database, you must delete all mappings using the XML schema. When the last mapping using an XML schema is deleted from the database, the XML schema is also deleted from the database.

  • Custom JAR files are saved in the database. If two or more mappings use the same Custom JAR file, the Custom JAR file is only stored once in the database.

    To remove a Custom JAR file from the database, you must delete all mappings using the Custom JAR file. When the last mapping using a Custom JAR file is deleted from the database, the Custom JAR file is also deleted from the database.

Note: 

  • Delete from workspace removes the complete mapping folder and not only the mapping file.

    This action can be reversed using the Eclipse standard feature Restore from Local History on the Navigator tab.

  • Remove from server has no reverse function.

    Before you remove a mapping, you must verify the name and version number of the mapping to remove. While you still have the mapping in your workspace, note that the mapping in the Mapper Database could differ from the mapping in your workspace.

    Before you can remove a mapping from the server, you must unpublish the mapping.