Mail Mime Service

How the Mail Mime Service Works

The Mail Mime service is used for building or parsing a MIME message.

Implementing the Mail Mime Service

Configuring the Mail Mime Service

Sterling B2B Integrator Configuration

The following table describes the fields used to configure the Mail Mime service in Sterling B2B Integrator:

GPM Configuration

The following table describes the fields that are used to configure the Mail Mime service in the GPM:

Parameters Passed from Business Process to Service

The following parameters can be passed to the service when started from a business process:

How the Mail Mime Service Handles Attachment Data

For the build operation, the Mail Mime service can retrieve attachment data from the file system or the business process context. If the attachment data is in the file system, the service automatically looks up the content type and subtype of the data from the file system repository. If the attachment data is in the business process context, the filename and the content type/subtype information is read from the business process document. It is the responsibility of the calling business process to pass this information to the service. You can use the Get Document Info service to set or get the information.

The parse operation reads all information from the incoming e-mail and its attachments. Each attachment has data available for its name, MIME type and subtype, and character encoding. This information is made available when the attachments are written to the document area of process data.

Process Data Examples

When the Mail Mime service parses a MIME message, the total count of messages (including attachments) is output to the process data, in the format shown in the following example:

<ProcessData> 
	  	<Mail_Mime> 
	     		<Total_Message_Content> 
         {---value----} 
	     		</Total_Message_Content> 
	  	</Mail_Mime> 
</ProcessData> 

The following example of process data is created when the Mail Mime service parses a MIME message with four message parts (main body and three attachments):

<ProcessData> 
 <PrimaryDocument SCIObjectID="prodsys3:123c99:f88fee0b27:-796e"/> 
 <Mail_Mime_DOC_2 SCIObjectID=" prodsys3:123c99:f88fee0b27:-796c"/> 
 <Mail_Mime_DOC_3 SCIObjectID=" prodsys3:123c99:f88fee0b27:-796a"/> 
 <Mail_Mime_DOC_4 SCIObjectID=" prodsys3:123c99:f88fee0b27:-7968"/> 
 <Mail_Mime> 
    <Total_Message_Content>4</Total_Message_Content> 
 </Mail_Mime> 
</ProcessData> 

The first message content is put into the primary document and the attachments are placed in the document area, which can be referenced by a unique index key. The format of the unique index key is Mail_Mime_DOC_n, where n is the message count. The sample above shows that a total of four message parts is extracted from the MIME message. The first part is put in the primary document. The attachments are put into the document area, and they can each be referenced by a unique index key such as Mail_Mime_DOC_2, Mail_Mime_DOC_3 and Mail_Mime_DOC_4 respectively.

Business Process Examples

This section contains sample business processes that illustrate by using the Mail Mime service to build or parse messages.

Building a Mime Message

The following business process illustrates building a MIME message from the primary document and sending the MIME message to an SMTP server, 00.000.00.00.

<process name="Test_mm_build"> 
<sequence name="optional"> 
<operation name="Build a mime message"> 
<participant name="MailMimeService"/> 
<output message="Xout">
<assign to="." from="*"></assign> 
<assign to="mail-mime-operation">build</assign> 
<assign to="mail-mime-body">true</assign> 
<assign to="mail-mime-sender">ediintout@joeuser.mycompany.com</assign> 
<assign to="mail-mime-recipient">steveuser@mycompany.com</assign> 
<assign to="mail-mime-subject">This is my subject</assign> 
</output> 
<input message="Xin"> 
<assign to="." from="*"></assign> 
</input> 
</operation> 
<operation name="One"> 
<participant name="SMTP_SEND_ADAPTER"/> 
<output message="Xout"> 
<assign to="." from="*"></assign> 
<assign to="xport-smtp-mailhost">00.000.00.00</assign> 
<assign to="xport-smtp-mailport">25</assign> 
<assign to="b2b-raw-message">true</assign> 
</output> 
<input message="Xin"> 
<assign to="." from="*"></assign> 
</input> 
</operation> 
</sequence> 
</process>

The following business process illustrates building a MIME message with 12 attachments. Each attachment is picked up from the file system:

<process name="Test_mm_build"> 
  <sequence name="optional"> 
   <operation name="One"> 
      <participant name="MailMimeService"/> 
      <output message="Xout"> 
        <assign to="." from="*"></assign> 
        <assign to="mail-mime-operation">build</assign> 
        <assign to="mail-mime-body">false</assign> 
        <assign to="mail-mime-attachment-count">12</assign> 
        <assign to="mail-mime-attachment1">/home/testsys/test_data/smc1.props
        </assign> 
        <assign to="mail-mime-attachment2">/home/testsys/test_data/smc2.props
        </assign> 
        <assign to="mail-mime-attachment3">/home/testsys/test_data/smc3.props
        </assign> 
        <assign to="mail-mime-attachment4">/home/testsys/test_data/smc4.props
        </assign> 
        <assign to="mail-mime-attachment5">/home/testsys/test_data/smc5.props
        </assign> 
        <assign to="mail-mime-attachment6">/home/testsys/test_data/smc6.props
        </assign> 
        <assign to="mail-mime-attachment7">/home/testsys/test_data/smc7.props
        </assign> 
        <assign to="mail-mime-attachment8">/home/testsys/test_data/smc8.props
        </assign> 
        <assign to="mail-mime-attachment9">/home/testsys/test_data/smc9.props
        </assign> 
        <assign to="mail-mime-attachment10">/home/testsys/test_data/smc10.props
        </assign> 
        <assign to="mail-mime-attachment11">/home/testsys/test_data/smc11.props
        </assign> 
        <assign to="mail-mime-attachment12">/home/testsys/test_data/smc12.props
        </assign> 
        <assign to="mail-mime-sender">ediintout@companyname.com</assign> 
        <assign to="mail-mime-recipient">ediintin@companyname.com</assign> 
        <assign to="mail-mime-subject">This is a mime message with 12 attachments
        </assign> 
      </output> 
     <input message="Xin"> 
        <assign to="." from="*"></assign> 
      </input> 
   </operation> 
  </sequence> 
</process> 

Parsing a Mime Message

The following business process example illustrates parsing a MIME message. The Mail Mime service picks up the MIME message from the primary document, extracts all the message contents, and outputs them to the primary document and the document area:

<process name="Test_mm_parse"> 
 <sequence name="optional"> 
    <operation name="One"> 
      <participant name="MailMimeService"/> 
     <output message="Xout"> 
        <assign to="." from="*"></assign> 
        <assign to="mail-mime-operation">parse</assign> 
     </output> 
      <input message="Xin"> 
       <assign to="." from="*"></assign> 
     </input> 
    </operation> 
 </sequence> 
</process>