Open topic with navigation

TIBCO BusinessConnect™ Container Edition 1.3.0

# Setting Up Email for a Trading Partner

To make a transport available for a trading partner, you have to perform the following tasks:

1. Configuring Email for a Trading Partner
2. Select this transport for the partner in the Inbound transport for Partner section on the Business Agreements > Bind Protocol > Available Protocols > Edit Configurations > Transports.

Note: Only the transport protocols that are selected in System Settings > Transport Protocols > Inbound Protocols are displayed in the Inbound transport for Partner section.

## Configuring Email for a Trading Partner

To configure Email transport for a trading partner, perform the following steps:

Procedure
1. On the Partner Management tile, click Partners.
2. On the Partners page, click any partner you wish to configure this transport.
3. In the Edit Partner window, on the Protocol tab, click Edit Configurations for any protocol you wish to configure.
4. On the protocol configurations page, click the Add icon.
5. In the Add Transport dialog box, enter required information in the following fields:

   Email Transport Settings
   Field | Description
   --- | ---
   Transport Name | An identifier for these transport settings.
   Transport Type | Select EMAIL transport from the drop-down list.
   URL (mailto) | The URL for the trading partner is: mailto: e-mailID@domain.com.
   Subject | A short string identifying the topic of the email message; for example, “Purchase Order from ABC Company”. For more information on the Subject Header field for MIME messages, see RFC C2822, Internet Message Format.
   Base64 Encode Clear Text Messages | Base64 encode plain outbound email messages. Plain messages are those messages which are not signed, not encrypted, and not compressed.
   Non Repudiation of Receipt | Enable logging of receipts in the non-repudiation table. If you check this option, you must also check the Sign checkbox and set Request Receipt to Signed. This means that outbound messages are signed and signed receipts are requested from the Responder. The original signed request from the Initiator and the signed receipt from the Responder are logged in the Initiator’s non-repudiation table.
   Sign | Enable outbound request messages or acknowledgments to be signed using your private key. Your trading partner uses your public key to authenticate your message. The 1024-bit key length is used for signatures. TIBCO BusinessConnect Container can process messages which contain message digests computed using the SHA1 hash algorithm. However, TIBCO BusinessConnect Container Edition computes its message digests using the digest algorithm setting specified for the business agreement in the Document Exchange tab. Whether an outbound receipt is signed or not is controlled by the setup in the requesting partner’s Request Receipt list.
   Signature Scheme | Select the desired signature algorithm from the list of options: RSA, RSA-PSS. The default option is RSA. Note: Ensure to enable the Sign checkbox to apply the signature scheme.
   Encrypt | Enables each outgoing message to be encrypted using your partner’s public key. Your partner uses their private key to decrypt your message. The encryption algorithm specified for the business agreement in the Document Exchange screen is used to encrypt the email messages.
   Encryption Scheme | Select the desired encryption algorithm from the list of options: RSA-PKCS1-v1_5, RSA-OAEP, and RSA-OAEP-sha256, RSA-OAEP-sha384, and RSA-OAEP-sha512. The default option is RSA-PKCS1-v1_5. Note: Ensure to enable the Encrypt checkbox to apply the encryption scheme.
   Compress | File compression is always performed before message signing. If selected, each outgoing message is compressed in GZIP file format.
   Send Data as Attachment | If selected, the outbound business documents will be sent as file attachments to email messages. Normally, the business documents are sent inline, as the main body of an email message.
   Use Attachment Filename as Subject | If selected, the file name of the first attachment of the email is used as the message subject. This file name is presented in the Content Disposition MIME header with a type of "attachment" of the first attachment. Note: This feature is introduced for TIBCO BusinessConnect Container Edition - EDI Protocol powered by Instream, EDIFACT Protocol, and cannot be used by other protocols.
   Request Receipt | The type of receipt returned from the trading partner. The following options are available: None No receipt is requested from the trading partner for a message. Signed A signed receipt is requested from the trading partner for each message. After the Responder gets the document and verifies the content for integrity, a signed receipt is created and sent by the trading partner. Unsigned An unsigned receipt is requested from the trading partner for each message. If you choose to request a receipt of any kind, you must have a valid email address set for the trading host. If you checked Non Repudiation of Receipt, you should select Signed. For computing the message digest, BusinessConnect Container Edition uses the digest algorithm that was configured for the business agreement in the Document Exchange page. For more information on receipts, see Message Disposition Notification Receipts.
   Receipt Timeout (minutes) | The amount of time within which a receipt should be returned by the trading partner. Example: 5

6. Click Add.

# Setting the Partner’s Email Address for a Protocol

Procedure
1. On the Partner Management tile, click Partners.
2. On the Partners page, click any one of the partners whose email address you wish to set.
3. On the Edit Partner page, click protocol > Edit Configurations.
4. In the General tab of the protocol configuration page, enter partner's email address in the Valid Email Address List field.
5. Click Save.

Did you find this helpful?

Yes No
Great!
Thanks for taking the time to give us some feedback.
Sorry about that

Why wasn't this helpful? (check all that apply)

Could not find what I was looking for
Instructions confusing or unclear
Instructions did not work

Want to tell us more?

Please select at least one option or provide details about the issue!!

Error occurred while submitting feedback.

Error2 occurred while submitting feedback.

TIBCO BusinessConnect™ Container Edition

Copyright © 2001-2023. Cloud Software Group, Inc. All Rights Reserved.