Hybrid Integration 10.2 | Integrating On-Premises Applications | Managing MIME messages | Building MIME and S/MIME Messages | Creating a MIME Message | Example—Creating a Multipart MIME Message
 
Example—Creating a Multipart MIME Message
The following flow service creates a multipart MIME message that contains three parts: a simple text message, an XML document, and an image file. The steps you use to create a multipart message are essentially the same as the ones you use to create a single-part MIME message—the only difference is that you execute addBodyPart multiple times.
Flow service that creates a multipart MIME message
Step
Description
1
This step creates an empty MIME object. It does not take any inputs. It puts an empty MIME object called mimeData in the pipeline.
2
This step generates the content of the message and adds it to the mimeData object. If you view the pipeline for the addBodyPart service in this step, you will see that the stream output variable generated by the stringToStream service is linked to the content input variable. Because content contains a simple text message, the contenttype and encoding parameters are set as follows:
Parameter
Value
contenttype
text/plain;charset=UTF8
encoding
quoted-printable
3
This step creates an XML document from a document (IData object) in the pipeline, converts that XML document to an InputStream, and then adds the InputStream to the mimeData object. Because content contains an XML document, the contenttype and encoding parameters are set as follows:
Parameter
Value
contenttype
text/xml
encoding
quoted-printable
4
This step gets an image file from disk and adds it to the mimeData object. Because the file is retrieved as an InputStream, it can be linked directly to the mimeData object. In this case, content is an image file (binary data), so the contenttype and encoding parameters are set as follows:
Parameter
Value
contenttype
image/gif;name="b2b.gif"
encoding
base64
5
This step generates the finished MIME message. It takes the mimeData object populated in steps 2–4 and produces an InputStream called envStream that contains the multipart MIME message. At this point, you could pass envStream to any process that expects a MIME message as input.
6
Because you cannot view an InputStream, this example includes a step that converts envStream to a String so you can examine the finished message with Designer. This technique is useful for testing and debugging.
If you examine the contents of string on the Service Result view, you will see a MIME message similar to the following:
Points to keep in mind when building multipart MIME messages:
*By default, the Content-Type header field is set to “multipart/mixed.” If you want to use a different subtype, set the subtype parameter when you invoke createMimeData.
*Body parts appear in the message in the order in which you add them to the MIME object—the first part you add appears first in the message.
*If you set message headers (for example, using addMimeHeader) before you add body parts, those header fields will also be inserted into each body part. To prevent this, drop the mimeHeader variable from the pipeline before you perform an addBodyPart step or execute the addMimeHeader step after adding the message’s body parts.
Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release