Configuring transport servers for exchange profiles
When you configure a receiver or a destination in an exchange profile, the configuration includes a server that uses either the HTTP, HTTPS, or SFTP transport protocol.
The server is where a file is directed by the rules of the exchange profile when the file is sent to or from a trading partner.
The following table describes the basic characteristics of each protocol:
| Protocol | Description |
|---|---|
| HTTP (Hypertext Transfer Protocol) | Used for communications between a web server and a browser. |
| HTTPS (Hypertext Transfer Protocol Secure) | HTTP through a secured connection. Communications are encrypted with either the Transport
Layer Security (TLS) or Secure Sockets Layer (SSL) cryptographic protocol. Important: Selecting an SSL protocol for message exchanges, including such configurations as SSL_TLS,
SSL, SSLv2, SSL, SSLv2, SSLv3, is not suggested. A security risk exists for all SSL protocols.
Available TLS connection protocols include TLS, TLSv1, TLSv1.1, and TLSv1.2.
Important: If you are using a custom system certificate using SHA-1 or MD5,
you must replace it with a certificate that uses SHA-2.
|
| SFTP (SSH File Transfer Protocol) | Provides secure file transfer over a secure channel that uses the SSH cryptographic
protocol. Restriction: SFTP does not use the SSL cryptographic protocol. SFTP is not
affected by the risks of SSL.
|
The security needs and security technology of your trading partner help determine the type of transport protocol for your installation. For example, if your trading partner uses SFTP for communications, then you must configure an exchange profile that uses SFTP.