You are on page 1of 2

5/25/2021

Define a Decoder 

You use this task to decode the message received over the network to retrieve original data.

Procedure
. Open the integration ow in the editor.

. From the palette, choose Transformation Decoder .

. Select one of the following decoding schemes:

Base64 Decode: Decodes base64-encoded message content.

GZIP Decompress: Decompresses the message content using GNU zip (GZIP).

ZIP Decompress: Decompresses the message content using zip.

MIME Multipart Decode: Transforms a MIME multipart message into a message with attachments.

If the multipart headers are part of the message body, select Multipart Headers Inline.

 Note
If this option is not selected and the content type camel-header is not set to a multipart type, no decoding takes place.

If this option is selected and the body of the message is not a MIME multipart (with MIME headers in the body), the message is handled as a MIME comment and the body
is empty afterwards.

 Note
Note that SAP Cloud Integration does not support the processing of MIME multipart messages that contain multiple attachments with the same le name.

More information:

MIME Multipart Messages

MIME Multipart Encoder: Handling Message Headers (Examples)

Example Scenario with MIME Multipart Encoder/Decoder

. Save the changes.

1/2
5/25/2021

Example
Let us suppose that an input message to the decoder is a message encoded in Base64 that looks like this:

PG1lc3NhZ2U+DQoJSW5wdXQgZm9yIGVuY29kZXINCjwvbWVzc2FnZT4NCg==

The output message of the decoder would be as follows:

<message>
Input for encoder
</message>

Related Information
https://blogs.sap.com/2020/05/05/cloud-integration-zip-and-compress-capabilities-encoder-decoder-splitter-aggregate/

2/2

You might also like