Integration Platform Technologies: Siebel Enterprise Application Integration > Siebel EAI and File Attachments >

About the EAI MIME Doc Converter


The MIME Doc Converter converts a MIME Hierarchy into a MIME Message and a MIME Message into a MIME Hierarchy. A MIME Hierarchy consists of two different types of property sets.

Property
Description

Document

Mapping to MIME basic-part

EAI MIME Doc Converter Properties

Table 45 illustrates some examples of how a MIME Message maps to a MIME Hierarchy.

Table 45. Examples of MIME Message and MIME Hierarchy
MIME Message
MIME Hierarchy

MIME-Version: 1.0

Content-Type: application/xml

Content-Transfer-Encoding: 7bit

This is a test.

MIME-Version: 1.0

Content-Type: multipart/related; type="application/xml"; boundary=--abc

----abc

Content-Type: application/xml

Content-Transfer-Encoding: 7bit

This is test2.

----abc--

 

The business service needs the following properties on the child property set as shown in Table 46. These properties reflect the most accurate information on the data contained in the child property set.

Table 46. Properties for EAI MIME Doc Converter
Property
Possible Values
Type
Description

ContentId

Any value

Document

No Default. The ContentId is the value used to identify the file attachment when the receiver parses the MIME message. When importing attachments, use a unique value for this property and not repeat it for the rest of the file attachments. This is required in the actual document. This property is automatically populated when you are exporting an attachment from a Siebel application.

Extension

txt, java, c, C, cc, CC, h, hxx, bat, rc, ini, cmd, awk, html, sh, ksh, pl, DIC, EXC, LOG, SCP, WT, mk, htm, xml, pdf, AIF, AIFC, AIFF, AU, SND, WAV. gif, jpg, jpeg, tif, XBM, avi, mpeg, ps, EPS, tar, zip, js, doc, nsc, ARC, ARJ, B64, BHX, GZ, HQX

Document

No Default. If ContentType and ContentSubType are not defined, the Extension is used to retrieve the appropriate values from this property. If all three values are specified, the ContentType and ContentSubType values override the values retrieved from the Extension. If either the Extension or both ContentType and ContentSubType are not specified, the ContentType will be set to application and ContentSubType will have the value of octet-stream.

ContentType

application, audio, image, text, video

Document

Default is application. The ContentType value has to be specified if you want to set the content type of the document instead of using the extension to get a value from the MIME utility function. If the value is not provided, the default value is used. The ContentType of multipart is used to represent file attachments in a MIME message. Other forms of values to describe a multipart is not supported.

ContentSubType

plain, richtext, html, xml (used with ContentType of Text)

octet-stream, pdf, postscript, x-tar, zip, x-javascript, msword, x-conference, x-gzip (used with ContentType of application)

aiff, basic, wav (used with ContentType of audio)

gif, jpeg, tiff, x-xbitmap (used with ContentType of image)

avi, mpeg (used with ContentType of video)

Document

Default is octet-stream. The ContentSubType value has to be specified if you want to set the content subtype of the document instead of using the extension to get a value from the MIME utility function. If the value is not provided the default value is used.

NOTE:  On the inbound direction, the business service is independent of the transport. It assumes that the input property set contains the MIME message, and writes a property set representation of the MIME message. A property set is used to represent each part of the MIME message. When decoding the MIME message, the business service automatically sets the properties based on the values in the MIME message.

Integration Platform Technologies: Siebel Enterprise Application Integration Copyright © 2008, Oracle and/or its affiliates. All rights reserved. Legal Notices.