Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 13 AS2 Transport : Setting Up AS2-HTTP/S for a Trading Partner

Setting Up AS2-HTTP/S for a Trading Partner
To make a transport available for a trading partner, you have to perform the following tasks:
1.
2.
See Business Agreement: Transports Tab for more details.
Configuring AS2-HTTP/S for a Trading Partner
To configure AS2-HTTP/S for a trading partner, perform these steps:
1.
In TIBCO Administrator, expand BusinessConnect > Participants.
2.
3.
Select the Protocols tab.
4.
The Edit Enabled Protocol dialog is displayed. The General tab is selected by default.
5.
6.
Select the Transports tab to add the transport for this participant.
7.
Click Add.
The New Transport dialog is displayed. Select or enter data as described in Table 42.
Select AS2-HTTP or AS2-HTTPS from the Transport Type list. This action adds the AS2-HTTP/S item to the list in the Primary Transport areas described in Table 12, Editing Protocol Bindings: Transports Tab.
8.
The URL for the trading partner. Syntax: https://host:port/dmz/protocol. Example: https://host_machine8:6705/dmz/EZComm.
For more information, see TIBCO BusinessConnect Concepts, "Non-Repudiation."
TIBCO BusinessConnect can process messages which contain message digests computed using the SHA1 hash algorithm. By default, TIBCO BusinessConnect will use the SHA1 hash algorithm when signing outbound messages for the AS1 and AS2 transports. To override this behavior, set the TIBCO BusinessConnect property bc.ediint.digestAlgorithmEnabled to true under System Settings. This will cause TIBCO BusinessConnect to compute the message digests for AS1 and AS2 using the digest algorithm setting specified for the business agreement in the Document Security screen.
Note: Ensure to enable the Sign check box to apply the signature scheme.
The default option is RSA-PKCS1-v1_5.
Note: Ensure to enable the Encrypt check box to apply the encryption scheme.
Before Signing  File compression is performed before signing.
After Signing  File compression is performed after signing.
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.
Note: If you want to receive the timeout error when no response received from your partner, the value in this field must be less than the value set in the Response Wait Time field in the Configuration tab of the SendRequest activity.
All ciphers are listed in TIBCO BusinessConnect Concepts, "Cipher Suites."
Note: If you select TLS version 1.1 or 1.2, you have to select SUN or IBM as the security vendor for inbound and outbound socket operations.
9.
Click Save three times.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved