Page 91 - E-Commerce

90

EDI Protocol

An EDI protocol describes and defines the exchange of data between computers and
is used by the communication software/application. In essence each protocol is like a
separate language, as unless the trading partners are using a VAN, the computers of
both parties must use the same protocol in order to communicate.
The chosen protocol also determines the level of message encryption, what software
and hardware will be required and the ease with which transmissions can be received
(i.e. whether both sides’ machines have to be online at the same time for message
exchange to occur or not).
Although EDI can theoretically be conducted between two partners via any electronic
method capable of transmitting the relevant information, the vast majority of EDI
today is conducted over the internet. With the emergence of new technology came the
need for standardised protocols. Naturally, over the past few decades the number of
these protocols has gradually increased. Thankfully, however, most supply chain
organisations today use one of the following exchange channels:

HTTP

First established in 1991, HTTP, or Hypertext Transfer Protocol, is a well-known and
popular file transfer protocol. Since its inception four subsequent updates have been
released, with the fifth and latest (confusingly called version 3.0) coming in 2018.
As it only requires a web browser and no additional installation, HTTP constitutes a
simple method of completing person to server and person to person file transfers. As
anyone who uses the internet is likely to recognise, HTTP resources can be easily
located on the network through URLs (or Uniform Resource Identifiers).
The downside of this simplicity is the lack of security HTTP offers, however. Although
not as prone to firewall issues as File Transfer Protocol (FTP), HTTP is unable to
secure data or meet regulatory measures. Due to the security disadvantage plain HTTP
is therefore not recommended and at least the use of HTTPS with TLS (transport layer
security) should be considered.
Similarly, as HTTP does not offer users the ability to receive receipts automatically,
HTTP is lacking when it comes to message traceability.

Advantages of HTTP
 Simple to implement
 Ease of use (only requires a web browser)
 Less prone to firewall issues than other protocols due to standard port range
Disadvantages of HTTP
 Not secure
 No process traceability