Copyright © Cloud Software Group, Inc. All Rights Reserved

Transports Tab

Use the Transports tab to set transport information for a transporting Gateway.

A transporting Gateway can be shared by multiple B2B-EDIFACT and B2B-X12 trading partners, while it is not supported for partners using the B2B-TEXT protocol.

The top section of the tab is used for selecting transports for the outbound, or host to trading partner, direction. The bottom section of the tab is used for selecting and configuring transports for the inbound, or trading partner to host, direction.

See Transports Tab.

Table 10 Outbound Transport for the Host

Field	Description
Primary Transport	Outbound transport is supported only in the passthrough mode. That is, there is no validation available, and no conversion from B2B-TEXT to XML. Choose the primary transport from the list of transports previously configured in a trading partner’s Protocols > Transports tab (Transports Tab): FTP, FILE, FTPS, AS2-HTTP, AS2-HTTPS, SSHFTP See the Transports chapters in the TIBCO BusinessConnect Trading Partner Administration.
Backup Transport	TIBCO BusinessConnect B2BPlugin for CMI supports a backup outbound transport for sending files to the trading partner. This backup transport is used if the file could not be sent via the primary transport configured in the business agreement. Such situation may happen if the trading partner’s server is not available or has a wrong URL during the time the file is being sent: the file still needs to reach the server via some other means even after the primary transport retry was exhausted. Backup transports are configured at the business agreement level and can be one of the supported BusinessConnect transports. The same rules apply for choosing a backup transport as for a primary transport.
AS2 Async MDN Reply Transport	Same as for TIBCO BusinessConnect: select any of the configured transports. The settings from the specified AS2 MDN Async Reply Transport field are used for sending async MDN responses back to your trading partner. Configuring the AS2 MDN Async Reply Transport is not necessary unless you would like to specify different values for the following HTTP transmission related settings: • Retry Count – default is 3 • Retry Interval – default is 60 seconds • Socket Timeout – default is 300 seconds (5 minutes) Any other settings specified in the AS2 MDN Async Reply Transport are ignored. The most common case for which you would specify this transport is when your trading partner is not acknowledging the receipt of your async MDNs within the default socket timeout period.
AS2 Async MDN Remote Server Certificate	Same as for TIBCO BusinessConnect. The Remote Server Certificate for the AS2 HTTPS transport is a SSL certificate that should be used for encrypting the data sent using HTTPS. This dropdown list contains all of the certificates that have been configured for the Trading Partner. You can select the one that was configured to be used for SSL encryption. Note   The server certificate configuration is only required for Async MDNs via AS2 HTTPS transport.
Client Authentication Identity for HTTPS, FTPS, HTTPSCA	Choose between the transport that was set up as Client Authentication Identity for HTTPS, FTPS, HTTPSCA, or None.
Client Authentication Identity for SSHFTP	Choose between the transport that was set up as Client Authentication Identity for SSHFTP, or None.

Setting the Inbound Transport

What displays in this area depends on the transports that are selected in the Inbound Public Transport Types area under the System Settings tab.

For further information, see the section on Deployment Configuration in the TIBCO BusinessConnect Trading Partner Administration.

Table 11 Inbound Transport Fields 

Field	Description
HTTP/S	Allow HTTP/S connections from this partner directly or from a VAN. This also applies when the inbound connection is using the AS2 transport.
HTTPSCA/AS2	See TIBCO BusinessConnect Trading Partner Administration, Chapter 11, HTTP, HTTPS, and HTTPSCA Transports.
FTP/S	Allow the host to perform FTP/S connections with this partner. The host is the Initiator of the FTP process. Click Edit Settings to configure FTP/S. See TIBCO BusinessConnect Trading Partner Administration Guide for more information on how a host uses FTP.
FILE	Allow FILE connections from this partner. FILE is normally used for file exchange within an enterprise. If your partner uses FILE and a transporting Gateway to send EDI documents back to you through a VAN, you need to configure FTP transport. You must use FTP to get your partner’s documents from the VAN Gateway site. This is because a VAN receives documents for multiple trading partners, but does not forward those documents to the recipients.
SSHFTP	See TIBCO BusinessConnect Trading Partner Administration, Chapter 15, SSHFTP Transport.

Copyright © Cloud Software Group, Inc. All Rights Reserved