In the Properties window, in the Pipeline Component Properties section, do the following.
| Use this | To do this |
| Add Signing Cert To Message | If the Signature Type property is not NoSign, you can select whether to add the signing certificate to the signed message by setting the Add Signing Cert to the Message property.
Default value: True Possible values in BizTalk Administration Console: True/False |
| Check revocation list | Specifies whether to check the certificate revocation list while processing an SMIME message.
Default value: True Possible values in BizTalk Administration Console: True/False |
| Content transfer encoding | Indicates the encoding format.
Options: Base64, QuotedPrintable, SevenBit, EightBit, Binary, and UUEncode. Default value: Base64 Possible values in BizTalk Administration Console: base64, quoted-printable, 7bit, 8bit, binary, UUEncode |
| Enable encryption | Set to True if you want to encrypt the outgoing message. If this option is enabled, the user can select the encryption algorithm to use by setting the Encryption algorithm property. For message encryption, the MIME/SMIME Encoder pipeline component uses the public key certificate that is associated with a send port in BizTalk Explorer.
Default value: False Possible values in BizTalk Administration Console: True/False |
| Encryption algorithm | Define the encryption algorithm.
This property can only be set if Enable encryption is set to True. Options: DES3, DES, RC2. Default value: DES3 Possible values in BizTalk Administration Console: 0, 1, 2 |
| Send body part as attachment | Set to True if you want to send the body party of a BizTalk message as a MIME attachment.
Default value: False Possible values in BizTalk Administration Console: True/False Important: You should not set this property to True when sending messages between BizTalk Servers. Otherwise, the message decoding will require custom coding because the message is interpreted on the receive side as a two-part message. |
| Signature Type | If you want to sign the outgoing message, select a signing format with this property. This property has three values:
NoSign. The message will not be signed. ClearSign. The signature will be appended to the message. ClearSign cannot be used if Enable Encryption is set to True. BlobSign. The signature will be appended to the message and the message will be encoded. For message signing, the MIME/SMIME Encoder component uses the private key client certificate that is associated with BizTalk Group in the BizTalk Administration console. Default value: NoSign Possible values in BizTalk Administration Console: 0, 1, 2 |
In BizTalk 2006 and R2, this component has a strange behavior in the BizTalk Server Administration Console. In Visual Studio when we drag the MIME/SMIME component to the pipeline, we can see a combo with the possible choice of the properties:
- Content transfer encoding
- Encryption algorithm
- Signature Type
But when we try to configure the component in the BizTalk Administration Console, is a little different:
The choice option in visual studio is plain text in Administration console, and the values are a little different.
Possible values in Administration Console for “Content transfer encoding” property
- base64 – plain text for the option Base64 in Visual Studio
- quoted-printable – plain text for the option QuotedPrintable in Visual Studio
- 7bit – plain text for the option SevenBit in Visual Studio
- 8bit – plain text for the option EightBit in Visual Studio
- Binary – plain text for the option Binary in Visual Studio
- UUEncode – plain text for the option UUEncode in Visual Studio
Possible values in Administration Console for “Encryption algorithm” property
- 0 – code for the option DES3 in Visual Studio
- 1 – code for the option DES in Visual Studio
- 2 – code for the option RC2 in Visual Studio
Possible values in Administration Console for “Signature Type” property
- 0 – code for the option NoSign in Visual Studio
- 1 – code for the option ClearSign in Visual Studio
- 2 – code for the option BlobSign in Visual Studio
Note: After changing the component in the administration console, you have to restart the associated host instance.
Sir kindly post a similar article to configure the properties for the MIME/SMIME Decoder pipeline component.
Hi Sandro,
Your Blogs are really helpful. Having a weird issue while encrypting the message with AES256 algorithm in Biz-talk 2016.
1. Created a pipeline component with MIME encoder.
2.Enabled Encryption is ‘True’ and Encryption Algorithm is ‘AES256’
3. Content transfer encoding has been used to ‘Base64’
Verified message parts in run time, the message part has been encrypted with trading partners public key (cert) and XML file drop in the folder.
No error displayed but file has 0 bytes. (kind of empty file) please advise…