Mapping the input of the activity

In this task, you map the XML variables containing the MIME header and the parts (contains the attachments) to the mimeheader and parts input parameters of the Write MIME activity, respectively. Variable(s) must be mapped to the parts input parameter—this input parameter is required. The mimeheader input parameter is optional. If you do not map to or define default values for the elements of the mimeheader input parameter, default values are provided in the following table.

About this task

If the mimeheader input parameter is not listed in the To Activity pane of the Map Inputs pane, select Map > Show Optional Parameters from the toolbar menu or right-click in the To Activity pane and select the Show Optional Parameters option. If the Map > Show Optional Parameters option is not selectable in the toolbar menu, click on a element in the Map Inputs pane to make this option active.

The following table defines the elements in the mimeheader input parameter:
Table 1.
Child Element of the mimeheader Input Parameter Default Value
mimeVersion The standard MIME Version of 1.0 is assigned. The resulting MIME header is equal to the following setting: MIME-Version: 1.0.
contentType The value of the Content-Type setting in the resulting MIME header is equal to the following setting: Content-Type: multipart/mixed.
contentType/attribute/name contentType/attribute/value The attribute element contains a set of attributes as name/value pairs. The boundary between attachments can be specified using a boundary attribute element. If a boundary attribute is not specified a default value is generated.
contentTransferEncoding The value of the Content-Transfer-Encoding in the resulting MIME header is equal to the following setting: Content-Transfer-Encoding: 7-bit. NOTE: The Content-Transfer-Encoding you specify in this element for the main MIME header cannot be more restrictive than Content-Transfer-Encoding of the entity MIME headers. For example if you specify that the Content-Transfer-Encoding for the main MIME header is 7-bit but the Content-Transfer-Encoding specified in the entity MIME headers is 8-bit, the Content-Transfer-Encoding of the main MIME header is changed to 8-bit.
If you do not specify values for some of the child elements of the parts input parameter, defaults are described in the following table.
Table 2.
Child Element of the parts Input Parameter Default Value
mimeVersion The standard MIME Version of 1.0 is assigned. The resulting MIME header contains the following setting: MIME-Version: 1.0.
contentType The value of the Content-Type in the resulting MIME header contains the following setting: Content-Type: text/plain; charset=US-ASCII.
contentTransferEncoding The value of the Content-Transfer-Encoding in the resulting MIME header depends on the Content-Type setting. If the Content-Type is equal to multipart, the resulting MIME header contains the following setting: Content-Transfer-Encoding: 7-bit. If the Content-Type is equal to text and charset is equal to not-us-ascii (where not-us-ascii is any type except US-ASCII) the resulting MIME header contains the following setting: Content-Transfer-Encoding: quoted-printable. If the Content-Type is equal to non-text, the resulting MIME header contains the following setting: Content-Transfer-Encoding: base64. NOTE: If the Content-Disposition is equal to attachment, the entity part is not treated as text.
The parts input parameter can contain one or more parts. Each part contains a MIME header that describes various attributes of the associated part body. How the individual MIME part is serialized depends on the values assigned to the following parameters in the mine header:
  • Content-Type header
  • Charset attribute within the Content-Type header
  • Content-Transfer-Encoding

How the part body is serialized depends on the settings of Content-Transfer-Encoding and Content-Type:

Content-Type is equal to “text:”
  • If the Content-Type is “text” and the Content-Transfer-Encoding is “7-bit”/”8-bit” or “binary,” the part body is converted from UTF8 charset to the charset specified and copied into the body output parameter.
  • If the Content-Type is “text” and the Content-Transfer-Encoding is “quoted-printable,” the part body is converted from UTF8 charset to the charset specified, quoted-printable encoded and copied into the body output parameter.
  • If the Content-Type is “text” and the Content-Transfer-Encoding is “base64," the part body is converted from UTF8 charset to the charset specified, base64 encoded, and copied into the body output parameter.

If not explicitly specified in the part MIME header, charset defaults to "UTF8." The only exception to this default behavior is when the Content-Disposition is equal to “attachment” and the Content-Type is equal to “text.” In this case, the part is not treated as text since the charset of the data cannot be known. In addition for this case, the Content-Transfer-Encoding is set to "binary."

Content-Type is not equal to “text:”

  • If the Content-Type is not equal to “text” and the Content-Transfer-Encoding is “7bit”/”8bit” or “binary,” the part body is copied to the body output parameter as is.
  • If the Content-Type is not equal to “text” and the Content-Transfer-Encoding is “quoted-printable,” the part body is base64 decoded, quoted-printable encoded and copied into the body output parameter.
  • If the Content-Type is not equal to “text” and the Content-Transfer-Encoding is “base64,” the part body is copied as is (base64 data) into the body output parameter.

See Creating a Standalone Map for general instructions on mapping.




Feedback | Notices


Timestamp icon Last updated: Wednesday, February 17, 2016


http://pic.dhe.ibm.com/infocenter/wci/v7r0m0/topic/com.ibm.wci.doc/Map_Activity_Input_Write_MIME.html