MIME type to file extension mapping

When a document is archived with the Content Services for ERP via ArchiveLink, the file extension (of the attachment file to be stored in ImageMaster) is derived from the MIME type which is returned by SAP during the archiving request. To determine the file extension, ImageMaster uses the following logic:

If the custom configuration “ERP_MimeTypeExtensionMappingConfiguration” is available, the file extension is derived from the “mappingType” entry with the matching “mimeType” value:

1
2
3
4
5
<ns:mimeTypeExtensionMappings xmlns:ns="http://www.tsystems.com/ima/9/contentserver/20210601/">
  <!--Zero or more repetitions:-->
  <ns:mappingType mimeType="application/pdf" extension="pdf"/>
  <ns:mappingType mimeType="application/msword" extension="doc"/>
</ns:mimeTypeExtensionMappings>

Figure 383: Example configuration – mapping MIME type to file extension

Such a custom configuration must be set up via a SOAP request with the administration web services of the Integration Service [WS AdminClient]. The AdminClient does not support setting this up.

If no custom configuration is available, the file extension will be taken from an internal default mapping.

If no matching MIME type can be found, neither via a custom configuration nor by the internal default mapping, the name of the file will be set to the content key (internal document property “contentKey”) without any file extension.