Open topic with navigation

TIBCO BusinessConnect™ Container Edition 1.2.0

# Configuring AS1 Email for a Trading Partner

To configure AS1 Email for a trading partner, perform these steps:

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 page, 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.
6. Enter the transport name.
7. Select AS1_Email from the list and, enter required information in the following fields:

   AS1_Email Transport Settings
   Field | Description
   --- | ---
   Transport Name | An identifier for these transport settings.
   URL | (Required) The URL for the trading partner. 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, refer to 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 select the Sign check box 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. For more information, see TIBCO BusinessConnect Container Edition Concepts, "Non-Repudiation."
   Sign | Enable outbound request messages or acknowledgments to be signed using your private key. Your partner uses your public key to authenticate your message. The 1024-bit key length is used for signatures. TIBCO BusinessConnect Container Edition can process messages which contain message digests computed using the SHA1 hash algorithms. By default, TIBCO BusinessConnect Container Edition will use the SHA1 hash algorithm when signing outbound messages for the AS1 and AS2 transports. To override this behavior, set the TIBCO BusinessConnect Container Edition property bc.ediint.digestAlgorithmEnabled to true under System Settings. This will cause TIBCO BusinessConnect Container Edition to compute the message digests for AS1 and AS2 using the digest algorithm setting specified for the business agreement in the Document Security screen. 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 check box to apply the signature scheme.
   Encrypt | Enable 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 Security 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, RSA-OAEP-sha256, RSA-OAEP-sha384, and RSA-OAEP-sha512. The default option is RSA-PKCS1-v1_5. Note: Ensure to enable the Encrypt check box to apply the encryption scheme.
   Compress | If selected, each outgoing message is compressed in ZLIB format.
   Compression Order | File compression is performed in the following orders: Before Signing File compression is performed before signing. After Signing File compression is performed after signing.
   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 Security screen. 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

8. Click Add.

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-2022. TIBCO Software Inc. All Rights Reserved.